Chunking Strategy Factors for RAG
Which THREE factors should be considered when designing a chunking strategy for a RAG application?
Quick Answer
The answer is the embedding model’s maximum input tokens, document structure, and desired retrieval granularity. These three factors directly govern how effectively a RAG application can split source content into meaningful, searchable pieces without losing context or exceeding the model’s processing limits. The embedding model’s token limit sets a hard ceiling on chunk size, while document structure—such as paragraphs or sections—guides natural breakpoints, and retrieval granularity determines whether you need fine-grained answers or broader context. On the Oracle Cloud Infrastructure Generative AI Professional 1Z0-1127 exam, this question tests your understanding of pre-retrieval optimization, often appearing as a “select three” item with distractors like GPU availability or indexing methods, which are irrelevant to chunking design. A common trap is confusing post-chunking indexing steps with pre-chunking strategy factors. To remember, think of the three C’s: Capacity (token limit), Coherence (document structure), and Coverage (retrieval granularity).
⚠ Common exam trap
A common misconception is that hardware resources like GPUs influence data preprocessing decisions, but chunking is purely a data design choice independent of compute capacity.
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
✓
Desired granularity of retrieval
The desired granularity of retrieval determines how much context is returned per chunk. Fine-grained chunks (e.g., sentences) improve precision for specific answers, while coarse chunks (e.g., paragraphs) provide broader context. This directly impacts the relevance and completeness of the retrieved passages in a RAG pipeline.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Desired granularity of retrieval
Why this is correct
Smaller chunks allow more precise retrieval; larger chunks provide more context.
- ✗
Number of GPUs available
Why it's wrong here
GPU count affects inference speed, not chunk design.
- ✗
Database indexing method
Why it's wrong here
Indexing method (e.g., HNSW) is chosen after chunking.
- ✓
Document structure
Why this is correct
Logical breaks (paragraphs, headings) guide natural chunk boundaries.
- ✓
Embedding model's maximum input tokens
Why this is correct
Each chunk must fit within the model's token limit.
Go deeper
Related to this question
About these practice questions
This 1Z0-1127-25 question is part of Courseiva's 768-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 →
Same concept, more angles
2 more ways this is tested on 1Z0-1127-25
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. What is the primary purpose of chunking documents in a RAG pipeline?
easy- A.To improve embedding quality
- B.To speed up training
- C.To reduce storage costs
- ✓ D.To ensure each chunk fits within the model's context window
Why D: The primary purpose of chunking documents in a RAG pipeline is to divide large documents into smaller, manageable pieces that each fit within the model's context window. This ensures that the retrieval step can fetch relevant chunks without exceeding the token limit of the LLM, which would otherwise cause truncation or failure to process the input.
Variation 2. A RAG system returns irrelevant chunks even though the embedding model and vector index are correctly configured. After reviewing, the chunks are too large and contain extraneous information. Which combination of adjustments should be made to improve relevance?
hard- A.Increase chunk overlap only.
- B.Decrease chunk size and increase chunk overlap.
- C.Use semantic chunking and adjust topK.
- ✓ D.Reduce chunk size, increase overlap, and adjust topK.
Why D: Reducing chunk size removes extraneous information, increasing overlap ensures context continuity across smaller chunks, and adjusting topK limits the number of retrieved chunks to the most relevant ones. This combination directly addresses the problem of large chunks containing irrelevant data while maintaining retrieval precision.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 1Z0-1127-25 practice question is part of Courseiva's free Oracle 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 1Z0-1127-25 exam.