Microsoft AI-103 (Developing AI Apps and Agents on Azure) Practice Test 6

Question 50

A production AI solution is being scoped for production. The non-negotiable task is to keep Foundry resource access off public paths for a network-restricted application. Which implementation fits?

  1. Use private connectivity and correct DNS resolution
  2. Use deployment aliases or versioned configuration for controlled rollout
  3. Use managed identity for a production Azure-hosted app
  4. Use asynchronous batch inference for delay-tolerant processing

Explanation

Correct Answer

A:

For the stated requirement to keep Foundry resource access off public paths for a network-restricted application, private endpoints route traffic over approved private networking; proper private DNS and routing are prerequisites for clients to reach the service; this is the mechanism that the system must implement.

Incorrect Answers

B:

For a system whose objective is to move a subset of application traffic to a newly validated model without changing every client, an application-level rollout control separates client configuration from backend deployment selection, enabling staged exposure and rollback; this does not directly meet the required outcome to keep Foundry resource access off public paths for a network-restricted application.

C:

For a system whose objective is to avoid storing long-lived service keys in source control while authorizing access to Foundry resources, managed identity provides an Azure-hosted workload an Entra identity; it still needs the correct data-plane roles and reachable resource endpoint; this does not directly meet the required outcome to keep Foundry resource access off public paths for a network-restricted application.

D:

For a system whose objective is to summarize a nightly backlog of records without any requirement for immediate responses, batch deployments are designed for large asynchronous jobs and favorable economics; they are not a synchronous low-latency chat endpoint; this does not directly meet the required outcome to keep Foundry resource access off public paths for a network-restricted application.

Question 51

A design review proposes to run evaluated model changes through CI/CD gates. Which measurable check would establish success on real inputs?

  1. Run drift detection and compare provisioned configuration with approved definitions
  2. Verify deployment type and allowed processing boundary against compliance requirements
  3. Check pipeline rejection on a deliberately failing evaluation and verify rollback readiness
  4. Exercise the deployment endpoint from a smoke test and check resolved deployment metadata

Explanation

Correct Answer

C:

The accepted change is to run evaluated model changes through CI/CD gates; this evaluation checks whether it can prevent a newly deployed model or prompt from reaching users before quality and safety checks pass, since a delivery pipeline can test application behavior, evaluations and deployment health before promotion; versioned artifacts support rollback.

Incorrect Answers

A:

This test concerns the ability to reproduce Foundry resources, roles, and deployment settings across test and production environments, for which infrastructure-as-code records resource configuration for reviewable repeatable deployments and reduces portal-only drift; secrets remain in secure stores; it does not establish whether the change to run evaluated model changes through CI/CD gates works for the current release.

B:

This test concerns the ability to process prompts only within an approved Microsoft-defined data zone while demand fluctuates, for which data Zone Standard keeps inference processing within its specified zone while retaining pay-as-you-go characteristics; geography-specific processing is a different constraint; it does not establish whether the change to run evaluated model changes through CI/CD gates works for the current release.

D:

This test concerns the ability to invoke a specific deployed model from application code when a catalog model has multiple deployments, for which a model's catalog identity is not necessarily the deployment identifier used by inference requests; deployment references need environment-aware configuration; it does not establish whether the change to run evaluated model changes through CI/CD gates works for the current release.

Question 52

The acceptance criteria for a Foundry-based application require it to prevent a newly deployed model or prompt from reaching users before quality and safety checks pass. Which design should be approved?

  1. Use managed identity for a production Azure-hosted app
  2. Run evaluated model changes through CI/CD gates
  3. Use the project's scoped endpoint and identity
  4. Separate deployment names from model names

Explanation

Correct Answer

B:

For the stated requirement to prevent a newly deployed model or prompt from reaching users before quality and safety checks pass, a delivery pipeline can test application behavior, evaluations and deployment health before promotion; versioned artifacts support rollback; this is the mechanism that the system must implement.

