AI0-001 Implementing AI Solutions Practice Question
A team is implementing a document intelligence solution to extract key-value pairs from invoices. They plan to use a pre-trained vision-language model with a RAG pipeline that indexes invoice images. Which chunking strategy is BEST suited for invoice documents that have a consistent layout but vary in length?
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 groups lines into logical sections (header, line items, totals)
Invoices typically have sections (header, line items, totals). Hierarchical chunking preserves this structure, enabling retrieval at the section level. Fixed-size may split important fields, semantic chunking is less predictable on structured documents.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Semantic chunking based on sentence boundaries
Why it's wrong here
Sentence-boundary chunking splits label-value pairs such as invoice number and total across chunks, destroying the layout context a vision-language model needs. It suits prose documents, where sentence semantics carry meaning, not structured forms with consistent field positions.
- ✓
Hierarchical chunking that groups lines into logical sections (header, line items, totals)
Why this is correct
Hierarchical chunking preserves invoice structure by grouping lines into header, line items, and totals, so retrieval returns coherent key-value pairs rather than fragments. This satisfies the stem's constraint of consistent layout with variable length, where fixed-size splitting would sever field-label relationships.
- ✗
Fixed-size chunking with 512 tokens per chunk
Why it's wrong here
Fixed 512-token splits cut across field boundaries at arbitrary offsets, separating labels from their values and breaking the consistent layout. Fixed-size chunking is correct for uniform, unstructured text streams, not invoices where layout position defines each key-value pair.
- ✗
No chunking; pass the entire invoice as one document per query
Why it's wrong here
Passing whole invoices ignores the varying length: long documents exceed the model's context window and dilute retrieval precision across many fields. Whole-document indexing is correct for short, single-topic files, not variable-length forms needing field-level extraction.
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 by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.