Guide-linked quiz · Medium Level
Multi-Query Attention Quiz
Test how Multi-Query Attention shares key-value heads, reduces cache traffic, and relates to grouped-query attention in decoder models.
Question 1 of 8
What does Multi-Query Attention share across all attention heads?
Preview every question8 questions
Answers and explanations appear as you take the quiz.
- What does Multi-Query Attention share across all attention heads?
- A single set of keys and values
- The query projections
- The softmax temperature
- The output layer weights
- What is the primary bottleneck that MQA addresses during autoregressive generation?
- Floating-point compute throughput
- Memory bandwidth from loading the KV cache
- The number of training epochs
- Tokenizer vocabulary size
- By roughly what factor does MQA shrink the KV cache?
- By the sequence length
- By the batch size
- By the number of attention heads
- It does not change the KV cache size
- What is the main trade-off of using MQA?
- Much slower inference
- It can no longer use multiple heads at all
- It requires far more training data
- A modest drop in model quality
- Which variant sits between standard multi-head attention and MQA?
- Grouped-Query Attention
- Sliding-Window Attention
- Flash Attention
- Sparse Attention
- Who proposed Multi-Query Attention?
- Geoffrey Hinton
- Noam Shazeer
- Yann LeCun
- Andrej Karpathy
- In Multi-Query Attention, what remains separate for each attention head?
- The shared key projection
- The shared value projection
- The query projection
- The token sequence itself
- How does Grouped-Query Attention differ from standard MQA?
- It shares query projections but gives every head separate keys and values
- It removes attention and replaces it with a recurrent layer
- It groups output vocabulary tokens instead of attention heads
- It shares keys and values within several groups of query heads rather than across all heads at once
Keep testing yourself
More quizzes picked for your level.