Question 990
At Delta Transit, a passenger support center is improving service disruption updates while preparing a production promotion (SF-P02-02). The administrator observes that regional teams handwrite inconsistent product descriptions despite having approved CRM product facts. 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: A reusable prompt template standardizes instructions and connects them to trusted contextual data. In this service disruption updates scenario, this separates supported agent behavior from assumptions about the AI model. Because regional teams handwrite inconsistent product descriptions despite having approved CRM product facts, the intended response is to create a reusable template that grounds generation in the approved product data and brand instructions. An observable check is that two eligible users generate consistent product descriptions from the same approved source fields.
Incorrect Answers
The idea “Prompt Builder generates contextual text and should not replace deterministic business-rule execution; interpret this without inferring extra permissions from an LLM response” explains another source-defined situation: A nightly data cleanup requirement is being treated as a request for open-ended generated prose. The correction must ensure that customer order details stay within each authorized account. That situation depends on: Prompt Builder generates contextual text and should not replace deterministic business-rule execution. The present question instead concerns regional teams handwrite inconsistent product descriptions despite having approved CRM product facts. The correction must ensure that safety-critical changes need an attributable human approval. Its directly relevant mechanism is: A reusable prompt template standardizes instructions and connects them to trusted contextual data.
The idea “Prompt Builder creates reusable Salesforce-grounded prompt templates instead of unmanaged external text entry; interpret this as distinct from unrelated UI configuration” explains another source-defined situation: A support team copies case comments into a consumer chatbot to create CRM case summaries. The correction must ensure that student records never cross program authorization boundaries. That situation depends on: Prompt Builder creates reusable Salesforce-grounded prompt templates instead of unmanaged external text entry. The present question instead concerns regional teams handwrite inconsistent product descriptions despite having approved CRM product facts. The correction must ensure that safety-critical changes need an attributable human approval. Its directly relevant mechanism is: A reusable prompt template standardizes instructions and connects them to trusted contextual data.
The idea “Template access alone does not erase record and field permission boundaries; interpret this rather than assuming a generative instruction is an access rule” explains another source-defined situation: A service representative can see a generated-content feature but the template run is denied. The correction must ensure that escalations preserve only the needed guest context. That situation depends on: Template access alone does not erase record and field permission boundaries. The present question instead concerns regional teams handwrite inconsistent product descriptions despite having approved CRM product facts. The correction must ensure that safety-critical changes need an attributable human approval. Its directly relevant mechanism is: A reusable prompt template standardizes instructions and connects them to trusted contextual data.