Microsoft AI-103 Practice Test 17 - Prepaway
Practice Exams:

Pass Microsoft AI-103 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers!

30 Days Free Updates, Instant Download!

Verified By Experts
Premium File
$89.99 $98.99

AI-103 Premium ETE File


  • Premium File 187 Questions & Answers. Last Update: Nov 15, 2026
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Microsoft AI-103 Practice Test 17

Question 160

Situation: A factory requires all model invocations to remain on approved private routes and to reject access from developer home networks. Which TWO proposed practices create material safety, correctness, or reliability risks? Select TWO answers.

  1. Inspect records that explain the affected process, then check the result described in this case: A factory requires all model invocations to remain on approved private routes and to reject access from developer home networks
  2. Map the service host name manually to an obsolete private address in application source
  3. Configure approved private connectivity and correct private DNS resolution for the Foundry dependencies, then validate blocked public paths
  4. Authorized app subnets resolve the service to private endpoints and connect while disallowed internet clients cannot access the data path
  5. Leave public network access enabled for a regulated model endpoint despite a private-endpoint requirement

Explanation

Correct Answer

B:

“Map the service host name manually to an obsolete private address in application source” would violate the requirement. A private endpoint alone cannot ensure isolation when clients resolve a public endpoint or dependent services still require unrestricted egress.

E:

Because a factory requires all model invocations to remain on approved private routes and to reject access from developer home networks, “Leave public network access enabled for a regulated model endpoint despite a private-endpoint requirement” would violate the requirement. A private endpoint alone cannot ensure isolation when clients resolve a public endpoint or dependent services still require unrestricted egress.

Incorrect Answers

A:

“Inspect records that explain the affected process, then check the result described in this case: A factory requires all model invocations to remain on approved private routes” adds a relevant safeguard or verification step rather than weakening the solution. A private endpoint alone cannot ensure isolation when clients resolve a public endpoint or dependent services still require unrestricted egress. Confirm that authorized app subnets resolve the service to private endpoints and connect while disallowed internet clients cannot access the data path.

C:

A factory requires all model invocations to remain on approved private routes and to reject access from developer home networks. “Configure approved private connectivity and correct private DNS resolution for the Foundry dependencies, then validate blocked public paths” is the controlled implementation, not an unsafe workaround. A private endpoint alone cannot ensure isolation when clients resolve a public endpoint or dependent services still require unrestricted egress. Confirm that authorized app subnets resolve the service to private endpoints and connect while disallowed internet clients cannot access the data path.

D:

A factory requires all model invocations to remain on approved private routes and to reject access from developer home networks. “Authorized app subnets resolve the service to private endpoints and connect while disallowed internet clients cannot access the data path” is the required outcome of a working control, not an action that weakens it. A private endpoint alone cannot ensure isolation when clients resolve a public endpoint or dependent services still require unrestricted egress. Confirm that authorized app subnets resolve the service to private endpoints and connect while disallowed internet clients cannot access the data path.

Question 161

Architecture case: A retail assistant is upgrading its model snapshot but a new version occasionally omits fields required by an order API. What configuration should the engineer choose for this workload?

  1. Treat matching endpoint URLs as evidence of behavioral equivalence
  2. Roll out the model version behind a small monitored canary, compare frozen evaluation cohorts, and maintain a rehearsed rollback path
  3. Apply the proposed setting to all connected workloads before testing the case-specific boundary: a retail assistant is upgrading its model snapshot but a new version occasionally omits fields required by an order api
  4. Suppress regression errors during version rollout

Explanation

Correct Answer

B:

Because a retail assistant is upgrading its model snapshot but a new version occasionally omits fields required by an order API, a model version update can change output structure, safety responses and token consumption even when the application API remains compatible. Canary evaluation remains within correctness and latency guardrails and rollback restores the last accepted version when thresholds are breached.

Incorrect Answers

A:

Because a retail assistant is upgrading its model snapshot but a new version occasionally omits fields required by an order API, “Treat matching endpoint URLs as evidence of behavioral equivalence” does not implement the control that the facts call for. A model version update can change output structure, safety responses and token consumption even when the application API remains compatible. Instead, roll out the model version behind a small monitored canary, compare frozen evaluation cohorts, and maintain a rehearsed rollback path.

