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

Question 420

Situation: A travel assistant charges a booking deposit and its client times out after the payment provider accepted the call. Which TWO proposed practices create material safety, correctness, or reliability risks? Select TWO answers.

  1. Validate tool names and arguments against an allowlist, attach idempotency keys to side-effecting calls and retry only under explicit policy
  2. Allow arbitrary generated tool names to execute server shell commands
  3. Inspect records that explain the affected process, then check the result described in this case: A travel assistant charges a booking deposit and its client times out after the payment provider accepted the call
  4. Automatically repeat a payment tool after every timeout using a new request ID
  5. Replayed requests do not cause duplicate side effects, and unsupported tool names or out-of-range values are denied before dispatch

Explanation

Correct Answer

B:

Because a travel assistant charges a booking deposit and its client times out after the payment provider accepted the call, “Allow arbitrary generated tool names to execute server shell commands” would violate the requirement. Model-generated tool suggestions are untrusted requests; transient timeouts do not prove whether an external payment or order action executed.

D:

“Automatically repeat a payment tool after every timeout using a new request ID” would violate the requirement. Model-generated tool suggestions are untrusted requests; transient timeouts do not prove whether an external payment or order action executed.

Incorrect Answers

A:

A travel assistant charges a booking deposit and its client times out after the payment provider accepted the call. “Validate tool names and arguments against an allowlist, attach idempotency keys to side-effecting calls and retry only under explicit policy” is the controlled implementation, not an unsafe workaround. Model-generated tool suggestions are untrusted requests; transient timeouts do not prove whether an external payment or order action executed. Confirm that replayed requests do not cause duplicate side effects, and unsupported tool names or out-of-range values are denied before dispatch.

C:

“Inspect records that explain the affected process, then check the result described in this case: A travel assistant charges a booking deposit” adds a relevant safeguard or verification step rather than weakening the solution. Model-generated tool suggestions are untrusted requests; transient timeouts do not prove whether an external payment or order action executed. Confirm that replayed requests do not cause duplicate side effects, and unsupported tool names or out-of-range values are denied before dispatch.

E:

“Replayed requests do not cause duplicate side effects, and unsupported tool names or out-of-range values are denied before dispatch” is the required outcome of a working control, not an action that weakens it. Model-generated tool suggestions are untrusted requests; transient timeouts do not prove whether an external payment or order action executed.

Question 421

Architecture case: A retail ordering agent can use approved inventory and order tools but generates a tool name outside the allowlist. What configuration should the engineer choose for this workload?

  1. Apply the proposed setting to all connected workloads before testing the case-specific boundary: a retail ordering agent can use approved inventory and order tools but generates a tool name outside the allowlist
  2. Interpret an HTTP timeout as proof no side effect happened
  3. Skip request validation once the assistant has a trusted system prompt
  4. Validate tool names and arguments against an allowlist, attach idempotency keys to side-effecting calls and retry only under explicit policy

Explanation

Correct Answer

D:

Model-generated tool suggestions are untrusted requests; transient timeouts do not prove whether an external payment or order action executed. Replayed requests do not cause duplicate side effects, and unsupported tool names or out-of-range values are denied before dispatch.

Incorrect Answers

A:

“Apply the proposed setting to all connected workloads before testing the case-specific boundary: a retail ordering agent can use approved inventory” does not implement the control that the facts call for. Model-generated tool suggestions are untrusted requests; transient timeouts do not prove whether an external payment or order action executed. Instead, validate tool names and arguments against an allowlist, attach idempotency keys to side-effecting calls and retry only under explicit policy.

B:

A retail ordering agent can use approved inventory and order tools but generates a tool name outside the allowlist. “Interpret an HTTP timeout as proof no side effect happened” does not implement the control that the facts call for. Model-generated tool suggestions are untrusted requests; transient timeouts do not prove whether an external payment or order action executed. Instead, validate tool names and arguments against an allowlist, attach idempotency keys to side-effecting calls and retry only under explicit policy.

C:

A retail ordering agent can use approved inventory and order tools but generates a tool name outside the allowlist. “Skip request validation once the assistant has a trusted system prompt” would not meet the requirement. Model-generated tool suggestions are untrusted requests; transient timeouts do not prove whether an external payment or order action executed. Instead, validate tool names and arguments against an allowlist, attach idempotency keys to side-effecting calls and retry only under explicit policy.

Question 422

Production requirement: A retail ordering agent can use approved inventory and order tools but generates a tool name outside the allowlist. What technical fact prevents the simplest shortcut from being reliable?

  1. Model-generated tool suggestions are untrusted requests; transient timeouts do not prove whether an external payment or order action executed
  2. Successful provisioning by itself proves all security, output, and operational constraints are satisfied
  3. The most powerful or least restricted model is always the safest choice regardless of task conditions
  4. The fact that the team started work is enough to prove correctness for this exact case: a retail ordering agent can use approved inventory and order tools but generates a tool name outside the allowlist

Explanation

Correct Answer

A:

A retail ordering agent can use approved inventory and order tools but generates a tool name outside the allowlist. Model-generated tool suggestions are untrusted requests; transient timeouts do not prove whether an external payment or order action executed. Validate tool names and arguments against an allowlist, attach idempotency keys to side-effecting calls and retry only under explicit policy.

Incorrect Answers

B:

“Successful provisioning by itself proves all security, output, and operational constraints are satisfied” does not fully explain the decisive technical boundary in this case. Model-generated tool suggestions are untrusted requests; transient timeouts do not prove whether an external payment or order action executed.

C:

“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. Model-generated tool suggestions are untrusted requests; transient timeouts do not prove whether an external payment or order action executed.

D:

“The fact that the team started work is enough to prove correctness for this exact case: a retail ordering agent can use approved inventory and order tools but generates a tool name outside the allowlist” does not fully explain the decisive technical boundary in this case. Model-generated tool suggestions are untrusted requests; transient timeouts do not prove whether an external payment or order action executed. The implementation must validate tool names and arguments against an allowlist, attach idempotency keys to side-effecting calls and retry only under explicit policy.

Question 423

A team is investigating this task: A retail ordering agent can use approved inventory and order tools but generates a tool name outside the allowlist. 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. The operator reports success without reproducing the observed behavior: a retail ordering agent can use approved inventory and order tools but generates a tool name outside the allowlist
  3. Replayed requests do not cause duplicate side effects, and unsupported tool names or out-of-range values are denied before dispatch
  4. The team closes a change ticket without replaying a representative positive and negative test

Explanation

Correct Answer

C:

Because a retail ordering agent can use approved inventory and order tools but generates a tool name outside the allowlist, model-generated tool suggestions are untrusted requests; transient timeouts do not prove whether an external payment or order action executed. Replayed requests do not cause duplicate side effects, and unsupported tool names or out-of-range values are denied before dispatch. If this test fails, inspect tool schemas, transaction IDs, idempotency-store hits, timeout traces and denied request arguments.

Incorrect Answers

A:

A retail ordering agent can use approved inventory and order tools but generates a tool name outside the allowlist. “A project dashboard remains green, although the affected request, output and permissions were not checked” would not meet the requirement. Replayed requests do not cause duplicate side effects, and unsupported tool names or out-of-range values are denied before dispatch. Model-generated tool suggestions are untrusted requests; transient timeouts do not prove whether an external payment or order action executed.

B:

“The operator reports success without reproducing the observed behavior: a retail ordering agent can use approved inventory and order tools but generates a tool name outside the allowlist” alone does not establish all the required behavior. Replayed requests do not cause duplicate side effects, and unsupported tool names or out-of-range values are denied before dispatch. Model-generated tool suggestions are untrusted requests; transient timeouts do not prove whether an external payment or order action executed.

D:

A retail ordering agent can use approved inventory and order tools but generates a tool name outside the allowlist. “The team closes a change ticket without replaying a representative positive and negative test” alone does not establish all the required behavior. Replayed requests do not cause duplicate side effects, and unsupported tool names or out-of-range values are denied before dispatch.

