Kafka easy
What is the primary operational purpose of configuring a 'Replication Factor' greater than 1 for a topic?
- A To double the speed of consumer reads through parallelization.
- B Durability and Availability: To ensure that data remains accessible even if one or more brokers in the cluster suffer from hardware failure or downtime.
- C To compress the log files on disk by identifying duplicate records across nodes.
- D To automatically convert the data from JSON to a more efficient binary format.
Answer: B. Durability and Availability: To ensure that data remains accessible even if one or more brokers in the cluster suffer from hardware failure or downtime.
Replication Factor 3 means there are 3 copies of every message. One broker is the 'Leader' (handles all reads/writes), while the other two are 'Followers' (copy the leader). If the Leader dies, one Follower is promoted to Leader instantly.
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?