AI0-001 Implementing AI Solutions Practice Question
Which chunking strategy for RAG is MOST appropriate when documents have a natural hierarchical structure (e.g., sections, subsections)?
⚠ Common exam trap
AI0-001 often tests the misconception that any chunking strategy works equally well for all documents, but the key is matching the strategy to the document's inherent structure—hierarchical chunking is specifically designed for documents with natural hierarchies.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Hierarchical chunking that preserves document structure
Hierarchical chunking is designed to respect the document's inherent structure—such as sections, subsections, and paragraphs—by creating chunks that align with these boundaries. This preserves the logical flow and context, which is crucial for retrieval-augmented generation (RAG) because the retriever can fetch coherent units that match the query's intent. By maintaining the hierarchy, the system can also leverage parent-child relationships to improve retrieval accuracy and generation quality.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Hierarchical chunking that preserves document structure
Why this is correct
Hierarchical chunking preserves the document's section and subsection boundaries, embedding each node with its parent context intact. This directly satisfies the stem's requirement for natural hierarchical structure, unlike fixed-size or semantic splitting, which sever headings from their content and degrade retrieval precision during Microsoft Entra ID-secured RAG queries.
- ✗
Fixed-size chunking with no overlap
Why it's wrong here
Fixed-size chunking with no overlap splits purely by token count, so section and subsection boundaries fall mid-chunk and hierarchy is lost. It is tempting for uniform, unstructured text where simplicity and predictable chunk sizes matter, but the stem's documents already expose their hierarchy, which should drive the split points instead.
- ✗
Semantic chunking based on sentence boundaries
Why it's wrong here
Semantic chunking splits at sentence boundaries by meaning, which can cut across section and subsection headings, discarding the explicit hierarchy the stem specifies. It is tempting for unstructured prose where topic shifts are not marked, but here the document already declares its structure through headings, so splitting on those headings preserves parent-child context.
- ✗
Random chunking with varying sizes
Why it's wrong here
Random chunking with varying sizes ignores the document's section and subsection boundaries, so retrieved passages mix unrelated headings and lose the hierarchy the stem requires. It is tempting when text has no discernible structure and uniform splitting risks cutting mid-topic, but here the structure is explicit and should be chunked along those natural divisions.
About these practice questions
This AI0-001 question is part of Courseiva's 962-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CompTIA exam blueprint
This AI0-001 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AI0-001 exam.