Question 770
At Trillium Services, an internal HR help desk is improving employee leave guidance after a knowledge-policy revision (SF-D02-01). The administrator observes that a revised employee handbook was uploaded but an agent still cites the prior edition. Any fix must ensure that employee case files are accessible only to the case owner. Which continuing control best prevents this issue from recurring?
Explanation
Correct Answer
The preventive control directly addresses repeat failures: Monitor data-sync and indexing completion after each publication; require the check in the next release review at Trillium Services (SF-D02-01). It complements the corrective action, refresh the library ingestion and search assets then retest retrieval against the revised passage, and protects the explicit condition that employee case files are accessible only to the case owner.
Incorrect Answers
This safeguard, “Run cross-tenant retrieval-denial checks after source changes; review it and confirm the control remains effective after release”, reduces a different source-defined risk: Two subsidiaries share a platform but must not retrieve each other's knowledge documents. The correction must ensure that member records cannot be exposed to other members. That risk depends on: Knowledge availability requires both indexing and audience-aware scope controls. The recurring problem here is a revised employee handbook was uploaded but an agent still cites the prior edition. The correction must ensure that employee case files are accessible only to the case owner. The originally selected control “Monitor data-sync and indexing completion after each publication; review it before expanding channel availability” is more specific because a library answer depends on the freshness of its ingested and indexed content.
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 revised employee handbook was uploaded but an agent still cites the prior edition. The correction must ensure that employee case files are accessible only to the case owner. The originally selected control “Monitor data-sync and indexing completion after each publication; review it before expanding channel availability” is more specific because a library answer depends on the freshness of its ingested and indexed content.
This safeguard, “Evaluate chunk boundaries on headings, procedures, and exceptions; review it with audit evidence from regression testing”, reduces a different source-defined risk: A twenty-page support guide is indexed as one oversized passage and retrieval is imprecise. The correction must ensure that employee procedures cannot be exposed to anonymous users. That risk depends on: Chunking trades passage granularity against preservation of useful context. The recurring problem here is a revised employee handbook was uploaded but an agent still cites the prior edition. The correction must ensure that employee case files are accessible only to the case owner. The originally selected control “Monitor data-sync and indexing completion after each publication; review it before expanding channel availability” is more specific because a library answer depends on the freshness of its ingested and indexed content.