Question 424

Situation: A retail ordering agent can use approved inventory and order tools but generates a tool name outside the allowlist. Which diagnostic investigation best isolates the issue before another change?

  1. Inspect tool schemas, transaction IDs, idempotency-store hits, timeout traces and denied request arguments
  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 retail ordering agent can use approved inventory and order tools but generates a tool name outside the allowlist
  4. Restart every affected component before collecting request or tool traces

Explanation

Correct Answer

A:

A retail ordering agent can use approved inventory and order tools but generates a tool name outside the allowlist. Inspect tool schemas, transaction IDs, idempotency-store hits, timeout traces and denied request arguments. Model-generated tool suggestions are untrusted requests; transient timeouts do not prove whether an external payment or order action executed. Replayed requests do not cause duplicate side effects, and unsupported tool names or out-of-range values are denied before dispatch.

Incorrect Answers

B:

A retail ordering agent can use approved inventory and order tools but generates a tool name outside the allowlist. “Read only the broad service-health summary and skip actual workload evidence” would not meet the requirement. Inspect tool schemas, transaction IDs, idempotency-store hits, timeout traces and denied request arguments.

C:

“Assume the general service is at fault without checking the affected operation in this case: a retail ordering agent can use approved inventory” would not meet the requirement. Inspect tool schemas, transaction IDs, idempotency-store hits, timeout traces and denied request arguments. Model-generated tool suggestions are untrusted requests; transient timeouts do not prove whether an external payment or order action executed.

D:

“Restart every affected component before collecting request or tool traces” would not be the most direct first check for this failure. Inspect tool schemas, transaction IDs, idempotency-store hits, timeout traces and denied request arguments. Model-generated tool suggestions are untrusted requests; transient timeouts do not prove whether an external payment or order action executed.

Question 425

Architecture case: A retail ordering agent can use approved inventory and order tools but generates a tool name outside the allowlist. Which TWO shortcuts should be rejected for this scenario? Select TWO answers.

  1. Inspect records that explain the affected process, then check the result described in this case: A retail ordering agent can use approved inventory and order tools but generates a tool name outside the allowlist
  2. Validate tool names and arguments against an allowlist, attach idempotency keys to side-effecting calls and retry only under explicit policy
  3. Allow arbitrary generated tool names to execute server shell commands
  4. Automatically repeat a payment tool after every timeout using a new request ID
  5. Replayed requests do not cause duplicate side effects, and unsupported tool names or out-of-range values are denied before dispatch

Explanation

Correct Answer

C:

Because a retail ordering agent can use approved inventory and order tools but generates a tool name outside the allowlist, “Allow arbitrary generated tool names to execute server shell commands” would violate the requirement. Model-generated tool suggestions are untrusted requests; transient timeouts do not prove whether an external payment or order action executed.

D:

A retail ordering agent can use approved inventory and order tools but generates a tool name outside the allowlist. “Automatically repeat a payment tool after every timeout using a new request ID” would violate the requirement. Model-generated tool suggestions are untrusted requests; transient timeouts do not prove whether an external payment or order action executed.

Incorrect Answers

A:

“Inspect records that explain the affected process, then check the result described in this case: A retail ordering agent can use approved inventory” adds a relevant safeguard or verification step rather than weakening the solution. Model-generated tool suggestions are untrusted requests; transient timeouts do not prove whether an external payment or order action executed.

B:

A retail ordering agent can use approved inventory and order tools but generates a tool name outside the allowlist. “Validate tool names and arguments against an allowlist, attach idempotency keys to side-effecting calls and retry only under explicit policy” is the controlled implementation, not an unsafe workaround. Model-generated tool suggestions are untrusted requests; transient timeouts do not prove whether an external payment or order action executed. Confirm that replayed requests do not cause duplicate side effects, and unsupported tool names or out-of-range values are denied before dispatch.

E:

