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

Question 360

Situation: A sales assistant can view a quote but must request manager approval before submitting a refund. Which TWO proposed practices create material safety, correctness, or reliability risks? Select TWO answers.

  1. Authorized read requests succeed; unapproved writes, cross-tenant identifiers and malformed arguments are rejected with traceable policy reasons
  2. Define a narrow validated tool schema, restrict its identity permissions and require explicit authorization for irreversible or high-impact tool calls
  3. Expose a general administrator tool to all customers because arguments are described in the prompt
  4. Inspect records that explain the affected process, then check the result described in this case: A sales assistant can view a quote but must request manager approval before submitting a refund
  5. Execute any generated payment or deletion call without a human approval checkpoint

Explanation

Correct Answer

C:

A sales assistant can view a quote but must request manager approval before submitting a refund. “Expose a general administrator tool to all customers because arguments are described in the prompt” would violate the requirement. A model-proposed tool call is untrusted until its arguments, caller authority, resource boundary and side-effect class are checked by the application.

E:

A sales assistant can view a quote but must request manager approval before submitting a refund. “Execute any generated payment or deletion call without a human approval checkpoint” would violate the requirement. A model-proposed tool call is untrusted until its arguments, caller authority, resource boundary and side-effect class are checked by the application.

Incorrect Answers

A:

Because a sales assistant can view a quote but must request manager approval before submitting a refund, “Authorized read requests succeed; unapproved writes, cross-tenant identifiers and malformed arguments are rejected with traceable policy reasons” is the required outcome of a working control, not an action that weakens it. A model-proposed tool call is untrusted until its arguments, caller authority, resource boundary and side-effect class are checked by the application. Confirm that authorized read requests succeed; unapproved writes, cross-tenant identifiers and malformed arguments are rejected with traceable policy reasons.

B:

Because a sales assistant can view a quote but must request manager approval before submitting a refund, “Define a narrow validated tool schema, restrict its identity permissions and require explicit authorization for irreversible or high-impact tool calls” is the controlled implementation, not an unsafe workaround. A model-proposed tool call is untrusted until its arguments, caller authority, resource boundary and side-effect class are checked by the application.

D:

“Inspect records that explain the affected process, then check the result described in this case: A sales assistant can view a quote but must request manager approval before submitting a refund” adds a relevant safeguard or verification step rather than weakening the solution. A model-proposed tool call is untrusted until its arguments, caller authority, resource boundary and side-effect class are checked by the application. Confirm that authorized read requests succeed; unapproved writes, cross-tenant identifiers and malformed arguments are rejected with traceable policy reasons.

Question 361

Architecture case: A hospital scheduling agent may read appointment slots but cannot cancel another patient’s appointment without explicit authority. What configuration should the engineer choose for this workload?

  1. Define a narrow validated tool schema, restrict its identity permissions and require explicit authorization for irreversible or high-impact tool calls
  2. Trust model JSON syntax alone as authorization
  3. Apply the proposed setting to all connected workloads before testing the case-specific boundary: a hospital scheduling agent may read appointment slots but cannot cancel another patient’s appointment without explicit authority
  4. Pass user-submitted arbitrary resource IDs directly into a privileged action

Explanation

Correct Answer

A:

A model-proposed tool call is untrusted until its arguments, caller authority, resource boundary and side-effect class are checked by the application. Confirm that authorized read requests succeed; unapproved writes, cross-tenant identifiers and malformed arguments are rejected with traceable policy reasons.

Incorrect Answers

B:

“Trust model JSON syntax alone as authorization” does not implement the control that the facts call for. A model-proposed tool call is untrusted until its arguments, caller authority, resource boundary and side-effect class are checked by the application. Instead, define a narrow validated tool schema, restrict its identity permissions and require explicit authorization for irreversible or high-impact tool calls.

C:

“Apply the proposed setting to all connected workloads before testing the case-specific boundary: a hospital scheduling agent may read appointment slots but cannot cancel another patient’s appointment” does not implement the control that the facts call for. A model-proposed tool call is untrusted until its arguments, caller authority, resource boundary and side-effect class are checked by the application. Instead, define a narrow validated tool schema, restrict its identity permissions and require explicit authorization for irreversible or high-impact tool calls.

