Microsoft AI-103 Practice Test 7 - 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 7

Question 60

Situation: A media-processing job uses an identity-enabled compute service and must rotate downstream credentials without shipping new container images. Which TWO proposed practices create material safety, correctness, or reliability risks? Select TWO answers.

  1. Give every application identity read permission to all vaults in the subscription
  2. The deployed app retrieves only authorized secrets or search data while an identity without the role receives an auditable denial
  3. Use managed identity with minimal data-plane roles and protected secret references rather than embedding service keys in prompts or source code
  4. Inspect records that explain the affected process, then check the result described in this case: A media-processing job uses an identity-enabled compute service and must rotate downstream credentials without shipping new container images
  5. Commit an unrestricted AI service API key into the shared application repository

Explanation

Correct Answer

A:

Because a media-processing job uses an identity-enabled compute service and must rotate downstream credentials without shipping new container images, “Give every application identity read permission to all vaults in the subscription” would violate the requirement. Managed identities reduce long-lived credential distribution only if each downstream resource grants exactly the required operations.

E:

Because a media-processing job uses an identity-enabled compute service and must rotate downstream credentials without shipping new container images, this grants access or authority beyond the scope established in the case. “Commit an unrestricted AI service API key into the shared application repository” would violate the requirement. Managed identities reduce long-lived credential distribution only if each downstream resource grants exactly the required operations.

Incorrect Answers

B:

A media-processing job uses an identity-enabled compute service and must rotate downstream credentials without shipping new container images. “The deployed app retrieves only authorized secrets or search data while an identity without the role receives an auditable denial” is the required outcome of a working control, not an action that weakens it. Managed identities reduce long-lived credential distribution only if each downstream resource grants exactly the required operations. Confirm that the deployed app retrieves only authorized secrets or search data while an identity without the role receives an auditable denial.

C:

A media-processing job uses an identity-enabled compute service and must rotate downstream credentials without shipping new container images. “Use managed identity with minimal data-plane roles and protected secret references rather than embedding service keys in prompts or source code” is the controlled implementation, not an unsafe workaround. Managed identities reduce long-lived credential distribution only if each downstream resource grants exactly the required operations.

D:

“Inspect records that explain the affected process, then check the result described in this case: A media-processing job uses an identity-enabled compute service” adds a relevant safeguard or verification step rather than weakening the solution. Managed identities reduce long-lived credential distribution only if each downstream resource grants exactly the required operations.

Question 61

Architecture case: A delivery assistant launches for customers and hits rate limits when many users request parcel updates simultaneously. What configuration should the engineer choose for this workload?

  1. Measure workload token or request demand, configure bounded concurrency and backoff, and request suitable capacity with monitored cost limits
  2. Route every tenant to one limited deployment without admission control
  3. Apply the proposed setting to all connected workloads before testing the case-specific boundary: a delivery assistant launches for customers and hits rate limits when many users request parcel updates simultaneously
  4. Increase request concurrency without measuring model quota or cost

Explanation

Correct Answer

A:

Because a delivery assistant launches for customers and hits rate limits when many users request parcel updates simultaneously, rate limits and token capacity are distinct from model quality; transient throttling needs controlled retry while permanent request errors must fail safely. Peak load meets agreed success and latency targets without duplicate writes, unlimited retry storms or unexpected capacity overspend.

Incorrect Answers

B:

A delivery assistant launches for customers and hits rate limits when many users request parcel updates simultaneously. “Route every tenant to one limited deployment without admission control” does not implement the control that the facts call for. Rate limits and token capacity are distinct from model quality; transient throttling needs controlled retry while permanent request errors must fail safely. Instead, measure workload token or request demand, configure bounded concurrency and backoff, and request suitable capacity with monitored cost limits.

C:

“Apply the proposed setting to all connected workloads before testing the case-specific boundary: a delivery assistant launches for customers” does not implement the control that the facts call for. Rate limits and token capacity are distinct from model quality; transient throttling needs controlled retry while permanent request errors must fail safely. Instead, measure workload token or request demand, configure bounded concurrency and backoff, and request suitable capacity with monitored cost limits.

