引導式測驗 · 中等 等級
文件分塊策略測驗
查看區塊邊界、重疊、語義和結構分裂,以及經驗結果如何因資料集而異。比較語料庫上的配置。
問題 1 的 8
What does Amazon Bedrock say its default chunking approach does?
預覽每個問題8 問題
當您參加測驗時,就會出現答案和解釋。
- 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
- 非常小的區塊和非常大的區塊之間的主要權衡是什麼?
- 小塊的嵌入總是比較慢
- 大塊永遠無法檢索
- 小塊是精確的,但失去了上下文;大塊保留了上下文但削弱了相關性
- 沒有有意義的區別
- 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