Question 660
At Beacon Medical, an internal clinic IT service desk is improving employee IT triage during a least-privilege verification (SF-D06-01). The administrator observes that a help team needs answers from internal installation manuals rather than customer account fields. Any fix must ensure that employee identity is verified before accessing private tickets. Which continuing control best prevents this issue from recurring?
Explanation
Correct Answer
The preventive control directly addresses repeat failures: Validate library document coverage and retention permissions; require the check in the next release review at Beacon Medical (SF-D06-01). It complements the corrective action, ingest the approved manuals into an Agentforce Data Library and connect the correct retriever, and protects the explicit condition that employee identity is verified before accessing private tickets.
Incorrect Answers
This safeguard, “Monitor ingestion failures and index availability; review it and retest after dependent metadata changes”, reduces a different source-defined risk: A knowledge-backed agent has no useful results after initial library setup. The correction must ensure that guest profile fields are used only with permitted access. That risk depends on: Data-library setup is a pipeline with dependent indexing and retrieval stages. The recurring problem here is a help team needs answers from internal installation manuals rather than customer account fields. The correction must ensure that employee identity is verified before accessing private tickets. The originally selected control “Validate library document coverage and retention permissions; review it and confirm the control remains effective after release” is more specific because unstructured document knowledge and CRM record grounding serve different source needs.
This safeguard, “Retire obsolete chunks and review source precedence rules; review it with a documented exception process”, reduces a different source-defined risk: Two overlapping libraries contain conflicting versions of the same return policy. The correction must ensure that copyrighted manuscripts remain within the approved workspace. That risk depends on: Duplicate knowledge sources can make retrieval ambiguous even with correct prompts. The recurring problem here is a help team needs answers from internal installation manuals rather than customer account fields. The correction must ensure that employee identity is verified before accessing private tickets. The originally selected control “Validate library document coverage and retention permissions; review it and confirm the control remains effective after release” is more specific because unstructured document knowledge and CRM record grounding serve different source needs.
This safeguard, “Maintain separate index and retriever change records; review it with a documented exception process”, reduces a different source-defined risk: A team creates a search index and expects prompt templates to query it without a retriever. The correction must ensure that billing adjustments require verified eligibility. That risk depends on: Search indexes organize content; retrievers select relevant indexed content for a use case. The recurring problem here is a help team needs answers from internal installation manuals rather than customer account fields. The correction must ensure that employee identity is verified before accessing private tickets. The originally selected control “Validate library document coverage and retention permissions; review it and confirm the control remains effective after release” is more specific because unstructured document knowledge and CRM record grounding serve different source needs.