Question 10
At Bluehaven University, an internal student services team is improving student advising while preparing a production promotion (SF-T10-01). The administrator observes that a prompt template is deployed but invokes a Flow not present or active in production. Any fix must ensure that student records never cross program authorization boundaries. 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 Bluehaven University's student advising workflow (SF-T10-01) while respecting that student records never cross program authorization boundaries. Its outcome is not established merely by changing instructions: In a controlled Student_Request__c acceptance test, the production prompt resolves all referenced automation resources successfully; the record is retained under Bluehaven University's rollout (SF-T10-01). The underlying reason is that Prompt templates can depend on metadata and automation beyond template text. In this student advising 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 student records never cross program authorization boundaries. The original answer “Include required Flow and template dependencies in a controlled deployment plan; implement it with a controlled rollback path” 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 student records never cross program authorization boundaries. The original answer “Include required Flow and template dependencies in a controlled deployment plan; implement it with a controlled rollback path” targets that failure because prompt templates can depend on metadata and automation beyond template text.
The action “Use a properly configured sandbox with safe representative data for action tests; implement it with traceable change approval” addresses a separate source case: A team proposes batch-testing an order cancellation agent directly in production. The correction must ensure that supplier prices are never shown outside entitled teams. Its underlying reason is: Agent tests can invoke business actions and therefore require environmental isolation. This question instead describes 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. The original answer “Include required Flow and template dependencies in a controlled deployment plan; implement it with a controlled rollback path” targets that failure because prompt templates can depend on metadata and automation beyond template text.