Question 950
At Summit Pharma, a regulated information center is improving product information following a quarterly access review (SF-A03-02). The administrator observes that a customer-support agent asks users to repeat an authenticated session identifier supplied by the channel. Any fix must ensure that sensitive product claims must cite approved knowledge. Which continuing control best prevents this issue from recurring?
Explanation
Correct Answer
The preventive control directly addresses repeat failures: Verify channel mappings and avoid exposing session identifiers unnecessarily; require the check in the next release review at Summit Pharma (SF-A03-02). It complements the corrective action, declare and reference the appropriate supported linked session variable as read-only context, and protects the explicit condition that sensitive product claims must cite approved knowledge.
Incorrect Answers
This safeguard, “Initialize state and test first-turn and repeated-turn behavior; review it and confirm the control remains effective after release”, reduces a different source-defined risk: An agent checks whether a compensation was issued but its mutable flag has no reliable initial state. The correction must ensure that sensitive product claims must cite approved knowledge. That risk depends on: Mutable Agent Script variables hold state that deterministic conditions can use. The recurring problem here is a customer-support agent asks users to repeat an authenticated session identifier supplied by the channel. The correction must ensure that sensitive product claims must cite approved knowledge. The originally selected control “Verify channel mappings and avoid exposing session identifiers unnecessarily; review it and retest after dependent metadata changes” is more specific because linked variables receive externally supplied session context and cannot be reassigned like mutable variables.
This safeguard, “Review block placement and syntax before activation; review it before expanding channel availability”, reduces a different source-defined risk: An administrator puts all conversational logic into system messages instead of separating routing and subagent behavior. The correction must ensure that supplier prices are never shown outside entitled teams. That risk depends on: Agent Script separates top-level system, config, variables, start_agent, and subagent responsibilities. The recurring problem here is a customer-support agent asks users to repeat an authenticated session identifier supplied by the channel. The correction must ensure that sensitive product claims must cite approved knowledge. The originally selected control “Verify channel mappings and avoid exposing session identifiers unnecessarily; review it and retest after dependent metadata changes” is more specific because linked variables receive externally supplied session context and cannot be reassigned like mutable variables.
This safeguard, “Test cross-workspace access and installation governance; review it with audit evidence from regression testing”, reduces a different source-defined risk: Internal employees expect the company agent in Slack but the connector exposes an unrelated public service agent. The correction must ensure that quoted amounts use authorized account and price-book records. That risk depends on: Channel connections must preserve the intended audience and authorization context. The recurring problem here is a customer-support agent asks users to repeat an authenticated session identifier supplied by the channel. The correction must ensure that sensitive product claims must cite approved knowledge. The originally selected control “Verify channel mappings and avoid exposing session identifiers unnecessarily; review it and retest after dependent metadata changes” is more specific because linked variables receive externally supplied session context and cannot be reassigned like mutable variables.