Pass Microsoft AI-103 Exam in First Attempt Guaranteed!
Get 100% Latest Exam Questions, Accurate & Verified Answers!
30 Days Free Updates, Instant Download!
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.
Explanation
Correct Answer
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.
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
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.
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.
“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?
Explanation
Correct Answer
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
“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.
“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.
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?
Explanation
Correct Answer
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
“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.
“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.
“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?
Explanation
Correct Answer
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
“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.
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.
“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?
Explanation
Correct Answer
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 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.
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.
“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.
Explanation
Correct Answer
“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.
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
“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.
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.
“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?
Explanation
Correct Answer
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
“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.
“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.
“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?
Explanation
Correct Answer
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
“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.
“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.
“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?
Explanation
Correct Answer
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
“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.
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.
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?
Explanation
Correct Answer
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
“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.
“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.
“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.
Explanation
Correct Answer
“Execute any generated payment or deletion call without a human approval checkpoint” would violate the requirement.
“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
“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.
“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.
“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
- Microsoft AI-103 Practice Test 35 - 10 Questions (Last Reviewed 18-Oct-2026)
- Microsoft AI-103 Practice Test 36 - 10 Questions (Last Reviewed 17-Oct-2026)
- Microsoft AI-103 Practice Test 37 - 10 Questions (Last Reviewed 16-Oct-2026)
- Microsoft AI-103 Practice Test 38 - 10 Questions (Last Reviewed 15-Oct-2026)
- Microsoft AI-103 Practice Test 39 - 10 Questions (Last Reviewed 14-Oct-2026)