Question 650
At Aster Retail, a storefront service desk is improving order-support as a new data source is onboarded (SF-T11-02). The administrator observes that a revised prompt arrives in production but callers keep receiving the earlier active version. Any fix must ensure that customer order details stay within each authorized account. 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 Case acceptance test, a test invocation returns behavior from the intended active version; the record is retained under Aster Retail's rollout (SF-T11-02). The chosen correction was to validate and activate the intended prompt template version after deployment; the measurement therefore tests the relevant source, routing or authorization outcome rather than unrelated activity.
Incorrect Answers
The proposed observation “Production invocation uses current authorized records rather than sandbox IDs; confirm this using a representative sandbox fixture” would check a different original case: 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. Its mechanism is: Reusable templates require portable bindings for environment-specific context. In the present case, a revised prompt arrives in production but callers keep receiving the earlier active version. The correction must ensure that customer order details stay within each authorized account; the more direct acceptance evidence is “A test invocation returns behavior from the intended active version; confirm this while testing the unauthorized case” because deployment and activation are separate steps in prompt lifecycle.
The proposed observation “The production prompt resolves all referenced automation resources successfully; confirm this and confirm the resulting trace” would check a different original case: 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 mechanism is: Prompt templates can depend on metadata and automation beyond template text. In the present case, a revised prompt arrives in production but callers keep receiving the earlier active version. The correction must ensure that customer order details stay within each authorized account; the more direct acceptance evidence is “A test invocation returns behavior from the intended active version; confirm this while testing the unauthorized case” because deployment and activation are separate steps in prompt lifecycle.
The proposed observation “The test run shows protected actions remain blocked for bypass attempts; confirm this and confirm the resulting trace” would check a different original case: An agent responds correctly to normal refund requests but fails when a user tries to bypass the refund rule. The correction must ensure that customer order details stay within each authorized account. Its mechanism is: Positive-only testing cannot establish guardrail behavior. In the present case, a revised prompt arrives in production but callers keep receiving the earlier active version. The correction must ensure that customer order details stay within each authorized account; the more direct acceptance evidence is “A test invocation returns behavior from the intended active version; confirm this while testing the unauthorized case” because deployment and activation are separate steps in prompt lifecycle.