Incorrect Answers

A:

For a system whose objective is to avoid storing long-lived service keys in source control while authorizing access to Foundry resources, managed identity provides an Azure-hosted workload an Entra identity; it still needs the correct data-plane roles and reachable resource endpoint; this does not directly meet the required outcome to prevent a newly deployed model or prompt from reaching users before quality and safety checks pass.

C:

For a system whose objective is to connect a Python application to its intended Foundry project instead of accidentally calling another environment, a project-scoped endpoint and appropriate credential select the target project and permitted resources; hardcoded secrets add avoidable risk; this does not directly meet the required outcome to prevent a newly deployed model or prompt from reaching users before quality and safety checks pass.

D:

For a system whose objective is to invoke a specific deployed model from application code when a catalog model has multiple deployments, a model's catalog identity is not necessarily the deployment identifier used by inference requests; deployment references need environment-aware configuration; this does not directly meet the required outcome to prevent a newly deployed model or prompt from reaching users before quality and safety checks pass.

Question 53

In an architecture review, the key requirement is to support high predictable usage while requiring processing within an Azure geography. Which solution directly satisfies it?

  1. Use asynchronous batch inference for delay-tolerant processing
  2. Use Global Standard for flexible general inference
  3. Use regional provisioned throughput for stable localized capacity
  4. Check model and region availability before provisioning

Explanation

Correct Answer

C:

For the stated requirement to support high predictable usage while requiring processing within an Azure geography, regional provisioned deployments reserve model throughput within an Azure geography where supported; this couples residency with more predictable capacity; this is the mechanism that the system must implement.

Incorrect Answers

A:

For a system whose objective is to summarize a nightly backlog of records without any requirement for immediate responses, batch deployments are designed for large asynchronous jobs and favorable economics; they are not a synchronous low-latency chat endpoint; this does not directly meet the required outcome to support high predictable usage while requiring processing within an Azure geography.

B:

For a system whose objective is to serve an unpredictable low-to-medium traffic pilot without geographic processing restrictions, global Standard offers pay-per-token inference with flexible global routing; it does not reserve a fixed amount of dedicated throughput; this does not directly meet the required outcome to support high predictable usage while requiring processing within an Azure geography.

D:

For a system whose objective is to avoid selecting a model or deployment type unsupported in the intended Azure region, Foundry model availability varies by model, region and deployment type; a catalog listing alone does not mean every combination can be deployed; this does not directly meet the required outcome to support high predictable usage while requiring processing within an Azure geography.

Question 54

After implementing a workflow to use a Data Zone Standard deployment for zone boundaries, the team needs a robust release gate. Which check should it choose?

  1. Load-test p95 latency, provisioned utilization, and the configured geography boundary
  2. Smoke-test the target project and resource identifiers in each deployed environment
  3. Measure batch completion, failures, and total cost against the overnight processing window
  4. Verify deployment type and allowed processing boundary against compliance requirements

Explanation

Correct Answer

D:

The accepted change is to use a Data Zone Standard deployment for zone boundaries; this evaluation checks whether it can process prompts only within an approved Microsoft-defined data zone while demand fluctuates, since data Zone Standard keeps inference processing within its specified zone while retaining pay-as-you-go characteristics; geography-specific processing is a different constraint.

Incorrect Answers

A:

This test concerns the ability to support high predictable usage while requiring processing within an Azure geography, for which regional provisioned deployments reserve model throughput within an Azure geography where supported; this couples residency with more predictable capacity; it does not establish whether the change to use a Data Zone Standard deployment for zone boundaries works for the current release.

B:

This test concerns the ability to connect a Python application to its intended Foundry project instead of accidentally calling another environment, for which a project-scoped endpoint and appropriate credential select the target project and permitted resources; hardcoded secrets add avoidable risk; it does not establish whether the change to use a Data Zone Standard deployment for zone boundaries works for the current release.

