Question 440
At Keystone Telecom, a technical contact center is improving network fault support as a new data source is onboarded (SF-A23-03). The administrator observes that a template returns a confidential account field in a customer-facing response. Any fix must ensure that production changes remain gated by approval. Which continuing control best prevents this issue from recurring?
Explanation
Correct Answer
The preventive control directly addresses repeat failures: Review sensitive field exposure at every release; require the check in the next release review at Keystone Telecom (SF-A23-03). It complements the corrective action, remove unauthorized source access and validate field-level permission enforcement, and protects the explicit condition that production changes remain gated by approval.
Incorrect Answers
This safeguard, “Include unauthorized object queries in regression testing; review it and confirm the control remains effective after release”, reduces a different source-defined risk: An action attempts to read a protected custom object based only on a user's natural-language request. The correction must ensure that member records cannot be exposed to other members. That risk depends on: An agent conversation is not an authorization bypass for CRM data. The recurring problem here is a template returns a confidential account field in a customer-facing response. The correction must ensure that production changes remain gated by approval. The originally selected control “Review sensitive field exposure at every release; review it before expanding channel availability” is more specific because field-level security still governs agent grounding and action results.
This safeguard, “Maintain approval and audit trail tests for write actions; review it with a documented exception process”, reduces a different source-defined risk: An agent would close a high-severity case directly without the required human approval. The correction must ensure that service changes follow approved warranty conditions. That risk depends on: Sensitive agent operations need deterministic approval gates beyond conversational requests. The recurring problem here is a template returns a confidential account field in a customer-facing response. The correction must ensure that production changes remain gated by approval. The originally selected control “Review sensitive field exposure at every release; review it before expanding channel availability” is more specific because field-level security still governs agent grounding and action results.
This safeguard, “Test information leakage between audience-specific agents; review it and retest after dependent metadata changes”, reduces a different source-defined risk: One shared bot mixes employee operational runbooks with public refund answers. The correction must ensure that capacity limits and customer entitlements are enforced deterministically. That risk depends on: Different agent audiences imply different trust, authorization and context boundaries. The recurring problem here is a template returns a confidential account field in a customer-facing response. The correction must ensure that production changes remain gated by approval. The originally selected control “Review sensitive field exposure at every release; review it before expanding channel availability” is more specific because field-level security still governs agent grounding and action results.