Question 140
At Juniper Civic, a public agency service counter is improving permit status while preparing a production promotion (SF-P15-01). The administrator observes that template preview looks correct as text but the actual resolved prompt lacks the latest case comment. Any fix must ensure that citizen information stays limited to the relevant case. Which action best addresses the issue while preserving the stated requirement?
Explanation
Correct Answer
The documented failure is that template preview looks correct as text but the actual resolved prompt lacks the latest case comment. Inspect resolved prompt resources and test with a case whose comments changed after setup for Juniper Civic's permit status workflow (SF-P15-01) while respecting that citizen information stays limited to the relevant case. Its outcome is not established merely by changing instructions: In a controlled Permit__c acceptance test, preview shows the new case comment in the resolved input before response generation; the record is retained under Juniper Civic's rollout (SF-P15-01). The underlying reason is that Prompt instructions and resolved data are distinct; both affect the final output. In this permit status scenario, this separates supported agent behavior from assumptions about the AI model.
Incorrect Answers
The action “Preview, validate, and activate the intended revised template version before invoking it; implement it within the documented Salesforce configuration” addresses a separate source case: 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 underlying reason is: A saved draft is not necessarily the active executable prompt template version. This question instead describes 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. The original answer “Inspect resolved prompt resources and test with a case whose comments changed after setup; implement it with traceable change approval” targets that failure because prompt instructions and resolved data are distinct; both affect the final output.
The action “Bind the required template inputs in Flow and test execution with representative records; implement it with least-privilege execution” addresses a separate source case: 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. Its underlying reason is: A template invocation depends on correct input bindings and execution context. This question instead describes 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. The original answer “Inspect resolved prompt resources and test with a case whose comments changed after setup; implement it with traceable change approval” targets that failure because prompt instructions and resolved data are distinct; both affect the final output.
The action “Validate proposed model selection against approved access and run versioned regression tests; implement it with a controlled rollback path” addresses a separate source case: A template worked before a model upgrade but now produces noncompliant formatting. The correction must ensure that quoted amounts use authorized account and price-book records. Its underlying reason is: A model change can alter generation behavior without changing template text. This question instead describes 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. The original answer “Inspect resolved prompt resources and test with a case whose comments changed after setup; implement it with traceable change approval” targets that failure because prompt instructions and resolved data are distinct; both affect the final output.