Question 300
At Northpoint Hospitality, a guest services desk is improving reservation help after a documented configuration change (SF-T12-02). The administrator observes that a prompt created in a sandbox references a test record identifier not present in production. Any fix must ensure that guest profile fields are used only with permitted access. Which continuing control best prevents this issue from recurring?
Explanation
Correct Answer
The preventive control directly addresses repeat failures: Scan prompts for hard-coded IDs before migration; require the check in the next release review at Northpoint Hospitality (SF-T12-02). It complements the corrective action, replace hard-coded environment-specific references with approved context bindings, and protects the explicit condition that guest profile fields are used only with permitted access.
Incorrect Answers
This safeguard, “Record active versions and compare resolved prompts; review it with audit evidence from regression testing”, reduces a different source-defined risk: 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. That risk depends on: Deployment and activation are separate steps in prompt lifecycle. The recurring problem here is a prompt created in a sandbox references a test record identifier not present in production. The correction must ensure that guest profile fields are used only with permitted access. The originally selected control “Scan prompts for hard-coded IDs before migration; review it and retest after dependent metadata changes” is more specific because reusable templates require portable bindings for environment-specific context.
This safeguard, “Validate dependency inventories before template deployment; review it and confirm the control remains effective after release”, reduces a different source-defined risk: 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. That risk depends on: Prompt templates can depend on metadata and automation beyond template text. The recurring problem here is a prompt created in a sandbox references a test record identifier not present in production. The correction must ensure that guest profile fields are used only with permitted access. The originally selected control “Scan prompts for hard-coded IDs before migration; review it and retest after dependent metadata changes” is more specific because reusable templates require portable bindings for environment-specific context.
This safeguard, “Maintain environment-specific deployment checklists; review it before expanding channel availability”, reduces a different source-defined risk: A service agent works in sandbox but its production deployment lacks dependent automation and entitlements. The correction must ensure that member records cannot be exposed to other members. That risk depends on: Agent migration is a dependency and permission deployment task, not just copying text instructions. The recurring problem here is a prompt created in a sandbox references a test record identifier not present in production. The correction must ensure that guest profile fields are used only with permitted access. The originally selected control “Scan prompts for hard-coded IDs before migration; review it and retest after dependent metadata changes” is more specific because reusable templates require portable bindings for environment-specific context.