C:

This test concerns the ability to summarize a nightly backlog of records without any requirement for immediate responses, for which batch deployments are designed for large asynchronous jobs and favorable economics; they are not a synchronous low-latency chat endpoint; it does not establish whether the change to use a Data Zone Standard deployment for zone boundaries works for the current release.

Question 55

The support ticket describes this behavior: A private endpoint is created but applications still resolve the service name to a public address. Which engineering change should come first?

  1. Introduce controlled routing between versioned deployments and retain a tested rollback target
  2. Read the actual deployment identifier from the target environment and update application configuration
  3. Fix private DNS linkage and ensure the client network reaches the private endpoint
  4. Switch the pilot to an eligible Global Standard deployment and monitor metered usage
  5. Enable its managed identity and assign the minimum required resource roles

Explanation

Correct Answer

C:

The fault signal is that a private endpoint is created but applications still resolve the service name to a public address; the targeted fix works because private endpoints route traffic over approved private networking; proper private DNS and routing are prerequisites for clients to reach the service, restoring the ability to keep Foundry resource access off public paths for a network-restricted application.

Incorrect Answers

A:

If the failing function were to move a subset of application traffic to a newly validated model without changing every client, this change could be relevant because an application-level rollout control separates client configuration from backend deployment selection, enabling staged exposure and rollback; the actual symptom is that a private endpoint is created but applications still resolve the service name to a public address, which calls for a different repair.

B:

If the failing function were to invoke a specific deployed model from application code when a catalog model has multiple deployments, this change could be relevant because a model's catalog identity is not necessarily the deployment identifier used by inference requests; deployment references need environment-aware configuration; the actual symptom is that a private endpoint is created but applications still resolve the service name to a public address, which calls for a different repair.

D:

If the failing function were to serve an unpredictable low-to-medium traffic pilot without geographic processing restrictions, this change could be relevant because global Standard offers pay-per-token inference with flexible global routing; it does not reserve a fixed amount of dedicated throughput; the actual symptom is that a private endpoint is created but applications still resolve the service name to a public address, which calls for a different repair.

E:

If the failing function were to avoid storing long-lived service keys in source control while authorizing access to Foundry resources, this change could be relevant because managed identity provides an Azure-hosted workload an Entra identity; it still needs the correct data-plane roles and reachable resource endpoint; the actual symptom is that a private endpoint is created but applications still resolve the service name to a public address, which calls for a different repair.

Question 56

Engineers have implemented a change to use managed identity for a production Azure-hosted app. What validation would expose a remaining defect?

  1. Check provisioning preflight results for the required region and deployment type
  2. Run drift detection and compare provisioned configuration with approved definitions
  3. Confirm token-based access succeeds and the app can operate without embedded keys
  4. Resolve resource hostnames from the workload subnet and trace the resulting private network path

Explanation

Correct Answer

C:

The accepted change is to use managed identity for a production Azure-hosted app; this evaluation checks whether it can avoid storing long-lived service keys in source control while authorizing access to Foundry resources, since managed identity provides an Azure-hosted workload an Entra identity; it still needs the correct data-plane roles and reachable resource endpoint.

Incorrect Answers

A:

This test concerns the ability to avoid selecting a model or deployment type unsupported in the intended Azure region, for which Foundry model availability varies by model, region and deployment type; a catalog listing alone does not mean every combination can be deployed; it does not establish whether the change to use managed identity for a production Azure-hosted app works for the current release.

B:

This test concerns the ability to reproduce Foundry resources, roles, and deployment settings across test and production environments, for which infrastructure-as-code records resource configuration for reviewable repeatable deployments and reduces portal-only drift; secrets remain in secure stores; it does not establish whether the change to use managed identity for a production Azure-hosted app works for the current release.

D:

