Question 210
At Redfern Aviation, a supplier operations group is improving spare-part quotations following a quarterly access review (SF-T10-02). The administrator observes that a prompt template is deployed but invokes a Flow not present or active in production. Any fix must ensure that supplier prices are never shown outside entitled teams. Which action best addresses the issue while preserving the stated requirement?
Explanation
Correct Answer
The documented failure is that a prompt template is deployed but invokes a Flow not present or active in production. Include required Flow and template dependencies in a controlled deployment plan for Redfern Aviation's spare-part quotations workflow (SF-T10-02) while respecting that supplier prices are never shown outside entitled teams. Its outcome is not established merely by changing instructions: In a controlled Quote acceptance test, the production prompt resolves all referenced automation resources successfully; the record is retained under Redfern Aviation's rollout (SF-T10-02). The underlying reason is that Prompt templates can depend on metadata and automation beyond template text. In this spare-part quotations scenario, this separates supported agent behavior from assumptions about the AI model.
Incorrect Answers
The action “Validate and activate the intended prompt template version after deployment; implement it with a named deployment owner” addresses a separate source case: 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. Its underlying reason is: Deployment and activation are separate steps in prompt lifecycle. This question instead describes a prompt template is deployed but invokes a Flow not present or active in production. The correction must ensure that supplier prices are never shown outside entitled teams. The original answer “Include required Flow and template dependencies in a controlled deployment plan; implement it before the next environment promotion” targets that failure because prompt templates can depend on metadata and automation beyond template text.
The action “Replace hard-coded environment-specific references with approved context bindings; implement it and keep the business rule enforceable” addresses a separate source 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 underlying reason is: Reusable templates require portable bindings for environment-specific context. This question instead describes a prompt template is deployed but invokes a Flow not present or active in production. The correction must ensure that supplier prices are never shown outside entitled teams. The original answer “Include required Flow and template dependencies in a controlled deployment plan; implement it before the next environment promotion” targets that failure because prompt templates can depend on metadata and automation beyond template text.
The action “Retain known-good versions and use a controlled activation or rollback procedure; implement it with traceable change approval” addresses a separate source case: A newly activated agent version gives an incorrect action routing during rollout. The correction must ensure that donor details cannot be revealed across accounts. Its underlying reason is: Agent lifecycle requires version control and recoverable release states. This question instead describes a prompt template is deployed but invokes a Flow not present or active in production. The correction must ensure that supplier prices are never shown outside entitled teams. The original answer “Include required Flow and template dependencies in a controlled deployment plan; implement it before the next environment promotion” targets that failure because prompt templates can depend on metadata and automation beyond template text.