Enforce authorization before disclosure
Apply the current user’s access rules to retrieval and every relevant storage layer. Do not retrieve confidential passages and ask the model to hide them. Scope caches and logs carefully so one tenant’s evidence cannot become another tenant’s context.
Propagate changes and deletions
Track document versions through source storage, chunks, embeddings, caches, and derived outputs. Define how quickly revocations and deletions take effect. A successfully deleted source file does not prove every derived copy has disappeared.
Evaluate coupled failure modes
Test stale permissions, conflicting versions, poisoned documents, exact identifiers, and cross-tenant queries. Separate retrieval recall from answer faithfulness. Require provenance that lets you reconstruct which sources and rules were used for a consequential answer.
A worked example
Invalidate or reauthorize affected cache entries and enforce permissions on each response. Review all derived stores and logs. A document-level check performed only during indexing is insufficient.
The point: Authorization can change after the content was indexed or cached.
Before you take the exam
Explain these concepts in your own words, work through a different example, and describe why the tempting alternatives fail. Use the references to go deeper.