Question 290
At Bluehaven University, an internal student services team is improving student advising while preparing a production promotion (SF-T10-01). The administrator observes that a prompt template is deployed but invokes a Flow not present or active in production. Any fix must ensure that student records never cross program authorization boundaries. Which underlying Agentforce or Salesforce design principle explains the appropriate approach?
Explanation
Correct Answer
The governing distinction is: Prompt templates can depend on metadata and automation beyond template text. In this student advising scenario, this separates supported agent behavior from assumptions about the AI model. Because a prompt template is deployed but invokes a Flow not present or active in production, the intended response is to include required Flow and template dependencies in a controlled deployment plan. An observable check is that the production prompt resolves all referenced automation resources successfully.
Incorrect Answers
The idea “Deployment and activation are separate steps in prompt lifecycle; interpret this independent of the surface wording of the conversation” explains another source-defined situation: A revised prompt arrives in production but callers keep receiving the earlier active version. The correction must ensure that work order updates follow supported automation guardrails. That situation depends on: Deployment and activation are separate steps in prompt lifecycle. The present question instead concerns a prompt template is deployed but invokes a Flow not present or active in production. The correction must ensure that student records never cross program authorization boundaries. Its directly relevant mechanism is: Prompt templates can depend on metadata and automation beyond template text.
The idea “Reusable templates require portable bindings for environment-specific context; interpret this as a necessary control for deterministic outcomes” explains another source-defined situation: A prompt created in a sandbox references a test record identifier not present in production. The correction must ensure that employee identity is verified before accessing private tickets. That situation depends on: Reusable templates require portable bindings for environment-specific context. The present question instead concerns a prompt template is deployed but invokes a Flow not present or active in production. The correction must ensure that student records never cross program authorization boundaries. Its directly relevant mechanism is: Prompt templates can depend on metadata and automation beyond template text.
The idea “Test results must be adjudicated when expected outcomes become obsolete; interpret this while preserving the specified source of truth” explains another source-defined situation: A test fails because its expected action list references a removed legacy action. The correction must ensure that citizen information stays limited to the relevant case. That situation depends on: Test results must be adjudicated when expected outcomes become obsolete. The present question instead concerns a prompt template is deployed but invokes a Flow not present or active in production. The correction must ensure that student records never cross program authorization boundaries. Its directly relevant mechanism is: Prompt templates can depend on metadata and automation beyond template text.