2.2Standard
Split long policies for retrieval.
Preserve meaning at section boundaries.
Choose two practices.
× Incorrect
Prefer semantic boundaries and evaluate overlap against context preservation, retrieval quality, duplicate tokens, and cost.
Detailed explanation
CorrectSplit at headings or paragraph boundaries when possible
Chunks retain meaningful units.
IncorrectIncrease overlap without limit
Duplication and cost grow.
CorrectEvaluate overlap against retrieval quality, context, duplicate tokens, and cost
Boundary context is balanced with expense.
IncorrectUse fixed characters and ignore headings
Meaningful boundaries may break.
Check official documentation
Compare the following points with the official documentation.
AWS公式AIF-C01 Domain 2.2のデータ分割と検索拡張生成を確認する。
Official references
What to confirm
チャンク境界と重なりを品質・コストで調整できる。
Key points
- Chunk
- Overlap
- Boundary
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
Chunk
A bounded fragment of a document used for embedding, retrieval, or context assembly.
Chunk overlap
Content repeated between adjacent fragments to preserve context near a split.
Question IDAWS-AIF-322
EnvironmentAWS公式AIF-C01試験ガイドとAWS公式ドキュメントの確認
Last technical review2026-08-20
Report an error or rights issue