quiz bu lëkkale ak tegtal · Diggante Niveau
Document Chunking Pexe Quiz
Xoolaat ay pexe, jaxasoo, xaaj semantik ak structurel, ak ni resultaa empirik yi mëna wuutee ci done yi. Teg leen tànneef yi ci corpus bi.
Laaj 1 de 8
What does Amazon Bedrock say its default chunking approach does?
Xoolaatal laaj bu nekk8 laaj
Sooy def quiz bi, tontu yi ak leeral yi dañuy feeñ.
- What does Amazon Bedrock say its default chunking approach does?
- Splits text into roughly 300-token chunks while preserving complete sentence boundaries
- Splits every document into one token
- Uses one chunk for every knowledge base regardless of size
- Groups documents by alphabetical title
- Why can the buffer size matter in semantic chunking?
- It changes the source document’s spelling
- It determines how many neighboring sentences are included when creating embeddings
- It identifies the correct speaker
- It specifies the model’s output vocabulary
- Lan mooy xéewal gi gëna mag ci diggante piyees yu ndaw lool ak yu mag lool?
- chunks yu ndaw yi ñoo gëna yeex dugg
- Mënuñu musa jëlaat ay piyees yu rëy
- Mbir yu ndaw yi dañu leer waaye duñu am muy tekki; ay pàcc yu yaatu dañuy tëye muy tekki waaye dañuy wàññi njariñ li
- Amul benn wuute bu am solo
- In Amazon Bedrock, what may its parsed-content chunker preserve as logical boundaries?
- Only individual characters
- Image colors and crop boxes
- The prompt’s output format
- Pages or sections
- How does Amazon Bedrock describe hierarchical chunking at retrieval time?
- It retrieves child chunks and can replace them with broader parent chunks
- It discards parent text and never returns broader context
- It merges all documents into one vector
- It converts every chunk to an image
- How does Amazon Bedrock’s semantic chunking propose boundaries between sentences?
- By sorting sentences alphabetically
- Using sentence-distance thresholds to identify less-similar adjacent sentences
- By splitting every document at the same character count
- By detecting speaker identity
- What did a 2026 chunking study find about overlap in its tested Natural Questions setup?
- It always doubled answer accuracy
- It eliminated all retrieval errors
- It increased indexing cost without a measurable answer-quality benefit
- It reduced indexing cost to zero
- What happened when retrieved context grew beyond about 2,500 tokens in that study?
- Accuracy rose without limit
- All questions became exact matches
- The retriever stopped using embeddings
- Answer quality showed a context cliff