This test concerns the ability to keep Foundry resource access off public paths for a network-restricted application, for which private endpoints route traffic over approved private networking; proper private DNS and routing are prerequisites for clients to reach the service; it does not establish whether the change to use managed identity for a production Azure-hosted app works for the current release.

Question 57

Before approving the proposed action to use Global Standard for flexible general inference, which measurable acceptance check should be required?

  1. Measure batch completion, failures, and total cost against the overnight processing window
  2. Load-test p95 latency, provisioned utilization, and the configured geography boundary
  3. Check pipeline rejection on a deliberately failing evaluation and verify rollback readiness
  4. Compare hourly demand variance, token spend, and successful requests before and after the change

Explanation

Correct Answer

D:

The accepted change is to use Global Standard for flexible general inference; this evaluation checks whether it can serve an unpredictable low-to-medium traffic pilot without geographic processing restrictions, since global Standard offers pay-per-token inference with flexible global routing; it does not reserve a fixed amount of dedicated throughput.

Incorrect Answers

A:

This test concerns the ability to summarize a nightly backlog of records without any requirement for immediate responses, for which batch deployments are designed for large asynchronous jobs and favorable economics; they are not a synchronous low-latency chat endpoint; it does not establish whether the change to use Global Standard for flexible general inference works for the current release.

B:

This test concerns the ability to support high predictable usage while requiring processing within an Azure geography, for which regional provisioned deployments reserve model throughput within an Azure geography where supported; this couples residency with more predictable capacity; it does not establish whether the change to use Global Standard for flexible general inference works for the current release.

C:

This test concerns the ability to prevent a newly deployed model or prompt from reaching users before quality and safety checks pass, for which a delivery pipeline can test application behavior, evaluations and deployment health before promotion; versioned artifacts support rollback; it does not establish whether the change to use Global Standard for flexible general inference works for the current release.

Question 58

After deployment, the team observes: A pipeline fails only in the production region because the selected deployment configuration is unavailable there. Which remediation addresses the likely cause?

  1. Validate the model-and-deployment-type availability matrix for the target region before deployment
  2. Fix private DNS linkage and ensure the client network reaches the private endpoint
  3. Enable its managed identity and assign the minimum required resource roles
  4. Read the actual deployment identifier from the target environment and update application configuration

Explanation

Correct Answer

A:

The fault signal is that a pipeline fails only in the production region because the selected deployment configuration is unavailable there; the targeted fix works because Foundry model availability varies by model, region and deployment type; a catalog listing alone does not mean every combination can be deployed, restoring the ability to avoid selecting a model or deployment type unsupported in the intended Azure region.

Incorrect Answers

B:

If the failing function were to keep Foundry resource access off public paths for a network-restricted application, this change could be relevant because private endpoints route traffic over approved private networking; proper private DNS and routing are prerequisites for clients to reach the service; the actual symptom is that a pipeline fails only in the production region because the selected deployment configuration is unavailable there, which calls for a different repair.

C:

If the failing function were to avoid storing long-lived service keys in source control while authorizing access to Foundry resources, this change could be relevant because managed identity provides an Azure-hosted workload an Entra identity; it still needs the correct data-plane roles and reachable resource endpoint; the actual symptom is that a pipeline fails only in the production region because the selected deployment configuration is unavailable there, which calls for a different repair.

D:

If the failing function were to invoke a specific deployed model from application code when a catalog model has multiple deployments, this change could be relevant because a model's catalog identity is not necessarily the deployment identifier used by inference requests; deployment references need environment-aware configuration; the actual symptom is that a pipeline fails only in the production region because the selected deployment configuration is unavailable there, which calls for a different repair.

Question 59

A release reviewer is assessing a feature intended to check model and region availability before provisioning. Which test is most meaningful?

  1. Check provisioning preflight results for the required region and deployment type
  2. Smoke-test the target project and resource identifiers in each deployed environment
  3. Resolve resource hostnames from the workload subnet and trace the resulting private network path
  4. Measure error rates and evaluated answer quality by deployment cohort during canary rollout

