Question 250
At Delta Transit, a passenger support center is improving service disruption updates after a documented configuration change (SF-A09-01). The administrator observes that an agent issues a customer credit twice during one support session after a repeated request. Any fix must ensure that safety-critical changes need an attributable human approval. Which continuing control best prevents this issue from recurring?
Explanation
Correct Answer
The preventive control directly addresses repeat failures: Test repeated requests and recovery after action failure; require the check in the next release review at Delta Transit (SF-A09-01). It complements the corrective action, use a session-state flag and deterministic action guard that prevents a second credit, and protects the explicit condition that safety-critical changes need an attributable human approval.
Incorrect Answers
This safeguard, “Test forged identifiers and user switching; review it as part of periodic access and quality reviews”, reduces a different source-defined risk: An agent confuses a user-provided email address with the authenticated contact ID. The correction must ensure that financial identifiers are masked outside authorized roles. That risk depends on: Trusted linked identity is not interchangeable with unverified conversational text. The recurring problem here is an agent issues a customer credit twice during one support session after a repeated request. The correction must ensure that safety-critical changes need an attributable human approval. The originally selected control “Test repeated requests and recovery after action failure; review it with a documented exception process” is more specific because a mutable state flag can enforce a rule independent of LLM wording.
This safeguard, “Run positive and negative action-availability tests; review it with audit evidence from regression testing”, reduces a different source-defined risk: An agent sometimes sends cancellation requests for orders that are already shipped. The correction must ensure that sensitive product claims must cite approved knowledge. That risk depends on: Action filters constrain which actions are available under defined conditions. The recurring problem here is an agent issues a customer credit twice during one support session after a repeated request. The correction must ensure that safety-critical changes need an attributable human approval. The originally selected control “Test repeated requests and recovery after action failure; review it with a documented exception process” is more specific because a mutable state flag can enforce a rule independent of LLM wording.
This safeguard, “Test eligibility boundaries and explanatory wording independently; review it as part of periodic access and quality reviews”, reduces a different source-defined risk: The agent must enforce a refund eligibility rule but still explain decisions conversationally. The correction must ensure that donor details cannot be revealed across accounts. That risk depends on: Hybrid reasoning combines fixed business logic with flexible language generation. The recurring problem here is an agent issues a customer credit twice during one support session after a repeated request. The correction must ensure that safety-critical changes need an attributable human approval. The originally selected control “Test repeated requests and recovery after action failure; review it with a documented exception process” is more specific because a mutable state flag can enforce a rule independent of LLM wording.