C:

“Apply the proposed setting to all connected workloads before testing the case-specific boundary: a retail assistant is upgrading its model snapshot but a new version occasionally omits fields required by” does not implement the control that the facts call for. A model version update can change output structure, safety responses and token consumption even when the application API remains compatible. Instead, roll out the model version behind a small monitored canary, compare frozen evaluation cohorts, and maintain a rehearsed rollback path.

D:

“Suppress regression errors during version rollout” does not implement the control that the facts call for. A model version update can change output structure, safety responses and token consumption even when the application API remains compatible. Instead, roll out the model version behind a small monitored canary, compare frozen evaluation cohorts, and maintain a rehearsed rollback path.

Question 162

Production requirement: A retail assistant is upgrading its model snapshot but a new version occasionally omits fields required by an order API. What technical fact prevents the simplest shortcut from being reliable?

  1. A model version update can change output structure, safety responses and token consumption even when the application API remains compatible
  2. The most powerful or least restricted model is always the safest choice regardless of task conditions
  3. Successful provisioning by itself proves all security, output, and operational constraints are satisfied
  4. The fact that the team started work is enough to prove correctness for this exact case: a retail assistant is upgrading its model snapshot but a new version occasionally omits fields required by an order api

Explanation

Correct Answer

A:

Because a retail assistant is upgrading its model snapshot but a new version occasionally omits fields required by an order API, a model version update can change output structure, safety responses and token consumption even when the application API remains compatible. Roll out the model version behind a small monitored canary, compare frozen evaluation cohorts, and maintain a rehearsed rollback path. The decisive evidence is that canary evaluation remains within correctness and latency guardrails and rollback restores the last accepted version when thresholds are breached.

Incorrect Answers

B:

“The most powerful or least restricted model is always the safest choice regardless of task conditions” does not fully explain the decisive technical boundary in this case. A model version update can change output structure, safety responses and token consumption even when the application API remains compatible.

C:

“Successful provisioning by itself proves all security, output, and operational constraints are satisfied” does not fully explain the decisive technical boundary in this case. A model version update can change output structure, safety responses and token consumption even when the application API remains compatible. The implementation must roll out the model version behind a small monitored canary, compare frozen evaluation cohorts, and maintain a rehearsed rollback path.

D:

“The fact that the team started work is enough to prove correctness for this exact case: a retail assistant is upgrading its model snapshot but a new version occasionally omits fields required by an order” does not fully explain the decisive technical boundary in this case. A model version update can change output structure, safety responses and token consumption even when the application API remains compatible. The implementation must roll out the model version behind a small monitored canary, compare frozen evaluation cohorts, and maintain a rehearsed rollback path.

Question 163

A team is investigating this task: A retail assistant is upgrading its model snapshot but a new version occasionally omits fields required by an order API. What end-to-end test would distinguish successful operation from an installed configuration?

  1. The team closes a change ticket without replaying a representative positive and negative test
  2. The operator reports success without reproducing the observed behavior: a retail assistant is upgrading its model snapshot but a new version occasionally omits fields required by an order api
  3. A project dashboard remains green, although the affected request, output and permissions were not checked
  4. Canary evaluation remains within correctness and latency guardrails and rollback restores the last accepted version when thresholds are breached

Explanation

Correct Answer

D:

A retail assistant is upgrading its model snapshot but a new version occasionally omits fields required by an order API. A model version update can change output structure, safety responses and token consumption even when the application API remains compatible. Canary evaluation remains within correctness and latency guardrails and rollback restores the last accepted version when thresholds are breached.

Incorrect Answers

A:

A retail assistant is upgrading its model snapshot but a new version occasionally omits fields required by an order API. “The team closes a change ticket without replaying a representative positive and negative test” alone does not establish all the required behavior. Canary evaluation remains within correctness and latency guardrails and rollback restores the last accepted version when thresholds are breached.

B:

“The operator reports success without reproducing the observed behavior: a retail assistant is upgrading its model snapshot but a new version occasionally omits fields required by an order api” alone does not establish all the required behavior. Canary evaluation remains within correctness and latency guardrails and rollback restores the last accepted version when thresholds are breached.

