Guide-linked quiz · Medium Level
Jamba Hybrid Transformer-Mamba Models Quiz
Review original Jamba hybrid layers, mixture-of-experts routing, recurrent state, attention cache growth, and workload-specific long-context evaluation.
Question 1 of 8
Which two core layer types does Jamba interleave?
Preview every question8 questions
Answers and explanations appear as you take the quiz.
- Which two core layer types does Jamba interleave?
- Convolutional and pooling layers
- RNN and CNN layers
- Transformer attention and Mamba state-space layers
- Diffusion and attention layers
- What additional technique does Jamba use to increase capacity while keeping active parameters low?
- Mixture-of-experts (MoE)
- Knowledge distillation
- Quantization-aware training
- Reinforcement learning from human feedback
- How does a Mamba layer's recurrent representation differ from an attention layer's KV cache?
- It removes every model parameter from memory
- It skips all tokens beyond the first one
- It stores an independent full copy of every earlier attention matrix
- It maintains a fixed-size recurrent state instead of retaining a growing set of past keys and values
- What context window did the first Jamba model support?
- 4K tokens
- 256K tokens
- 32K tokens
- 8 million tokens
- What is a reason to retain attention components alongside state-space layers in a Jamba-style hybrid?
- To combine different access and representation mechanisms while evaluating their quality-efficiency tradeoff
- To guarantee perfect retrieval of every token on every task
- To make all attention computation independent of sequence length
- To eliminate the need for any model evaluation
- How should Jamba's reported long-context memory benefit be evaluated for deployment?
- Assume every 256K request fits any single GPU
- Count only the recurrent state while ignoring weights and attention cache
- Measure the actual model, precision, batch size, context, and hardware configuration
- Treat every hybrid model as having zero sequence-state cost
- Does original Jamba's use of many Mamba layers make the whole model's sequence memory constant as input length grows?
- Yes; every hybrid attention cache has a fixed one-token size
- No; its retained attention layers still store a growing KV cache
- Yes; model weights disappear once the sequence becomes long
- Only the tokenizer's file size changes
- Why are total MoE parameters and active parameters per token different quantities in Jamba?
- Every stored expert is necessarily deleted when inactive
- A token must run all experts regardless of routing
- The model's supported context directly sets its vocabulary size
- Routing can activate only a subset of stored experts for each token
Keep testing yourself
More quizzes picked for your level.