Kafka easy
What is the primary architectural advantage of using a 'Consumer Group'?
- A It encrypts the data during transmission to prevent unauthorized access.
- B It allows a pool of consumers to divide the work of reading a topic, providing both horizontal scalability and fault tolerance (Load Balancing).
- C It enables the deletion of messages after they have been read by any member.
- D It provides a way to chat between different consumer instances.
Answer: B. It allows a pool of consumers to divide the work of reading a topic, providing both horizontal scalability and fault tolerance (Load Balancing).
Kafka ensures that each partition is processed by exactly one member of the group. If you have 4 partitions and 4 consumers, they all work in parallel. If one consumer fails, its partitions are re-assigned to the remaining members.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- When implementing 'Exactly-Once Semantics' (EOS) in a Kafka stream, what is the role of the `isolation.level=read_committed` setting on the Consumer?
- Historically, which external service was required by Kafka to manage cluster hierarchy, metadata, and leader election status?
- Once a message is successfully appended to a Kafka partition log, what is its mutability status?
- In a Kafka cluster, what is the role of a 'Broker'?
- What is the primary indicator of a bottleneck in a Kafka consumer's processing logic?
- What is the primary architectural role of Apache Kafka in a distributed system?