C:

A retail assistant is upgrading its model snapshot but a new version occasionally omits fields required by an order API. “A project dashboard remains green, although the affected request, output and permissions were not checked” would not meet the requirement. Canary evaluation remains within correctness and latency guardrails and rollback restores the last accepted version when thresholds are breached. A model version update can change output structure, safety responses and token consumption even when the application API remains compatible.

Question 164

Situation: A retail assistant is upgrading its model snapshot but a new version occasionally omits fields required by an order API. Which diagnostic investigation best isolates the issue before another change?

  1. Assume the general service is at fault without checking the affected operation in this case: a retail assistant is upgrading its model snapshot but a new version occasionally omits fields required by an order api
  2. Read only the broad service-health summary and skip actual workload evidence
  3. Inspect pinned model versions, routing percentages, test-suite results, safety regressions, latency, spend and deployment-revision logs
  4. Restart every affected component before collecting request or tool traces

Explanation

Correct Answer

C:

Inspect pinned model versions, routing percentages, test-suite results, safety regressions, latency, spend and deployment-revision logs. A model version update can change output structure, safety responses and token consumption even when the application API remains compatible. Canary evaluation remains within correctness and latency guardrails and rollback restores the last accepted version when thresholds are breached.

Incorrect Answers

A:

“Assume the general service is at fault without checking the affected operation in this case: a retail assistant is upgrading its model snapshot but a new version occasionally omits fields required by an” would not meet the requirement. Inspect pinned model versions, routing percentages, test-suite results, safety regressions, latency, spend and deployment-revision logs. A model version update can change output structure, safety responses and token consumption even when the application API remains compatible.

B:

“Read only the broad service-health summary and skip actual workload evidence” would not meet the requirement. Inspect pinned model versions, routing percentages, test-suite results, safety regressions, latency, spend and deployment-revision logs. A model version update can change output structure, safety responses and token consumption even when the application API remains compatible.

D:

“Restart every affected component before collecting request or tool traces” would not be the most direct first check for this failure. Inspect pinned model versions, routing percentages, test-suite results, safety regressions, latency, spend and deployment-revision logs.

Question 165

Architecture case: A retail assistant is upgrading its model snapshot but a new version occasionally omits fields required by an order API. Which TWO shortcuts should be rejected for this scenario? Select TWO answers.

  1. Remove the previous model version before observing the canary
  2. Canary evaluation remains within correctness and latency guardrails and rollback restores the last accepted version when thresholds are breached
  3. Swap every production endpoint to an untested model snapshot simultaneously
  4. Inspect records that explain the affected process, then check the result described in this case: A retail assistant is upgrading its model snapshot but a new version occasionally omits fields required by an order API
  5. Roll out the model version behind a small monitored canary, compare frozen evaluation cohorts, and maintain a rehearsed rollback path

Explanation

Correct Answer

A:

“Remove the previous model version before observing the canary” would violate the requirement. A model version update can change output structure, safety responses and token consumption even when the application API remains compatible.

C:

“Swap every production endpoint to an untested model snapshot simultaneously” would violate the requirement. A model version update can change output structure, safety responses and token consumption even when the application API remains compatible.

Incorrect Answers

B:

“Canary evaluation remains within correctness and latency guardrails and rollback restores the last accepted version when thresholds are breached” is the required outcome of a working control, not an action that weakens it. A model version update can change output structure, safety responses and token consumption even when the application API remains compatible. Confirm that canary evaluation remains within correctness and latency guardrails and rollback restores the last accepted version when thresholds are breached.

D:

“Inspect records that explain the affected process, then check the result described in this case: A retail assistant is upgrading its model snapshot but a new version occasionally omits fields required by” adds a relevant safeguard or verification step rather than weakening the solution. A model version update can change output structure, safety responses and token consumption even when the application API remains compatible. Confirm that canary evaluation remains within correctness and latency guardrails and rollback restores the last accepted version when thresholds are breached.

E:

