What is the expected behavior and why is static membership important here?
hard📝 Application Q15 of 15
Kafka - Consumer Groups
You have a Kafka consumer group with 3 consumers using static membership via group.instance.id. One consumer crashes and restarts quickly with the same group.instance.id. What is the expected behavior and why is static membership important here?
AThe group pauses all consumption until manual intervention
BThe group avoids a rebalance, so processing continues smoothly with minimal delay
CThe restarted consumer must use a new <code>group.instance.id</code> or it will be rejected
DThe group triggers a rebalance to reassign partitions to other consumers immediately
Step-by-Step Solution
Solution:
Step 1: Analyze static membership effect on consumer restart
Static membership keeps the consumer identity stable, so a quick restart does not cause a rebalance.
Step 2: Understand impact on group processing
Because no rebalance occurs, partition assignments remain unchanged, allowing smooth and low-latency processing.
Final Answer:
The group avoids a rebalance, so processing continues smoothly with minimal delay -> Option B
Quick Check:
Static membership prevents rebalance on quick restart [OK]
Quick Trick:Static membership keeps group stable during quick restarts [OK]
Common Mistakes:
Expecting rebalance on every consumer restart
Thinking new ID is required after crash
Assuming group pauses automatically
Master "Consumer Groups" in Kafka
9 interactive learning modes - each teaches the same concept differently
