Subdomain 1.1: Choose the appropriate Foundry services for generative AI and agents
1.A startup expects unpredictable, low-volume traffic to its generative AI feature and wants to avoid provisioning and paying for dedicated virtual machine capacity while the feature is idle. Which Foundry Models deployment option fits best?
- A.Serverless deployment billed per token consumed through a hosted API
- B.Managed compute deployment billed for dedicated virtual machine core hours
- C.A hub-based deployment requiring a reserved GPU cluster around the clock
- D.A fine-tuning job that trains a new model copy for every incoming request
Show answer & explanation
Correct answer: A — Serverless deployment billed per token consumed through a hosted API
- A. Correct. Serverless deployment bills per token processed through a Microsoft-hosted API, so there's no idle virtual machine cost during low or unpredictable traffic.
- B. Incorrect. Managed compute bills for the virtual machine core hours behind the deployment regardless of whether traffic is flowing, which wastes cost when idle.
- C. Incorrect. A reserved GPU cluster running continuously incurs cost whether or not requests arrive, the opposite of what this cost-sensitive startup needs.
- D. Incorrect. Fine-tuning trains a model on data ahead of time; it isn't a per-request serving mechanism and wouldn't run for every incoming request.