Because a retail assistant is upgrading its model snapshot but a new version occasionally omits fields required by an order API, “Roll out the model version behind a small monitored canary, compare frozen evaluation cohorts, and maintain a rehearsed rollback path” is the controlled implementation, not an unsafe workaround. A model version update can change output structure, safety responses and token consumption even when the application API remains compatible.

Question 166

Production requirement: A healthcare summarizer sees unexpected refusal messages after a model deployment revision in staging. Which next change most directly addresses the reported technical risk?

  1. Treat matching endpoint URLs as evidence of behavioral equivalence
  2. Suppress regression errors during version rollout
  3. Roll out the model version behind a small monitored canary, compare frozen evaluation cohorts, and maintain a rehearsed rollback path
  4. Apply the proposed setting to all connected workloads before testing the case-specific boundary: a healthcare summarizer sees unexpected refusal messages after a model deployment revision in staging

Explanation

Correct Answer

C:

Roll out the model version behind a small monitored canary, compare frozen evaluation cohorts, and maintain a rehearsed rollback path. Canary evaluation remains within correctness and latency guardrails and rollback restores the last accepted version when thresholds are breached.

Incorrect Answers

A:

“Treat matching endpoint URLs as evidence of behavioral equivalence” does not implement the control that the facts call for. Instead, roll out the model version behind a small monitored canary, compare frozen evaluation cohorts, and maintain a rehearsed rollback path.

B:

“Suppress regression errors during version rollout” does not implement the control that the facts call for. Instead, roll out the model version behind a small monitored canary, compare frozen evaluation cohorts, and maintain a rehearsed rollback path.

D:

“Apply the proposed setting to all connected workloads before testing the case-specific boundary: a healthcare summarizer sees unexpected refusal messages after a model deployment revision in staging” does not implement the control that the facts call for. Instead, roll out the model version behind a small monitored canary, compare frozen evaluation cohorts, and maintain a rehearsed rollback path.

Question 167

A team is investigating this task: A healthcare summarizer sees unexpected refusal messages after a model deployment revision in staging. Which explanation best captures the key behavior of this architecture?

  1. The most powerful or least restricted model is always the safest choice regardless of task conditions
  2. Successful provisioning by itself proves all security, output, and operational constraints are satisfied
  3. The fact that the team started work is enough to prove correctness for this exact case: a healthcare summarizer sees unexpected refusal messages after a model deployment revision in staging
  4. A model version update can change output structure, safety responses and token consumption even when the application API remains compatible

Explanation

Correct Answer

D:

A model version update can change output structure, safety responses and token consumption even when the application API remains compatible. Canary evaluation remains within correctness and latency guardrails and rollback restores the last accepted version when thresholds are breached.

Incorrect Answers

A:

“The most powerful or least restricted model is always the safest choice regardless of task conditions” would not be the most direct first check for this failure. A model version update can change output structure, safety responses and token consumption even when the application API remains compatible.

B:

“Successful provisioning by itself proves all security, output, and operational constraints are satisfied” would not be the most direct first check for this failure. A model version update can change output structure, safety responses and token consumption even when the application API remains compatible.

C:

“The fact that the team started work is enough to prove correctness for this exact case: a healthcare summarizer sees unexpected refusal messages after a model deployment revision in staging” would not be the most direct first check for this failure. A model version update can change output structure, safety responses and token consumption even when the application API remains compatible.

Question 168

Situation: A healthcare summarizer sees unexpected refusal messages after a model deployment revision in staging. Which result would demonstrate that the proposed remedy works end to end?

  1. The operator reports success without reproducing the observed behavior: a healthcare summarizer sees unexpected refusal messages after a model deployment revision in staging
  2. A project dashboard remains green, although the affected request, output and permissions were not checked
  3. Canary evaluation remains within correctness and latency guardrails and rollback restores the last accepted version when thresholds are breached
  4. The team closes a change ticket without replaying a representative positive and negative test

Explanation

Correct Answer

C:

A healthcare summarizer sees unexpected refusal messages after a model deployment revision in staging. Canary evaluation remains within correctness and latency guardrails and rollback restores the last accepted version when thresholds are breached. Roll out the model version behind a small monitored canary, compare frozen evaluation cohorts, and maintain a rehearsed rollback path.

