A policy document has been revised.
Do not return the old version and keep changes traceable.
Choose two appropriate practices.
Manage document version and publication metadata, then synchronize additions, updates, and deletions with the retrieval index.
Detailed explanation
Expired or withdrawn content can cause incorrect answers.
Changing the source alone may leave stale chunks in the index.
These attributes distinguish the effective document from an old version.
The retrieved content and version would remain inconsistent.
Check official documentation
Compare the following points with the official documentation.
Amazon Bedrock Knowledge Bases公式のデータ同期・取り込みとS3バージョニング情報を確認する。
Official references
What to confirm
文書ライフサイクルと検索インデックス更新を一体で設計できる。
Key points
- Versioning
- Synchronization
- Old-version removal
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
Change propagation
Changing a source file without updating its index can leave old content available to retrieval.
Withdrawal boundary
Deleting or unpublishing a source should also trigger removal or restriction of its derived index data.