A retail ordering agent can use approved inventory and order tools but generates a tool name outside the allowlist. “Replayed requests do not cause duplicate side effects, and unsupported tool names or out-of-range values are denied before dispatch” is the required outcome of a working control, not an action that weakens it. Model-generated tool suggestions are untrusted requests; transient timeouts do not prove whether an external payment or order action executed. Confirm that replayed requests do not cause duplicate side effects, and unsupported tool names or out-of-range values are denied before dispatch.

Question 426

Production requirement: A pharmacy reorder system receives a negative quantity from a model-suggested tool argument. Which next change most directly addresses the reported technical risk?

  1. Interpret an HTTP timeout as proof no side effect happened
  2. Apply the proposed setting to all connected workloads before testing the case-specific boundary: a pharmacy reorder system receives a negative quantity from a model-suggested tool argument
  3. Validate tool names and arguments against an allowlist, attach idempotency keys to side-effecting calls and retry only under explicit policy
  4. Skip request validation once the assistant has a trusted system prompt

Explanation

Correct Answer

C:

Validate tool names and arguments against an allowlist, attach idempotency keys to side-effecting calls and retry only under explicit policy. Replayed requests do not cause duplicate side effects, and unsupported tool names or out-of-range values are denied before dispatch.

Incorrect Answers

A:

“Interpret an HTTP timeout as proof no side effect happened” does not implement the control that the facts call for. Instead, validate tool names and arguments against an allowlist, attach idempotency keys to side-effecting calls and retry only under explicit policy.

B:

“Apply the proposed setting to all connected workloads before testing the case-specific boundary: a pharmacy reorder system receives a negative quantity from a model-suggested tool argument” does not implement the control that the facts call for. Instead, validate tool names and arguments against an allowlist, attach idempotency keys to side-effecting calls and retry only under explicit policy.

D:

“Skip request validation once the assistant has a trusted system prompt” would not meet the requirement. Instead, validate tool names and arguments against an allowlist, attach idempotency keys to side-effecting calls and retry only under explicit policy.

Question 427

A team is investigating this task: A pharmacy reorder system receives a negative quantity from a model-suggested tool argument. Which explanation best captures the key behavior of this architecture?

  1. Model-generated tool suggestions are untrusted requests; transient timeouts do not prove whether an external payment or order action executed
  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 pharmacy reorder system receives a negative quantity from a model-suggested tool argument

Explanation

Correct Answer

A:

A pharmacy reorder system receives a negative quantity from a model-suggested tool argument. Model-generated tool suggestions are untrusted requests; transient timeouts do not prove whether an external payment or order action executed. Replayed requests do not cause duplicate side effects, and unsupported tool names or out-of-range values are denied before dispatch.

Incorrect Answers

B:

“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. Model-generated tool suggestions are untrusted requests; transient timeouts do not prove whether an external payment or order action executed.

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. Model-generated tool suggestions are untrusted requests; transient timeouts do not prove whether an external payment or order action executed.

D:

“The fact that the team started work is enough to prove correctness for this exact case: a pharmacy reorder system receives a negative quantity from a model-suggested tool argument” would not be the most direct first check for this failure. Model-generated tool suggestions are untrusted requests; transient timeouts do not prove whether an external payment or order action executed.

Question 428

Situation: A pharmacy reorder system receives a negative quantity from a model-suggested tool argument. Which result would demonstrate that the proposed remedy works end to end?

  1. A project dashboard remains green, although the affected request, output and permissions were not checked
  2. The team closes a change ticket without replaying a representative positive and negative test
  3. The operator reports success without reproducing the observed behavior: a pharmacy reorder system receives a negative quantity from a model-suggested tool argument
  4. Replayed requests do not cause duplicate side effects, and unsupported tool names or out-of-range values are denied before dispatch

Explanation

Correct Answer

D:

Because a pharmacy reorder system receives a negative quantity from a model-suggested tool argument, replayed requests do not cause duplicate side effects, and unsupported tool names or out-of-range values are denied before dispatch. Validate tool names and arguments against an allowlist, attach idempotency keys to side-effecting calls and retry only under explicit policy.

Incorrect Answers

A:

A pharmacy reorder system receives a negative quantity from a model-suggested tool argument. “A project dashboard remains green, although the affected request, output and permissions were not checked” would not meet the requirement. Replayed requests do not cause duplicate side effects, and unsupported tool names or out-of-range values are denied before dispatch.

B:

Because a pharmacy reorder system receives a negative quantity from a model-suggested tool argument, “The team closes a change ticket without replaying a representative positive and negative test” alone does not establish all the required behavior. Replayed requests do not cause duplicate side effects, and unsupported tool names or out-of-range values are denied before dispatch.

C:

“The operator reports success without reproducing the observed behavior: a pharmacy reorder system receives a negative quantity from a model-suggested tool argument” alone does not establish all the required behavior. Replayed requests do not cause duplicate side effects, and unsupported tool names or out-of-range values are denied before dispatch.

Question 429

Architecture case: A pharmacy reorder system receives a negative quantity from a model-suggested tool argument. What evidence should the engineer correlate to verify the actual failure cause?

  1. Restart every affected component before collecting request or tool traces
  2. Inspect tool schemas, transaction IDs, idempotency-store hits, timeout traces and denied request arguments
  3. Assume the general service is at fault without checking the affected operation in this case: a pharmacy reorder system receives a negative quantity from a model-suggested tool argument
  4. Read only the broad service-health summary and skip actual workload evidence

Explanation

Correct Answer

B:

Replayed requests do not cause duplicate side effects, and unsupported tool names or out-of-range values are denied before dispatch. Validate tool names and arguments against an allowlist, attach idempotency keys to side-effecting calls and retry only under explicit policy.

Incorrect Answers

A:

“Restart every affected component before collecting request or tool traces” alone does not establish all the required behavior. Replayed requests do not cause duplicate side effects, and unsupported tool names or out-of-range values are denied before dispatch.

C:

“Assume the general service is at fault without checking the affected operation in this case: a pharmacy reorder system receives a negative quantity from a model-suggested tool argument” would not meet the requirement. Replayed requests do not cause duplicate side effects, and unsupported tool names or out-of-range values are denied before dispatch.

D:

“Read only the broad service-health summary and skip actual workload evidence” would not meet the requirement. Replayed requests do not cause duplicate side effects, and unsupported tool names or out-of-range values are denied before dispatch.

Question 430

Production requirement: A pharmacy reorder system receives a negative quantity from a model-suggested tool argument. Which TWO decisions would undermine the required system boundary? Select TWO answers.

  1. Automatically repeat a payment tool after every timeout using a new request ID
  2. Replayed requests do not cause duplicate side effects, and unsupported tool names or out-of-range values are denied before dispatch
  3. Validate tool names and arguments against an allowlist, attach idempotency keys to side-effecting calls and retry only under explicit policy
  4. Allow arbitrary generated tool names to execute server shell commands
  5. Inspect records that explain the affected process, then check the result described in this case: A pharmacy reorder system receives a negative quantity from a model-suggested tool argument

Explanation

Correct Answer

A:

“Automatically repeat a payment tool after every timeout using a new request ID” would violate the requirement. The appropriate control instead is to validate tool names and arguments against an allowlist, attach idempotency keys to side-effecting calls and retry only under explicit policy.

D:

“Allow arbitrary generated tool names to execute server shell commands” would violate the requirement.

Incorrect Answers

B:

“Replayed requests do not cause duplicate side effects, and unsupported tool names or out-of-range values are denied before dispatch” is the required outcome of a working control, not an action that weakens it. Confirm that replayed requests do not cause duplicate side effects, and unsupported tool names or out-of-range values are denied before dispatch.

C:

“Validate tool names and arguments against an allowlist, attach idempotency keys to side-effecting calls and retry only under explicit policy” is the controlled implementation, not an unsafe workaround.

E:

“Inspect records that explain the affected process, then check the result described in this case: A pharmacy reorder system receives a negative quantity from a model-suggested tool argument” adds a relevant safeguard or verification step rather than weakening the solution. Confirm that replayed requests do not cause duplicate side effects, and unsupported tool names or out-of-range values are denied before dispatch.

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