D:

Because a delivery assistant launches for customers and hits rate limits when many users request parcel updates simultaneously, “Increase request concurrency without measuring model quota or cost” does not implement the control that the facts call for. Rate limits and token capacity are distinct from model quality; transient throttling needs controlled retry while permanent request errors must fail safely. Instead, measure workload token or request demand, configure bounded concurrency and backoff, and request suitable capacity with monitored cost limits.

Question 62

Production requirement: A delivery assistant launches for customers and hits rate limits when many users request parcel updates simultaneously. What technical fact prevents the simplest shortcut from being reliable?

  1. Rate limits and token capacity are distinct from model quality; transient throttling needs controlled retry while permanent request errors must fail safely
  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 delivery assistant launches for customers and hits rate limits when many users request parcel updates simultaneously
  4. The most powerful or least restricted model is always the safest choice regardless of task conditions

Explanation

Correct Answer

A:

A delivery assistant launches for customers and hits rate limits when many users request parcel updates simultaneously. Rate limits and token capacity are distinct from model quality; transient throttling needs controlled retry while permanent request errors must fail safely. Measure workload token or request demand, configure bounded concurrency and backoff, and request suitable capacity with monitored cost limits. The decisive evidence is that peak load meets agreed success and latency targets without duplicate writes, unlimited retry storms or unexpected capacity overspend.

Incorrect Answers

B:

Because a delivery assistant launches for customers and hits rate limits when many users request parcel updates simultaneously, “Successful provisioning by itself proves all security, output, and operational constraints are satisfied” does not fully explain the decisive technical boundary in this case. Rate limits and token capacity are distinct from model quality; transient throttling needs controlled retry while permanent request errors must fail safely. The implementation must measure workload token or request demand, configure bounded concurrency and backoff, and request suitable capacity with monitored cost limits.

C:

“The fact that the team started work is enough to prove correctness for this exact case: a delivery assistant launches for customers” does not fully explain the decisive technical boundary in this case. Rate limits and token capacity are distinct from model quality; transient throttling needs controlled retry while permanent request errors must fail safely.

D:

“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. Rate limits and token capacity are distinct from model quality; transient throttling needs controlled retry while permanent request errors must fail safely. The implementation must measure workload token or request demand, configure bounded concurrency and backoff, and request suitable capacity with monitored cost limits.

Question 63

A team is investigating this task: A delivery assistant launches for customers and hits rate limits when many users request parcel updates simultaneously. What end-to-end test would distinguish successful operation from an installed configuration?

  1. A project dashboard remains green, although the affected request, output and permissions were not checked
  2. Peak load meets agreed success and latency targets without duplicate writes, unlimited retry storms or unexpected capacity overspend
  3. The operator reports success without reproducing the observed behavior: a delivery assistant launches for customers and hits rate limits when many users request parcel updates simultaneously
  4. The team closes a change ticket without replaying a representative positive and negative test

Explanation

Correct Answer

B:

A delivery assistant launches for customers and hits rate limits when many users request parcel updates simultaneously. Because a delivery assistant launches for customers and hits rate limits when many users request parcel updates simultaneously, rate limits and token capacity are distinct from model quality; transient throttling needs controlled retry while permanent request errors must fail safely. Peak load meets agreed success and latency targets without duplicate writes, unlimited retry storms or unexpected capacity overspend.

Incorrect Answers

A:

“A project dashboard remains green, although the affected request, output and permissions were not checked” would not meet the requirement. Peak load meets agreed success and latency targets without duplicate writes, unlimited retry storms or unexpected capacity overspend.

C:

“The operator reports success without reproducing the observed behavior: a delivery assistant launches for customers and hits rate limits when many users request parcel updates simultaneously” alone does not establish all the required behavior. Peak load meets agreed success and latency targets without duplicate writes, unlimited retry storms or unexpected capacity overspend. Rate limits and token capacity are distinct from model quality; transient throttling needs controlled retry while permanent request errors must fail safely.

D:

Because a delivery assistant launches for customers and hits rate limits when many users request parcel updates simultaneously, “The team closes a change ticket without replaying a representative positive and negative test” alone does not establish all the required behavior. Peak load meets agreed success and latency targets without duplicate writes, unlimited retry storms or unexpected capacity overspend.

Question 64

Situation: A delivery assistant launches for customers and hits rate limits when many users request parcel updates simultaneously. Which diagnostic investigation best isolates the issue before another change?

  1. Inspect rate-limit responses, token consumption, regional quota, concurrency, retry headers and actual request latency percentiles
  2. Restart every affected component before collecting request or tool traces
  3. Read only the broad service-health summary and skip actual workload evidence
  4. Assume the general service is at fault without checking the affected operation in this case: a delivery assistant launches for customers and hits rate limits when many users request parcel updates simultaneously

Explanation

Correct Answer

A:

Because a delivery assistant launches for customers and hits rate limits when many users request parcel updates simultaneously, inspect rate-limit responses, token consumption, regional quota, concurrency, retry headers and actual request latency percentiles. Rate limits and token capacity are distinct from model quality; transient throttling needs controlled retry while permanent request errors must fail safely. Peak load meets agreed success and latency targets without duplicate writes, unlimited retry storms or unexpected capacity overspend.

Incorrect Answers

B:

Because a delivery assistant launches for customers and hits rate limits when many users request parcel updates simultaneously, “Restart every affected component before collecting request or tool traces” would not be the most direct first check for this failure. Inspect rate-limit responses, token consumption, regional quota, concurrency, retry headers and actual request latency percentiles.

C:

A delivery assistant launches for customers and hits rate limits when many users request parcel updates simultaneously. “Read only the broad service-health summary and skip actual workload evidence” would not meet the requirement. Inspect rate-limit responses, token consumption, regional quota, concurrency, retry headers and actual request latency percentiles.

D:

“Assume the general service is at fault without checking the affected operation in this case: a delivery assistant launches for customers” would not meet the requirement. Inspect rate-limit responses, token consumption, regional quota, concurrency, retry headers and actual request latency percentiles.

Question 65

Architecture case: A delivery assistant launches for customers and hits rate limits when many users request parcel updates simultaneously. Which TWO shortcuts should be rejected for this scenario? Select TWO answers.

  1. Retry every 429 immediately in an infinite tight loop
  2. Hide all throttling errors by returning a fabricated successful generated answer
  3. Inspect records that explain the affected process, then check the result described in this case: A delivery assistant launches for customers and hits rate limits when many users request parcel updates simultaneously
  4. Measure workload token or request demand, configure bounded concurrency and backoff, and request suitable capacity with monitored cost limits
  5. Peak load meets agreed success and latency targets without duplicate writes, unlimited retry storms or unexpected capacity overspend

Explanation

Correct Answer

A:

A delivery assistant launches for customers and hits rate limits when many users request parcel updates simultaneously. “Retry every 429 immediately in an infinite tight loop” would violate the requirement. Rate limits and token capacity are distinct from model quality; transient throttling needs controlled retry while permanent request errors must fail safely.

B:

A delivery assistant launches for customers and hits rate limits when many users request parcel updates simultaneously. “Hide all throttling errors by returning a fabricated successful generated answer” would violate the requirement. Rate limits and token capacity are distinct from model quality; transient throttling needs controlled retry while permanent request errors must fail safely.

Incorrect Answers

C:

“Inspect records that explain the affected process, then check the result described in this case: A delivery assistant launches for customers” adds a relevant safeguard or verification step rather than weakening the solution. Rate limits and token capacity are distinct from model quality; transient throttling needs controlled retry while permanent request errors must fail safely. Confirm that peak load meets agreed success and latency targets without duplicate writes, unlimited retry storms or unexpected capacity overspend.

D:

A delivery assistant launches for customers and hits rate limits when many users request parcel updates simultaneously. “Measure workload token or request demand, configure bounded concurrency and backoff, and request suitable capacity with monitored cost limits” is the controlled implementation, not an unsafe workaround. Rate limits and token capacity are distinct from model quality; transient throttling needs controlled retry while permanent request errors must fail safely.

E:

“Peak load meets agreed success and latency targets without duplicate writes, unlimited retry storms or unexpected capacity overspend” is the required outcome of a working control, not an action that weakens it. Rate limits and token capacity are distinct from model quality; transient throttling needs controlled retry while permanent request errors must fail safely.

Question 66

Production requirement: A hospital summarization service bursts during shift changes while administrators must protect a predictable token budget. Which next change most directly addresses the reported technical risk?

  1. Apply the proposed setting to all connected workloads before testing the case-specific boundary: a hospital summarization service bursts during shift changes while administrators must protect a predictable token budget
  2. Measure workload token or request demand, configure bounded concurrency and backoff, and request suitable capacity with monitored cost limits
  3. Increase request concurrency without measuring model quota or cost
  4. Route every tenant to one limited deployment without admission control

Explanation

Correct Answer

B:

Measure workload token or request demand, configure bounded concurrency and backoff, and request suitable capacity with monitored cost limits. Confirm that peak load meets agreed success and latency targets without duplicate writes, unlimited retry storms or unexpected capacity overspend. If the result fails, rate limits and token capacity are distinct from model quality; transient throttling needs controlled retry while permanent request errors must fail safely.

Incorrect Answers

A:

“Apply the proposed setting to all connected workloads before testing the case-specific boundary: a hospital summarization service bursts during shift changes while administrators must protect a” does not implement the control that the facts call for. Instead, measure workload token or request demand, configure bounded concurrency and backoff, and request suitable capacity with monitored cost limits.

C:

“Increase request concurrency without measuring model quota or cost” does not implement the control that the facts call for. Instead, measure workload token or request demand, configure bounded concurrency and backoff, and request suitable capacity with monitored cost limits.

D:

“Route every tenant to one limited deployment without admission control” does not implement the control that the facts call for. Instead, measure workload token or request demand, configure bounded concurrency and backoff, and request suitable capacity with monitored cost limits.

Question 67

A team is investigating this task: A hospital summarization service bursts during shift changes while administrators must protect a predictable token budget. Which explanation best captures the key behavior of this architecture?

  1. The fact that the team started work is enough to prove correctness for this exact case: a hospital summarization service bursts during shift changes while administrators must protect a predictable token budget
  2. Rate limits and token capacity are distinct from model quality; transient throttling needs controlled retry while permanent request errors must fail safely
  3. Successful provisioning by itself proves all security, output, and operational constraints are satisfied
  4. The most powerful or least restricted model is always the safest choice regardless of task conditions

Explanation

Correct Answer

B:

Rate limits and token capacity are distinct from model quality; transient throttling needs controlled retry while permanent request errors must fail safely. Peak load meets agreed success and latency targets without duplicate writes, unlimited retry storms or unexpected capacity overspend.

Incorrect Answers

A:

“The fact that the team started work is enough to prove correctness for this exact case: a hospital summarization service bursts during shift changes while administrators must protect a predictable token” would not be the most direct first check for this failure. Rate limits and token capacity are distinct from model quality; transient throttling needs controlled retry while permanent request errors must fail safely.

C:

“Successful provisioning by itself proves all security, output, and operational constraints are satisfied” would not be the most direct first check for this failure. Rate limits and token capacity are distinct from model quality; transient throttling needs controlled retry while permanent request errors must fail safely.

D:

“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. Rate limits and token capacity are distinct from model quality; transient throttling needs controlled retry while permanent request errors must fail safely.

Question 68

Situation: A hospital summarization service bursts during shift changes while administrators must protect a predictable token budget. Which result would demonstrate that the proposed remedy works end to end?

  1. The operator reports success without reproducing the observed behavior: a hospital summarization service bursts during shift changes while administrators must protect a predictable token budget
  2. The team closes a change ticket without replaying a representative positive and negative test
  3. A project dashboard remains green, although the affected request, output and permissions were not checked
  4. Peak load meets agreed success and latency targets without duplicate writes, unlimited retry storms or unexpected capacity overspend

Explanation

Correct Answer

D:

Peak load meets agreed success and latency targets without duplicate writes, unlimited retry storms or unexpected capacity overspend. Measure workload token or request demand, configure bounded concurrency and backoff, and request suitable capacity with monitored cost limits.

