Question 450
At Fairmont Finance, a regulated client experience team is improving account onboarding during a least-privilege verification (SF-A11-01). The administrator observes that an agent confuses a user-provided email address with the authenticated contact ID. 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 forged identifiers and user switching; require the check in the next release review at Fairmont Finance (SF-A11-01). It complements the corrective action, use trusted linked identity context for account-specific action authorization, and protects the explicit condition that financial identifiers are masked outside authorized roles.
Incorrect Answers
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 confuses a user-provided email address with the authenticated contact ID. The correction must ensure that financial identifiers are masked outside authorized roles. The originally selected control “Test forged identifiers and user switching; review it as part of periodic access and quality reviews” is more specific because trusted linked identity is not interchangeable with unverified conversational text.
This safeguard, “Test repeated requests and recovery after action failure; review it with a documented exception process”, reduces a different source-defined risk: 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. That risk depends on: A mutable state flag can enforce a rule independent of LLM wording. The recurring problem here is 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. The originally selected control “Test forged identifiers and user switching; review it as part of periodic access and quality reviews” is more specific because trusted linked identity is not interchangeable with unverified conversational text.
This safeguard, “Audit Flow permissions and action-input mappings; review it with audit evidence from regression testing”, reduces a different source-defined risk: An agent explains case policy correctly but cannot execute an approved follow-up Flow. The correction must ensure that plant access boundaries are not weakened by chatbot replies. That risk depends on: Actions let agents execute governed Salesforce automation beyond text generation. The recurring problem here is 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. The originally selected control “Test forged identifiers and user switching; review it as part of periodic access and quality reviews” is more specific because trusted linked identity is not interchangeable with unverified conversational text.