Question 180
At Northpoint Hospitality, a guest services desk is improving reservation help after a documented configuration change (SF-P13-01). The administrator observes that a team saves edited prompt instructions but production still executes an older template version. Any fix must ensure that guest profile fields are used only with permitted access. Which underlying Agentforce or Salesforce design principle explains the appropriate approach?
Explanation
Correct Answer
The governing distinction is: A saved draft is not necessarily the active executable prompt template version. In this reservation help scenario, this separates supported agent behavior from assumptions about the AI model. Because a team saves edited prompt instructions but production still executes an older template version, the intended response is to preview, validate, and activate the intended revised template version before invoking it. An observable check is that the deployed invocation records the intended active version and updated instructions.
Incorrect Answers
The idea “A template invocation depends on correct input bindings and execution context; interpret this as distinct from unrelated UI configuration” explains another source-defined situation: A Flow invokes a prompt template without supplying the record inputs expected by its definition. The correction must ensure that escalations preserve only the needed guest context. That situation depends on: A template invocation depends on correct input bindings and execution context. The present question instead concerns a team saves edited prompt instructions but production still executes an older template version. The correction must ensure that guest profile fields are used only with permitted access. Its directly relevant mechanism is: A saved draft is not necessarily the active executable prompt template version.
The idea “Prompt instructions and resolved data are distinct; both affect the final output; interpret this rather than assuming a generative instruction is an access rule” explains another source-defined situation: Template preview looks correct as text but the actual resolved prompt lacks the latest case comment. The correction must ensure that citizen information stays limited to the relevant case. That situation depends on: Prompt instructions and resolved data are distinct; both affect the final output. The present question instead concerns a team saves edited prompt instructions but production still executes an older template version. The correction must ensure that guest profile fields are used only with permitted access. Its directly relevant mechanism is: A saved draft is not necessarily the active executable prompt template version.
The idea “Standard prompt types optimize specific tasks while Flex serves custom use cases; interpret this with boundaries enforced by supported platform controls” explains another source-defined situation: A team tries to use a fixed sales-email template for an unrelated service incident taxonomy analysis. The correction must ensure that billing adjustments require verified eligibility. That situation depends on: Standard prompt types optimize specific tasks while Flex serves custom use cases. The present question instead concerns a team saves edited prompt instructions but production still executes an older template version. The correction must ensure that guest profile fields are used only with permitted access. Its directly relevant mechanism is: A saved draft is not necessarily the active executable prompt template version.