3.1Standard
Policies must be split before indexing.
Preserve context while controlling cost.
Choose two designs.
× Incorrect
Split by semantic structure and measure a small overlap against retrieval quality and token cost.
Detailed explanation
IncorrectUse one fixed size without testing formats or question length
The design may not fit.
CorrectPreserve headings, paragraphs, and tables in appropriately sized chunks
Results retain context.
IncorrectPut the entire corpus in one giant chunk
Granularity and limits suffer.
CorrectTest a small overlap and measure retrieval quality and token cost
Boundary loss and cost can be compared.
Check official documentation
Compare the following points with the official documentation.
AWS公式AIF-C01 Domain 3.1のRAG、チャンク、埋め込み、検索を確認する。
Official references
What to confirm
文書構造と検索品質・費用を考慮してチャンク分割を調整できる。
Key points
- Chunk
- Overlap
- Retrieval quality
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 piece of source content stored or retrieved as one unit.
Chunk overlap
Repeated content between neighboring chunks that preserves context across boundaries.
Question IDAWS-AIF-420
EnvironmentAWS公式AIF-C01試験ガイドとAWS公式ドキュメントの確認
Last technical review2026-08-20
Report an error or rights issue