Question 580
At Valley Utilities, a customer billing center is improving billing questions after a documented configuration change (SF-A11-02). The administrator observes that an agent confuses a user-provided email address with the authenticated contact ID. Any fix must ensure that billing adjustments require verified eligibility. Which action best addresses the issue while preserving the stated requirement?
Explanation
Correct Answer
The documented failure is that an agent confuses a user-provided email address with the authenticated contact ID. Use trusted linked identity context for account-specific action authorization for Valley Utilities's billing questions workflow (SF-A11-02) while respecting that billing adjustments require verified eligibility. Its outcome is not established merely by changing instructions: In a controlled Billing_Account__c acceptance test, an attempted cross-account request fails despite a plausible supplied email address; the record is retained under Valley Utilities's rollout (SF-A11-02). The underlying reason is that Trusted linked identity is not interchangeable with unverified conversational text. In this billing questions scenario, this separates supported agent behavior from assumptions about the AI model.
Incorrect Answers
The action “Provide safe defaults and explicit null checks before evaluating the expression; implement it within the documented Salesforce configuration” addresses a separate source case: Dynamic script instructions expose an empty variable in a critical business condition. The correction must ensure that billing adjustments require verified eligibility. Its underlying reason is: Template expression correctness depends on typed variables and explicit conditions. This question instead describes an agent confuses a user-provided email address with the authenticated contact ID. The correction must ensure that billing adjustments require verified eligibility. The original answer “Use trusted linked identity context for account-specific action authorization; implement it and keep the business rule enforceable” targets that failure because trusted linked identity is not interchangeable with unverified conversational text.
The action “Filter the cancellation action on the required order state before execution; implement it with a named deployment owner” addresses a separate source case: An agent sometimes sends cancellation requests for orders that are already shipped. The correction must ensure that sensitive product claims must cite approved knowledge. Its underlying reason is: Action filters constrain which actions are available under defined conditions. This question instead describes an agent confuses a user-provided email address with the authenticated contact ID. The correction must ensure that billing adjustments require verified eligibility. The original answer “Use trusted linked identity context for account-specific action authorization; implement it and keep the business rule enforceable” targets that failure because trusted linked identity is not interchangeable with unverified conversational text.
The action “Separate customer service and internal employee use cases with appropriate agent boundaries; implement it with least-privilege execution” addresses a separate source case: One shared bot mixes employee operational runbooks with public refund answers. The correction must ensure that capacity limits and customer entitlements are enforced deterministically. Its underlying reason is: Different agent audiences imply different trust, authorization and context boundaries. This question instead describes an agent confuses a user-provided email address with the authenticated contact ID. The correction must ensure that billing adjustments require verified eligibility. The original answer “Use trusted linked identity context for account-specific action authorization; implement it and keep the business rule enforceable” targets that failure because trusted linked identity is not interchangeable with unverified conversational text.