Bird
0
0

Why does Kafka require group.instance.id to be unique within a consumer group when using static group membership?

hard📝 Conceptual Q10 of 15
Kafka - Consumer Groups

Why does Kafka require group.instance.id to be unique within a consumer group when using static group membership?

ATo uniquely identify each consumer instance and avoid session conflicts
BTo enable automatic offset commits
CTo allow consumers to share the same partitions
DTo increase the number of partitions in a topic
Step-by-Step Solution
Solution:

  1. Step 1: Role of group.instance.id

    This ID uniquely identifies a consumer instance in the group for static membership.

  2. Step 2: Preventing conflicts

    Uniqueness avoids session conflicts and ensures Kafka can track consumer membership correctly.

  3. Final Answer:

    To uniquely identify each consumer instance and avoid session conflicts -> Option A

  4. Quick Check:

    Unique IDs prevent session conflicts = B [OK]
Quick Trick: Unique IDs avoid session conflicts in static groups [OK]
Common Mistakes:
  • Thinking it controls offset commits
  • Assuming consumers share partitions by ID
  • Confusing with topic partition count

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kafka Quizzes
Consumer Groups - Why consumer groups enable parallel processing - Quiz 2easy Consumers - Auto-commit vs manual commit - Quiz 5medium Consumers - Consumer poll loop - Quiz 4medium Kafka Basics and Event Streaming - First message (produce and consume) - Quiz 4medium Kafka Basics and Event Streaming - Event streaming concept - Quiz 6medium Kafka Basics and Event Streaming - Kafka vs RabbitMQ vs Redis Pub/Sub - Quiz 6medium Kafka Cluster Architecture - Leader election - Quiz 1easy Kafka Cluster Architecture - Broker nodes - Quiz 4medium Producers - Message key and value - Quiz 7medium Producers - Batching and linger configuration - Quiz 5medium