Explanation

Correct Answer

A:

The accepted change is to check model and region availability before provisioning; this evaluation checks whether it can avoid selecting a model or deployment type unsupported in the intended Azure region, since Foundry model availability varies by model, region and deployment type; a catalog listing alone does not mean every combination can be deployed.

Incorrect Answers

B:

This test concerns the ability to connect a Python application to its intended Foundry project instead of accidentally calling another environment, for which a project-scoped endpoint and appropriate credential select the target project and permitted resources; hardcoded secrets add avoidable risk; it does not establish whether the change to check model and region availability before provisioning works for the current release.

C:

This test concerns the ability to keep Foundry resource access off public paths for a network-restricted application, for which private endpoints route traffic over approved private networking; proper private DNS and routing are prerequisites for clients to reach the service; it does not establish whether the change to check model and region availability before provisioning works for the current release.

D:

This test concerns the ability to move a subset of application traffic to a newly validated model without changing every client, for which an application-level rollout control separates client configuration from backend deployment selection, enabling staged exposure and rollback; it does not establish whether the change to check model and region availability before provisioning works for the current release.

Question 60

A project needs to complete all of these distinct tasks: (1) process prompts only within an approved Microsoft-defined data zone while demand fluctuates; and (2) summarize a nightly backlog of records without any requirement for immediate responses. Select one suitable capability for each task. Choose TWO.

  1. Use asynchronous batch inference for delay-tolerant processing
  2. Use private connectivity and correct DNS resolution
  3. Separate deployment names from model names
  4. Use regional provisioned throughput for stable localized capacity
  5. Use a Data Zone Standard deployment for zone boundaries
  6. Use Global Standard for flexible general inference

Explanation

Correct Answers

A:

For the stated requirement to summarize a nightly backlog of records without any requirement for immediate responses, batch deployments are designed for large asynchronous jobs and favorable economics; they are not a synchronous low-latency chat endpoint; this is the mechanism that the system must implement. This choice satisfies the specific deliverable to summarize a nightly backlog of records without any requirement for immediate responses, while the other deliverables require separate capabilities.

E:

For the stated requirement to process prompts only within an approved Microsoft-defined data zone while demand fluctuates, data Zone Standard keeps inference processing within its specified zone while retaining pay-as-you-go characteristics; geography-specific processing is a different constraint; this is the mechanism that the system must implement. This choice satisfies the specific deliverable to process prompts only within an approved Microsoft-defined data zone while demand fluctuates, while the other deliverables require separate capabilities.

Incorrect Answers

B:

For a system whose objective is to keep Foundry resource access off public paths for a network-restricted application, private endpoints route traffic over approved private networking; proper private DNS and routing are prerequisites for clients to reach the service; this does not directly meet the required outcome to process prompts only within an approved Microsoft-defined data zone while demand fluctuates.

C:

For a system whose objective is to invoke a specific deployed model from application code when a catalog model has multiple deployments, a model's catalog identity is not necessarily the deployment identifier used by inference requests; deployment references need environment-aware configuration; this does not directly meet the required outcome to process prompts only within an approved Microsoft-defined data zone while demand fluctuates.

D:

For a system whose objective is to support high predictable usage while requiring processing within an Azure geography, regional provisioned deployments reserve model throughput within an Azure geography where supported; this couples residency with more predictable capacity; this does not directly meet the required outcome to process prompts only within an approved Microsoft-defined data zone while demand fluctuates.

F:

For a system whose objective is to serve an unpredictable low-to-medium traffic pilot without geographic processing restrictions, global Standard offers pay-per-token inference with flexible global routing; it does not reserve a fixed amount of dedicated throughput; this does not directly meet the required outcome to process prompts only within an approved Microsoft-defined data zone while demand fluctuates.

Developing AI Apps and Agents on Azure (AI-103) Practice Tests