Question 970
At Greenwell Energy, a field technician assistance team is improving asset inspection during a controlled sandbox pilot (SF-A14-02). The administrator observes that a service agent handles warranty inspection but its broad existing topic attracts unrelated requests. Any fix must ensure that plant access boundaries are not weakened by chatbot replies. Which underlying Agentforce or Salesforce design principle explains the appropriate approach?
Explanation
Correct Answer
The governing distinction is: Topic descriptions and instructions guide appropriate task selection. In this asset inspection scenario, this separates supported agent behavior from assumptions about the AI model. Because a service agent handles warranty inspection but its broad existing topic attracts unrelated requests, the intended response is to add a custom topic with focused scope and clear routing instructions. An observable check is that warranty questions enter the custom topic while unrelated shipping questions do not.
Incorrect Answers
The idea “Standard agent topics can be reused when they already fit the task; interpret this as distinct from unrelated UI configuration” explains another source-defined situation: A customer asks for a common supported case status operation already provided by a standard Agentforce topic. The correction must ensure that part inventory decisions use approved current records. That situation depends on: Standard agent topics can be reused when they already fit the task. The present question instead concerns a service agent handles warranty inspection but its broad existing topic attracts unrelated requests. The correction must ensure that plant access boundaries are not weakened by chatbot replies. Its directly relevant mechanism is: Topic descriptions and instructions guide appropriate task selection.
The idea “Actions let agents execute governed Salesforce automation beyond text generation; interpret this independent of the surface wording of the conversation” explains another source-defined situation: An agent explains case policy correctly but cannot execute an approved follow-up Flow. The correction must ensure that plant access boundaries are not weakened by chatbot replies. That situation depends on: Actions let agents execute governed Salesforce automation beyond text generation. The present question instead concerns a service agent handles warranty inspection but its broad existing topic attracts unrelated requests. The correction must ensure that plant access boundaries are not weakened by chatbot replies. Its directly relevant mechanism is: Topic descriptions and instructions guide appropriate task selection.
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 service agent handles warranty inspection but its broad existing topic attracts unrelated requests. The correction must ensure that plant access boundaries are not weakened by chatbot replies. Its directly relevant mechanism is: Topic descriptions and instructions guide appropriate task selection.