Incorrect Answers

A:

“The operator reports success without reproducing the observed behavior: a hospital summarization service bursts during shift changes while administrators must protect a predictable token budget” alone does not establish all the required behavior. Peak load meets agreed success and latency targets without duplicate writes, unlimited retry storms or unexpected capacity overspend.

B:

A hospital summarization service bursts during shift changes while administrators must protect a predictable token budget. “The team closes a change ticket without replaying a representative positive and negative test” alone does not establish all the required behavior. Peak load meets agreed success and latency targets without duplicate writes, unlimited retry storms or unexpected capacity overspend.

C:

A hospital summarization service bursts during shift changes while administrators must protect a predictable token budget. “A project dashboard remains green, although the affected request, output and permissions were not checked” would not meet the requirement. Peak load meets agreed success and latency targets without duplicate writes, unlimited retry storms or unexpected capacity overspend.

Question 69

Architecture case: A hospital summarization service bursts during shift changes while administrators must protect a predictable token budget. What evidence should the engineer correlate to verify the actual failure cause?

  1. Restart every affected component before collecting request or tool traces
  2. Assume the general service is at fault without checking the affected operation in this case: a hospital summarization service bursts during shift changes while administrators must protect a predictable token budget
  3. Read only the broad service-health summary and skip actual workload evidence
  4. Inspect rate-limit responses, token consumption, regional quota, concurrency, retry headers and actual request latency percentiles

Explanation

Correct Answer

D:

Peak load meets agreed success and latency targets without duplicate writes, unlimited retry storms or unexpected capacity overspend. If this test fails, rate limits and token capacity are distinct from model quality; transient throttling needs controlled retry while permanent request errors must fail safely.

Incorrect Answers

A:

“Restart every affected component before collecting request or tool traces” alone does not establish all the required behavior. Peak load meets agreed success and latency targets without duplicate writes, unlimited retry storms or unexpected capacity overspend.

B:

“Assume the general service is at fault without checking the affected operation in this case: a hospital summarization service bursts during shift changes while administrators must protect a predictable” would not meet the requirement. Peak load meets agreed success and latency targets without duplicate writes, unlimited retry storms or unexpected capacity overspend.

C:

“Read only the broad service-health summary and skip actual workload evidence” would not meet the requirement. Peak load meets agreed success and latency targets without duplicate writes, unlimited retry storms or unexpected capacity overspend.

Question 70

Production requirement: A hospital summarization service bursts during shift changes while administrators must protect a predictable token budget. Which TWO decisions would undermine the required system boundary? Select TWO answers.

  1. Peak load meets agreed success and latency targets without duplicate writes, unlimited retry storms or unexpected capacity overspend
  2. Retry every 429 immediately in an infinite tight loop
  3. Measure workload token or request demand, configure bounded concurrency and backoff, and request suitable capacity with monitored cost limits
  4. Inspect records that explain the affected process, then check the result described in this case: A hospital summarization service bursts during shift changes while administrators must protect a predictable token budget
  5. Hide all throttling errors by returning a fabricated successful generated answer

Explanation

Correct Answer

B:

“Retry every 429 immediately in an infinite tight loop” would violate the requirement.

E:

“Hide all throttling errors by returning a fabricated successful generated answer” would violate the requirement.

Incorrect Answers

A:

“Peak load meets agreed success and latency targets without duplicate writes, unlimited retry storms or unexpected capacity overspend” is the required outcome of a working control, not an action that weakens it. Confirm that peak load meets agreed success and latency targets without duplicate writes, unlimited retry storms or unexpected capacity overspend.

C:

“Measure workload token or request demand, configure bounded concurrency and backoff, and request suitable capacity with monitored cost limits” is the controlled implementation, not an unsafe workaround. Confirm that peak load meets agreed success and latency targets without duplicate writes, unlimited retry storms or unexpected capacity overspend.

D:

“Inspect records that explain the affected process, then check the result described in this case: A hospital summarization service bursts during shift changes while administrators must protect a” adds a relevant safeguard or verification step rather than weakening the solution.

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