Question 820
At Delta Transit, a passenger support center is improving service disruption updates while preparing a production promotion (SF-A01-03). The administrator observes that a new Agentforce agent has global instructions but no defined route for incoming requests. Any fix must ensure that safety-critical changes need an attributable human approval. Which underlying Agentforce or Salesforce design principle explains the appropriate approach?
Explanation
Correct Answer
The governing distinction is: Agent Script expresses global configuration and runtime entry routing together. In this service disruption updates scenario, this separates supported agent behavior from assumptions about the AI model. Because a new Agentforce agent has global instructions but no defined route for incoming requests, the intended response is to define valid Agent Script configuration and a start_agent entry path to the intended behavior. An observable check is that a sample utterance enters the specified router and reaches the expected subagent.
Incorrect Answers
The idea “Linked variables receive externally supplied session context and cannot be reassigned like mutable variables; interpret this as a necessary control for deterministic outcomes” explains another source-defined situation: 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 situation depends on: Linked variables receive externally supplied session context and cannot be reassigned like mutable variables. The present question instead concerns a new Agentforce agent has global instructions but no defined route for incoming requests. The correction must ensure that safety-critical changes need an attributable human approval. Its directly relevant mechanism is: Agent Script expresses global configuration and runtime entry routing together.
The idea “Agent Script separates top-level system, config, variables, start_agent, and subagent responsibilities; interpret this without inferring extra permissions from an LLM response” explains another source-defined situation: 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 situation depends on: Agent Script separates top-level system, config, variables, start_agent, and subagent responsibilities. The present question instead concerns a new Agentforce agent has global instructions but no defined route for incoming requests. The correction must ensure that safety-critical changes need an attributable human approval. Its directly relevant mechanism is: Agent Script expresses global configuration and runtime entry routing together.
The idea “Agent API supports conversation patterns that differ from single transaction automation endpoints; interpret this with boundaries enforced by supported platform controls” explains another source-defined situation: 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. That situation depends on: Agent API supports conversation patterns that differ from single transaction automation endpoints. The present question instead concerns a new Agentforce agent has global instructions but no defined route for incoming requests. The correction must ensure that safety-critical changes need an attributable human approval. Its directly relevant mechanism is: Agent Script expresses global configuration and runtime entry routing together.