Question 30
At Summit Pharma, a regulated information center is improving product information during an agent routing evaluation (SF-A09-02). The administrator observes that an agent issues a customer credit twice during one support session after a repeated request. Any fix must ensure that sensitive product claims must cite approved knowledge. Which action best addresses the issue while preserving the stated requirement?
Explanation
Correct Answer
The documented failure is that an agent issues a customer credit twice during one support session after a repeated request. Use a session-state flag and deterministic action guard that prevents a second credit for Summit Pharma's product information workflow (SF-A09-02) while respecting that sensitive product claims must cite approved knowledge. Its outcome is not established merely by changing instructions: In a controlled Product2 acceptance test, two consecutive credit requests produce at most one approved credit action; the record is retained under Summit Pharma's rollout (SF-A09-02). The underlying reason is that A mutable state flag can enforce a rule independent of LLM wording. In this product information scenario, this separates supported agent behavior from assumptions about the AI model.
Incorrect Answers
The action “Use trusted linked identity context for account-specific action authorization; implement it with traceable change approval” addresses a separate source case: 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. Its underlying reason is: Trusted linked identity is not interchangeable with unverified conversational text. This question instead describes an agent issues a customer credit twice during one support session after a repeated request. The correction must ensure that sensitive product claims must cite approved knowledge. The original answer “Use a session-state flag and deterministic action guard that prevents a second credit; implement it with traceable change approval” targets that failure because a mutable state flag can enforce a rule independent of LLM wording.
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 issues a customer credit twice during one support session after a repeated request. The correction must ensure that sensitive product claims must cite approved knowledge. The original answer “Use a session-state flag and deterministic action guard that prevents a second credit; implement it with traceable change approval” targets that failure because a mutable state flag can enforce a rule independent of LLM wording.
The action “Use an appropriate Agent API interaction for the conversational requirement while keeping deterministic operations in Flow; implement it with a controlled rollback path” addresses a separate source case: An external partner requires conversational follow-ups but the design offers only a one-shot Flow endpoint. The correction must ensure that escalations preserve only the needed guest context. Its underlying reason is: Agent API supports conversation patterns that differ from single transaction automation endpoints. This question instead describes an agent issues a customer credit twice during one support session after a repeated request. The correction must ensure that sensitive product claims must cite approved knowledge. The original answer “Use a session-state flag and deterministic action guard that prevents a second credit; implement it with traceable change approval” targets that failure because a mutable state flag can enforce a rule independent of LLM wording.