Question 1easy
Why is chunking often described as the highest-leverage knob in a RAG system?
Question 2easy
You size chunks at '200 words'. Why can this silently break your token budget?
Question 3easy
What does a tokenizer like tiktoken give you that a plain .split() does not?
Question 4medium
In recursive character splitting, what is the ordering strategy for separators?
Question 5medium
What is the main advantage of splitting on natural boundaries over a fixed token window?
Question 6medium
Which capabilities does attaching metadata (source, section, position) to chunks unlock? (Select all that apply)
Question 7medium
When you filter retrieval by metadata (e.g. source='pricing.md'), when does the filter apply relative to similarity scoring?
Question 8hard
Parent-child (hierarchical) indexing resolves which tension?
Question 9hard
In the 'small-to-big' parent-child pattern, what is embedded and what is handed to the generator?
Question 10hard
When a single paragraph exceeds max_tokens, what does a well-built recursive splitter do? (Select all that apply)
Question 11medium
For an FAQ where each entry is a self-contained Q&A pair, what chunking approach usually works best?
Question 12medium
How should you decide on a chunk size for a new corpus?
Question 13medium
What unit should you size chunks in to reliably respect embedding and context-window limits? (one word)
Question 14hard
Name the indexing pattern that embeds small chunks for precise matching but returns larger surrounding chunks for context.