Question 600
At Fairmont Finance, a regulated client experience team is improving account onboarding during a least-privilege verification (SF-A09-03). The administrator observes that an agent issues a customer credit twice during one support session after a repeated request. Any fix must ensure that financial identifiers are masked outside authorized roles. 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 Fairmont Finance (SF-A09-03). 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 financial identifiers are masked outside authorized roles.
Incorrect Answers
This safeguard, “Test nulls, unexpected types, and boundary values; review it before expanding channel availability”, reduces a different source-defined risk: Dynamic script instructions expose an empty variable in a critical business condition. The correction must ensure that billing adjustments require verified eligibility. That risk depends on: Template expression correctness depends on typed variables and explicit 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 financial identifiers are masked outside authorized roles. The originally selected control “Test repeated requests and recovery after action failure; review it after configuration or data-source updates” 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 financial identifiers are masked outside authorized roles. The originally selected control “Test repeated requests and recovery after action failure; review it after configuration or data-source updates” is more specific because a mutable state flag can enforce a rule independent of LLM wording.
This safeguard, “Test over-limit and missing-evidence cases for each action; review it as part of periodic access and quality reviews”, reduces a different source-defined risk: A refund action accepts an unverified customer amount and bypasses the approved amount limit. The correction must ensure that member records cannot be exposed to other members. That risk depends on: Natural-language instructions alone are weaker than deterministic protected-action controls. 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 financial identifiers are masked outside authorized roles. The originally selected control “Test repeated requests and recovery after action failure; review it after configuration or data-source updates” is more specific because a mutable state flag can enforce a rule independent of LLM wording.