Question 35
Domain 3: Application DevelopmentAn agent can call a refund API that has real financial impact. What additional control is most appropriate before the tool runs?
Correct answer: B
Explanation
A refund API creates a side effect with real financial impact, so it should not run automatically. The appropriate control is to require "explicit confirmation or human approval for side effects" before execution, which adds a safeguard against unintended refunds.
Why each option is right or wrong
A. Always auto-execute to reduce latency
Auto-execution removes the safety checkpoint needed for financially impactful actions.
B. Require explicit confirmation or human approval for side effects
Refunding money is a state-changing action with direct financial loss, so it should not be executable on a single unverified agent request. In control terms, this is the classic “human-in-the-loop” safeguard for irreversible or high-impact side effects: the tool should pause until an explicit approval is received from an authorized person before the refund is submitted.
C. Lower the chunk overlap
Chunk overlap affects retrieval quality, not authorization for real-world side effects.
D. Disable logging
Disabling logging reduces auditability and makes sensitive actions harder to investigate.