D:

A hospital scheduling agent may read appointment slots but cannot cancel another patient’s appointment without explicit authority. “Pass user-submitted arbitrary resource IDs directly into a privileged action” does not implement the control that the facts call for. A model-proposed tool call is untrusted until its arguments, caller authority, resource boundary and side-effect class are checked by the application. Instead, define a narrow validated tool schema, restrict its identity permissions and require explicit authorization for irreversible or high-impact tool calls.

Question 362

Production requirement: A hospital scheduling agent may read appointment slots but cannot cancel another patient’s appointment without explicit authority. What technical fact prevents the simplest shortcut from being reliable?

  1. A model-proposed tool call is untrusted until its arguments, caller authority, resource boundary and side-effect class are checked by the application
  2. The fact that the team started work is enough to prove correctness for this exact case: a hospital scheduling agent may read appointment slots but cannot cancel another patient’s appointment without explicit authority
  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

A:

A model-proposed tool call is untrusted until its arguments, caller authority, resource boundary and side-effect class are checked by the application. Define a narrow validated tool schema, restrict its identity permissions and require explicit authorization for irreversible or high-impact tool calls.

Incorrect Answers

B:

“The fact that the team started work is enough to prove correctness for this exact case: a hospital scheduling agent may read appointment slots but cannot cancel another patient’s appointment without” does not fully explain the decisive technical boundary in this case. A model-proposed tool call is untrusted until its arguments, caller authority, resource boundary and side-effect class are checked by the application. The implementation must define a narrow validated tool schema, restrict its identity permissions and require explicit authorization for irreversible or high-impact tool calls.

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-proposed tool call is untrusted until its arguments, caller authority, resource boundary and side-effect class are checked by the application. The implementation must define a narrow validated tool schema, restrict its identity permissions and require explicit authorization for irreversible or high-impact tool calls.

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. A model-proposed tool call is untrusted until its arguments, caller authority, resource boundary and side-effect class are checked by the application.

Question 363

A team is investigating this task: A hospital scheduling agent may read appointment slots but cannot cancel another patient’s appointment without explicit authority. What end-to-end test would distinguish successful operation from an installed configuration?

  1. The operator reports success without reproducing the observed behavior: a hospital scheduling agent may read appointment slots but cannot cancel another patient’s appointment without explicit authority
  2. A project dashboard remains green, although the affected request, output and permissions were not checked
  3. Authorized read requests succeed; unapproved writes, cross-tenant identifiers and malformed arguments are rejected with traceable policy reasons
  4. The team closes a change ticket without replaying a representative positive and negative test

Explanation

Correct Answer

C:

A model-proposed tool call is untrusted until its arguments, caller authority, resource boundary and side-effect class are checked by the application. Authorized read requests succeed; unapproved writes, cross-tenant identifiers and malformed arguments are rejected with traceable policy reasons.

Incorrect Answers

A:

“The operator reports success without reproducing the observed behavior: a hospital scheduling agent may read appointment slots but cannot cancel another patient’s appointment without explicit authority” alone does not establish all the required behavior. Authorized read requests succeed; unapproved writes, cross-tenant identifiers and malformed arguments are rejected with traceable policy reasons. A model-proposed tool call is untrusted until its arguments, caller authority, resource boundary and side-effect class are checked by the application.

B:

Because a hospital scheduling agent may read appointment slots but cannot cancel another patient’s appointment without explicit authority, “A project dashboard remains green, although the affected request, output and permissions were not checked” would not meet the requirement. Authorized read requests succeed; unapproved writes, cross-tenant identifiers and malformed arguments are rejected with traceable policy reasons.

D:

“The team closes a change ticket without replaying a representative positive and negative test” alone does not establish all the required behavior. Authorized read requests succeed; unapproved writes, cross-tenant identifiers and malformed arguments are rejected with traceable policy reasons. A model-proposed tool call is untrusted until its arguments, caller authority, resource boundary and side-effect class are checked by the application.

Question 364

