Question 720
At Delta Transit, a passenger support center is improving service disruption updates while preparing a production promotion (SF-A02-02). The administrator observes that an administrator puts all conversational logic into system messages instead of separating routing and subagent behavior. Any fix must ensure that safety-critical changes need an attributable human approval. Which continuing control best prevents this issue from recurring?
Explanation
Correct Answer
The preventive control directly addresses repeat failures: Review block placement and syntax before activation; require the check in the next release review at Delta Transit (SF-A02-02). It complements the corrective action, assign identity, variables, routing, and subagent instructions to their appropriate script blocks, and protects the explicit condition that safety-critical changes need an attributable human approval.
Incorrect Answers
This safeguard, “Verify channel mappings and avoid exposing session identifiers unnecessarily; review it after configuration or data-source updates”, reduces a different source-defined risk: A customer-support agent asks users to repeat an authenticated session identifier supplied by the channel. The correction must ensure that safety-critical changes need an attributable human approval. That risk depends on: Linked variables receive externally supplied session context and cannot be reassigned like mutable variables. The recurring problem here is an administrator puts all conversational logic into system messages instead of separating routing and subagent behavior. The correction must ensure that safety-critical changes need an attributable human approval. The originally selected control “Review block placement and syntax before activation; review it and confirm the control remains effective after release” is more specific because agent Script separates top-level system, config, variables, start_agent, and subagent responsibilities.
This safeguard, “Validate required script blocks whenever the router changes; review it as part of periodic access and quality reviews”, reduces a different source-defined risk: A new Agentforce agent has global instructions but no defined route for incoming requests. The correction must ensure that student records never cross program authorization boundaries. That risk depends on: Agent Script expresses global configuration and runtime entry routing together. The recurring problem here is an administrator puts all conversational logic into system messages instead of separating routing and subagent behavior. The correction must ensure that safety-critical changes need an attributable human approval. The originally selected control “Review block placement and syntax before activation; review it and confirm the control remains effective after release” is more specific because agent Script separates top-level system, config, variables, start_agent, and subagent responsibilities.
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 an administrator puts all conversational logic into system messages instead of separating routing and subagent behavior. The correction must ensure that safety-critical changes need an attributable human approval. The originally selected control “Review block placement and syntax before activation; review it and confirm the control remains effective after release” is more specific because agent Script separates top-level system, config, variables, start_agent, and subagent responsibilities.