Search internal documents by meaning.
Return only documents whose department and publication scope match the user.
Which design is appropriate?
Combine semantic similarity with metadata and authorization filters so a highly similar but unauthorized document is not returned.
Detailed explanation
Semantic similarity alone is not an authorization check.
Search does not require exposing protected documents.
RAG must not bypass source-data permissions.
This loses the access boundary.
Check official documentation
Compare the following points with the official documentation.
Amazon Bedrock Knowledge Bases公式のメタデータフィルターとデータアクセス設計を確認する。
Official references
What to confirm
類似度検索と認可フィルターを別の条件として説明できる。
Key points
- Metadata
- Access scope
- Similarity and authorization
Notes
- Environment: AWS公式AIF-C01試験ガイドとAWS公式ドキュメントの確認
- Compare the definition with the AIF-C01 objective and the service documentation before applying it.
- Keep the concept separate from a particular answer choice or implementation step.
Foundation review
Relevance is not permission
A semantically close document must still pass the access policy for the requesting principal.
Filter ordering
Applying scope constraints as part of retrieval helps prevent unauthorized content from entering context.