Situation: A hospital scheduling agent may read appointment slots but cannot cancel another patient’s appointment without explicit authority. Which diagnostic investigation best isolates the issue before another change?

  1. Read only the broad service-health summary and skip actual workload evidence
  2. Restart every affected component before collecting request or tool traces
  3. Inspect function schema constraints, caller identity claims, effective tool permissions, validation errors and approval-event logs
  4. Assume the general service is at fault without checking the affected operation in this case: a hospital scheduling agent may read appointment slots but cannot cancel another patient’s appointment without explicit authority

Explanation

Correct Answer

C:

Inspect function schema constraints, caller identity claims, effective tool permissions, validation errors and approval-event logs. A model-proposed tool call is untrusted until its arguments, caller authority, resource boundary and side-effect class are checked by the application. Authorized read requests succeed; unapproved writes, cross-tenant identifiers and malformed arguments are rejected with traceable policy reasons.

Incorrect Answers

A:

A hospital scheduling agent may read appointment slots but cannot cancel another patient’s appointment without explicit authority. “Read only the broad service-health summary and skip actual workload evidence” would not meet the requirement. Inspect function schema constraints, caller identity claims, effective tool permissions, validation errors and approval-event logs. A model-proposed tool call is untrusted until its arguments, caller authority, resource boundary and side-effect class are checked by the application.

B:

Because a hospital scheduling agent may read appointment slots but cannot cancel another patient’s appointment without explicit authority, “Restart every affected component before collecting request or tool traces” would not be the most direct first check for this failure. Inspect function schema constraints, caller identity claims, effective tool permissions, validation errors and approval-event logs.

D:

“Assume the general service is at fault without checking the affected operation in this case: a hospital scheduling agent may read appointment slots but cannot cancel another patient’s appointment without” would not meet the requirement. Inspect function schema constraints, caller identity claims, effective tool permissions, validation errors and approval-event logs. A model-proposed tool call is untrusted until its arguments, caller authority, resource boundary and side-effect class are checked by the application.

Question 365

Architecture case: A hospital scheduling agent may read appointment slots but cannot cancel another patient’s appointment without explicit authority. Which TWO shortcuts should be rejected for this scenario? Select TWO answers.

  1. Expose a general administrator tool to all customers because arguments are described in the prompt
  2. Inspect records that explain the affected process, then check the result described in this case: A hospital scheduling agent may read appointment slots but cannot cancel another patient’s appointment without explicit authority
  3. Execute any generated payment or deletion call without a human approval checkpoint
  4. Authorized read requests succeed; unapproved writes, cross-tenant identifiers and malformed arguments are rejected with traceable policy reasons
  5. Define a narrow validated tool schema, restrict its identity permissions and require explicit authorization for irreversible or high-impact tool calls

Explanation

Correct Answer

A:

“Expose a general administrator tool to all customers because arguments are described in the prompt” would violate the requirement. A model-proposed tool call is untrusted until its arguments, caller authority, resource boundary and side-effect class are checked by the application.

C:

Because a hospital scheduling agent may read appointment slots but cannot cancel another patient’s appointment without explicit authority, “Execute any generated payment or deletion call without a human approval checkpoint” would violate the requirement. A model-proposed tool call is untrusted until its arguments, caller authority, resource boundary and side-effect class are checked by the application.

Incorrect Answers

B:

“Inspect records that explain the affected process, then check the result described in this case: A hospital scheduling agent may read appointment slots but cannot cancel another patient’s appointment” adds a relevant safeguard or verification step rather than weakening the solution. A model-proposed tool call is untrusted until its arguments, caller authority, resource boundary and side-effect class are checked by the application.

D:

Because a hospital scheduling agent may read appointment slots but cannot cancel another patient’s appointment without explicit authority, “Authorized read requests succeed; unapproved writes, cross-tenant identifiers and malformed arguments are rejected with traceable policy reasons” is the required outcome of a working control, not an action that weakens it. A model-proposed tool call is untrusted until its arguments, caller authority, resource boundary and side-effect class are checked by the application. Confirm that authorized read requests succeed; unapproved writes, cross-tenant identifiers and malformed arguments are rejected with traceable policy reasons.

E:

“Define a narrow validated tool schema, restrict its identity permissions and require explicit authorization for irreversible or high-impact tool calls” is the controlled implementation, not an unsafe workaround. A model-proposed tool call is untrusted until its arguments, caller authority, resource boundary and side-effect class are checked by the application.

Question 366

Production requirement: A support bot reads cloud deployment status, and administrators want only a separate role to restart production services. 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 support bot reads cloud deployment status, and administrators want only a separate role to restart production services
  2. Define a narrow validated tool schema, restrict its identity permissions and require explicit authorization for irreversible or high-impact tool calls
  3. Trust model JSON syntax alone as authorization
  4. Pass user-submitted arbitrary resource IDs directly into a privileged action

Explanation

Correct Answer

B:

Define a narrow validated tool schema, restrict its identity permissions and require explicit authorization for irreversible or high-impact tool calls. Confirm that authorized read requests succeed; unapproved writes, cross-tenant identifiers and malformed arguments are rejected with traceable policy reasons. If the result fails, a model-proposed tool call is untrusted until its arguments, caller authority, resource boundary and side-effect class are checked by the application.

Incorrect Answers

A:

“Apply the proposed setting to all connected workloads before testing the case-specific boundary: a support bot reads cloud deployment status” does not implement the control that the facts call for. Instead, define a narrow validated tool schema, restrict its identity permissions and require explicit authorization for irreversible or high-impact tool calls.

C:

“Trust model JSON syntax alone as authorization” does not implement the control that the facts call for. Instead, define a narrow validated tool schema, restrict its identity permissions and require explicit authorization for irreversible or high-impact tool calls.

D:

“Pass user-submitted arbitrary resource IDs directly into a privileged action” does not implement the control that the facts call for. Instead, define a narrow validated tool schema, restrict its identity permissions and require explicit authorization for irreversible or high-impact tool calls.

Question 367

A team is investigating this task: A support bot reads cloud deployment status, and administrators want only a separate role to restart production services. Which explanation best captures the key behavior of this architecture?

  1. Successful provisioning by itself proves all security, output, and operational constraints are satisfied
  2. The fact that the team started work is enough to prove correctness for this exact case: a support bot reads cloud deployment status, and administrators want only a separate role to restart production services
  3. The most powerful or least restricted model is always the safest choice regardless of task conditions
  4. A model-proposed tool call is untrusted until its arguments, caller authority, resource boundary and side-effect class are checked by the application

Explanation

Correct Answer

D:

A support bot reads cloud deployment status, and administrators want only a separate role to restart production services. A model-proposed tool call is untrusted until its arguments, caller authority, resource boundary and side-effect class are checked by the application. Authorized read requests succeed; unapproved writes, cross-tenant identifiers and malformed arguments are rejected with traceable policy reasons.

Incorrect Answers

A:

“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-proposed tool call is untrusted until its arguments, caller authority, resource boundary and side-effect class are checked by the application.

B:

“The fact that the team started work is enough to prove correctness for this exact case: a support bot reads cloud deployment status” would not be the most direct first check for this failure. A model-proposed tool call is untrusted until its arguments, caller authority, resource boundary and side-effect class are checked by the application.

C:

“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-proposed tool call is untrusted until its arguments, caller authority, resource boundary and side-effect class are checked by the application.

Question 368

Situation: A support bot reads cloud deployment status, and administrators want only a separate role to restart production services. Which result would demonstrate that the proposed remedy works end to end?

  1. The operator reports success without reproducing the observed behavior: a support bot reads cloud deployment status, and administrators want only a separate role to restart production services
  2. Authorized read requests succeed; unapproved writes, cross-tenant identifiers and malformed arguments are rejected with traceable policy reasons
  3. A project dashboard remains green, although the affected request, output and permissions were not checked
  4. The team closes a change ticket without replaying a representative positive and negative test

Explanation

Correct Answer

B:

Authorized read requests succeed; unapproved writes, cross-tenant identifiers and malformed arguments are rejected with traceable policy reasons. If this test fails, a model-proposed tool call is untrusted until its arguments, caller authority, resource boundary and side-effect class are checked by the application.

Incorrect Answers

A:

“The operator reports success without reproducing the observed behavior: a support bot reads cloud deployment status, and administrators want only a separate role to restart production services” alone does not establish all the required behavior. Authorized read requests succeed; unapproved writes, cross-tenant identifiers and malformed arguments are rejected with traceable policy reasons.

C:

A support bot reads cloud deployment status, and administrators want only a separate role to restart production services. “A project dashboard remains green, although the affected request, output and permissions were not checked” would not meet the requirement. Authorized read requests succeed; unapproved writes, cross-tenant identifiers and malformed arguments are rejected with traceable policy reasons.

D:

A support bot reads cloud deployment status, and administrators want only a separate role to restart production services. “The team closes a change ticket without replaying a representative positive and negative test” alone does not establish all the required behavior. Authorized read requests succeed; unapproved writes, cross-tenant identifiers and malformed arguments are rejected with traceable policy reasons.

Question 369

Architecture case: A support bot reads cloud deployment status, and administrators want only a separate role to restart production services. What evidence should the engineer correlate to verify the actual failure cause?

  1. Inspect function schema constraints, caller identity claims, effective tool permissions, validation errors and approval-event logs
  2. Assume the general service is at fault without checking the affected operation in this case: a support bot reads cloud deployment status, and administrators want only a separate role to restart production services
  3. Read only the broad service-health summary and skip actual workload evidence
  4. Restart every affected component before collecting request or tool traces

Explanation

Correct Answer

A:

Authorized read requests succeed; unapproved writes, cross-tenant identifiers and malformed arguments are rejected with traceable policy reasons. Define a narrow validated tool schema, restrict its identity permissions and require explicit authorization for irreversible or high-impact tool calls.

Incorrect Answers

B:

“Assume the general service is at fault without checking the affected operation in this case: a support bot reads cloud deployment status” would not meet the requirement. Authorized read requests succeed; unapproved writes, cross-tenant identifiers and malformed arguments are rejected with traceable policy reasons.

C:

“Read only the broad service-health summary and skip actual workload evidence” would not meet the requirement. Authorized read requests succeed; unapproved writes, cross-tenant identifiers and malformed arguments are rejected with traceable policy reasons.

D:

“Restart every affected component before collecting request or tool traces” alone does not establish all the required behavior. Authorized read requests succeed; unapproved writes, cross-tenant identifiers and malformed arguments are rejected with traceable policy reasons.

Question 370

Production requirement: A support bot reads cloud deployment status, and administrators want only a separate role to restart production services. Which TWO decisions would undermine the required system boundary? Select TWO answers.

  1. Execute any generated payment or deletion call without a human approval checkpoint
  2. Inspect records that explain the affected process, then check the result described in this case: A support bot reads cloud deployment status, and administrators want only a separate role to restart production services
  3. Authorized read requests succeed; unapproved writes, cross-tenant identifiers and malformed arguments are rejected with traceable policy reasons
  4. Define a narrow validated tool schema, restrict its identity permissions and require explicit authorization for irreversible or high-impact tool calls
  5. Expose a general administrator tool to all customers because arguments are described in the prompt

Explanation

Correct Answer

A:

“Execute any generated payment or deletion call without a human approval checkpoint” would violate the requirement.

E:

“Expose a general administrator tool to all customers because arguments are described in the prompt” would violate the requirement. The appropriate control instead is to define a narrow validated tool schema, restrict its identity permissions and require explicit authorization for irreversible or high-impact tool calls.

Incorrect Answers

B:

“Inspect records that explain the affected process, then check the result described in this case: A support bot reads cloud deployment status” adds a relevant safeguard or verification step rather than weakening the solution. Confirm that authorized read requests succeed; unapproved writes, cross-tenant identifiers and malformed arguments are rejected with traceable policy reasons.

C:

“Authorized read requests succeed; unapproved writes, cross-tenant identifiers and malformed arguments are rejected with traceable policy reasons” is the required outcome of a working control, not an action that weakens it. Confirm that authorized read requests succeed; unapproved writes, cross-tenant identifiers and malformed arguments are rejected with traceable policy reasons.

D:

“Define a narrow validated tool schema, restrict its identity permissions and require explicit authorization for irreversible or high-impact tool calls” is the controlled implementation, not an unsafe workaround.

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