Question 780
At Willow Tech, a sales operations organization is improving subscription upgrades following a quarterly access review (SF-P23-01). The administrator observes that a template worked before a model upgrade but now produces noncompliant formatting. Any fix must ensure that quoted amounts use authorized account and price-book records. Which continuing control best prevents this issue from recurring?
Explanation
Correct Answer
The preventive control directly addresses repeat failures: Require model-change signoff and keep baseline comparisons; require the check in the next release review at Willow Tech (SF-P23-01). It complements the corrective action, validate proposed model selection against approved access and run versioned regression tests, and protects the explicit condition that quoted amounts use authorized account and price-book records.
Incorrect Answers
This safeguard, “Review user grants and approved model availability together; review it with audit evidence from regression testing”, reduces a different source-defined risk: An administrator restricts which users can edit templates but leaves AI model access unrestricted. The correction must ensure that plant access boundaries are not weakened by chatbot replies. That risk depends on: Template permissions and model selection restrictions govern different risks. The recurring problem here is a template worked before a model upgrade but now produces noncompliant formatting. The correction must ensure that quoted amounts use authorized account and price-book records. The originally selected control “Require model-change signoff and keep baseline comparisons; review it and confirm the control remains effective after release” is more specific because a model change can alter generation behavior without changing template text.
This safeguard, “Recheck model allowlists when new models are introduced; review it as part of periodic access and quality reviews”, reduces a different source-defined risk: Policy prohibits use of an unapproved model in production prompt generation. The correction must ensure that production changes remain gated by approval. That risk depends on: Model governance must explicitly constrain the available model choices. The recurring problem here is a template worked before a model upgrade but now produces noncompliant formatting. The correction must ensure that quoted amounts use authorized account and price-book records. The originally selected control “Require model-change signoff and keep baseline comparisons; review it and confirm the control remains effective after release” is more specific because a model change can alter generation behavior without changing template text.
This safeguard, “Test field compatibility and page assignment before activation; review it and retest after dependent metadata changes”, reduces a different source-defined risk: A sales team expects a generated note to populate one writable account field directly. The correction must ensure that capacity limits and customer entitlements are enforced deterministically. That risk depends on: Field Generation templates target supported writable record fields rather than arbitrary output collections. The recurring problem here is a template worked before a model upgrade but now produces noncompliant formatting. The correction must ensure that quoted amounts use authorized account and price-book records. The originally selected control “Require model-change signoff and keep baseline comparisons; review it and confirm the control remains effective after release” is more specific because a model change can alter generation behavior without changing template text.