Question 620
At Redfern Aviation, a supplier operations group is improving spare-part quotations during cross-channel acceptance testing (SF-P02-01). The administrator observes that regional teams handwrite inconsistent product descriptions despite having approved CRM product facts. Any fix must ensure that supplier prices are never shown outside entitled teams. Which observable result would best demonstrate that the correction actually worked?
Explanation
Correct Answer
This is the direct acceptance signal for the reported failure: In a controlled Quote acceptance test, two eligible users generate consistent product descriptions from the same approved source fields; the record is retained under Redfern Aviation's rollout (SF-P02-01). The chosen correction was to create a reusable template that grounds generation in the approved product data and brand instructions; the measurement therefore tests the relevant source, routing or authorization outcome rather than unrelated activity.
Incorrect Answers
The proposed observation “An authorized agent invokes the record-field prompt and the summary references the intended case only; confirm this using a least-privilege test identity” would check a different original case: 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. Its mechanism is: Prompt Builder creates reusable Salesforce-grounded prompt templates instead of unmanaged external text entry. In the present case, regional teams handwrite inconsistent product descriptions despite having approved CRM product facts. The correction must ensure that supplier prices are never shown outside entitled teams; the more direct acceptance evidence is “Two eligible users generate consistent product descriptions from the same approved source fields; confirm this and compare with approved baseline behavior” because a reusable prompt template standardizes instructions and connects them to trusted contextual data.
The proposed observation “The cleanup runs under documented business rules without a generative response being used as the control; confirm this while testing the unauthorized case” would check a different original case: 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. Its mechanism is: Prompt Builder generates contextual text and should not replace deterministic business-rule execution. In the present case, regional teams handwrite inconsistent product descriptions despite having approved CRM product facts. The correction must ensure that supplier prices are never shown outside entitled teams; the more direct acceptance evidence is “Two eligible users generate consistent product descriptions from the same approved source fields; confirm this and compare with approved baseline behavior” because a reusable prompt template standardizes instructions and connects them to trusted contextual data.
The proposed observation “Flow debug confirms expected input mapping and records the generated output; confirm this using a least-privilege test identity” would check a different original 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 mechanism is: A template invocation depends on correct input bindings and execution context. In the present case, regional teams handwrite inconsistent product descriptions despite having approved CRM product facts. The correction must ensure that supplier prices are never shown outside entitled teams; the more direct acceptance evidence is “Two eligible users generate consistent product descriptions from the same approved source fields; confirm this and compare with approved baseline behavior” because a reusable prompt template standardizes instructions and connects them to trusted contextual data.