Bird
0
0

Why does Kafka trigger a rebalance when a consumer's session timeout expires?

hard📝 Conceptual Q10 of 15
Kafka - Consumer Groups
Why does Kafka trigger a rebalance when a consumer's session timeout expires?
ABecause the consumer is considered dead and partitions must be reassigned
BBecause the consumer requested a manual rebalance
CBecause the broker wants to increase partition count
DBecause the consumer committed offsets late
Step-by-Step Solution
Solution:

  1. Step 1: Understand session timeout role

    Session timeout defines how long a consumer can be silent before considered dead.

  2. Step 2: Analyze rebalance trigger on timeout

    If timeout expires, Kafka assumes consumer left and triggers rebalance to reassign partitions.

  3. Final Answer:

    Because the consumer is considered dead and partitions must be reassigned -> Option A

  4. Quick Check:

    Session timeout expiry = consumer dead, triggers rebalance [OK]
Quick Trick: Session timeout expiry signals dead consumer, triggers rebalance [OK]
Common Mistakes:
  • Thinking consumer requested rebalance manually
  • Assuming broker increases partitions on timeout
  • Believing late offset commit triggers rebalance

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kafka Quizzes
Consumer Groups - Cooperative vs eager rebalancing - Quiz 9hard Kafka Basics and Event Streaming - Kafka CLI tools overview - Quiz 6medium Kafka Basics and Event Streaming - Event streaming concept - Quiz 5medium Kafka Basics and Event Streaming - Message broker architecture - Quiz 14medium Kafka Cluster Architecture - Leader election - Quiz 9hard Producers - Acknowledgment modes (acks=0, 1, all) - Quiz 15hard Producers - Serialization (String, JSON, Avro) - Quiz 15hard Producers - Why producers publish data - Quiz 6medium Topics and Partitions - Topic deletion and cleanup - Quiz 4medium Topics and Partitions - Topic deletion and cleanup - Quiz 8hard