ガイド連動クイズ · 中 レベル

ドキュメントチャンク戦略に関するクイズ

チャンクの境界、重複、意味論的および構造的分割、および経験的結果がデータセットによってどのように異なるかを確認します。コーパス上の構成を比較します。

関連するガイドパスドキュメントのチャンク化戦略
質問 1 の 8

What does Amazon Bedrock say its default chunking approach does?

すべての質問をプレビューする8 質問

クイズに答えると、答えと解説が表示されます。

  1. 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
  2. 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
  3. 非常に小さなチャンクと非常に大きなチャンクの間の主なトレードオフは何ですか?
    • 小さなチャンクは埋め込みに常に時間がかかります
    • 大きなチャンクは決して取得できません
    • 小さなチャンクは正確ですが、コンテキストが失われます。大きなチャンクはコンテキストを保持しますが、関連性を薄めます
    • 意味のある違いはありません
  4. 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
  5. 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
  6. 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
  7. 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
  8. 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