AI-103 Practice Question 73: Data Zone Deployment Residency
Microsoft Azure AI Apps and Agents Developer Associate (AI-103) · Test 8 · question 3 of 10
A US hospital network's compliance policy states that patient data sent to a generative AI model must never be processed outside the United States, full stop. Their current deployment is Global Standard, chosen for its high default quota and pay-per-token billing, and they want to keep both of those. They do not have steady enough volume to justify reserved throughput, and confining the deployment to a single Azure region would leave them short of quota during peak intake.
Which deployment type satisfies the residency requirement without giving up quota or pay-per-token billing?
Show answer and explanation
Answer:
Microsoft's deployment-type documentation draws this exact line: for Global types, "the service can process prompts and responses in any geography where the model is deployed," while for Data Zone types, "the service processes prompts and responses only within the specified data zone", and the United States is one of the three defined zones. Data Zone Standard keeps pay-per-token billing and offers "higher default quotas than geography-based deployment types while keeping data within the specified zone," which is precisely the combination the hospital needs: US-only processing without dropping to single-region quota or reserved capacity billing.
- A is wrong because it conflates data at rest with data in transit for inference. Global Standard's *storage* stays in the deployment's geography, but its *inference processing* is explicitly allowed to run in any Azure region worldwide, the failure mode the policy forbids. - C is wrong because a single-region Standard deployment does satisfy residency, but it is the option the hospital already ruled out: it caps quota at that one region's capacity, which they said leaves them short during peak intake. - D is wrong on two counts: Global Provisioned still routes processing to any Azure region like other Global types, and Provisioned bills for reserved throughput rather than pay-per-token, which the hospital also wants to avoid.
Reference: Understanding deployment types in Microsoft Foundry Models