Incorrect Answers

A:

“The operator reports success without reproducing the observed behavior: a healthcare summarizer sees unexpected refusal messages after a model deployment revision in staging” alone does not establish all the required behavior. Canary evaluation remains within correctness and latency guardrails and rollback restores the last accepted version when thresholds are breached.

B:

Because a healthcare summarizer sees unexpected refusal messages after a model deployment revision in staging, “A project dashboard remains green, although the affected request, output and permissions were not checked” would not meet the requirement. Canary evaluation remains within correctness and latency guardrails and rollback restores the last accepted version when thresholds are breached.

D:

Because a healthcare summarizer sees unexpected refusal messages after a model deployment revision in staging, “The team closes a change ticket without replaying a representative positive and negative test” alone does not establish all the required behavior. Canary evaluation remains within correctness and latency guardrails and rollback restores the last accepted version when thresholds are breached.

Question 169

Architecture case: A healthcare summarizer sees unexpected refusal messages after a model deployment revision in staging. What evidence should the engineer correlate to verify the actual failure cause?

  1. Restart every affected component before collecting request or tool traces
  2. Read only the broad service-health summary and skip actual workload evidence
  3. Assume the general service is at fault without checking the affected operation in this case: a healthcare summarizer sees unexpected refusal messages after a model deployment revision in staging
  4. Inspect pinned model versions, routing percentages, test-suite results, safety regressions, latency, spend and deployment-revision logs

Explanation

Correct Answer

D:

Canary evaluation remains within correctness and latency guardrails and rollback restores the last accepted version when thresholds are breached. Roll out the model version behind a small monitored canary, compare frozen evaluation cohorts, and maintain a rehearsed rollback path.

Incorrect Answers

A:

“Restart every affected component before collecting request or tool traces” alone does not establish all the required behavior. Canary evaluation remains within correctness and latency guardrails and rollback restores the last accepted version when thresholds are breached.

B:

“Read only the broad service-health summary and skip actual workload evidence” would not meet the requirement. Canary evaluation remains within correctness and latency guardrails and rollback restores the last accepted version when thresholds are breached.

C:

“Assume the general service is at fault without checking the affected operation in this case: a healthcare summarizer sees unexpected refusal messages after a model deployment revision in staging” would not meet the requirement. Canary evaluation remains within correctness and latency guardrails and rollback restores the last accepted version when thresholds are breached.

Question 170

Production requirement: A healthcare summarizer sees unexpected refusal messages after a model deployment revision in staging. Which TWO decisions would undermine the required system boundary? Select TWO answers.

  1. Swap every production endpoint to an untested model snapshot simultaneously
  2. Canary evaluation remains within correctness and latency guardrails and rollback restores the last accepted version when thresholds are breached
  3. Remove the previous model version before observing the canary
  4. Inspect records that explain the affected process, then check the result described in this case: A healthcare summarizer sees unexpected refusal messages after a model deployment revision in staging
  5. Roll out the model version behind a small monitored canary, compare frozen evaluation cohorts, and maintain a rehearsed rollback path

Explanation

Correct Answer

A:

“Swap every production endpoint to an untested model snapshot simultaneously” would violate the requirement.

C:

“Remove the previous model version before observing the canary” would violate the requirement. The appropriate control instead is to roll out the model version behind a small monitored canary, compare frozen evaluation cohorts, and maintain a rehearsed rollback path.

Incorrect Answers

B:

“Canary evaluation remains within correctness and latency guardrails and rollback restores the last accepted version when thresholds are breached” is the required outcome of a working control, not an action that weakens it.

D:

“Inspect records that explain the affected process, then check the result described in this case: A healthcare summarizer sees unexpected refusal messages after a model deployment revision in staging” adds a relevant safeguard or verification step rather than weakening the solution. Confirm that canary evaluation remains within correctness and latency guardrails and rollback restores the last accepted version when thresholds are breached.

E:

“Roll out the model version behind a small monitored canary, compare frozen evaluation cohorts, and maintain a rehearsed rollback path” is the controlled implementation, not an unsafe workaround.

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