Understanding Apache Kafka’s internals and high availability mechanisms is critical for designing a robust, fault-tolerant, and scalable messaging system. Kafka uses concepts like leader-follower replication, ISR (in-sync replicas), Kafka Controller, log segments, high watermark, and more to ensure durability and availability even in case of broker failures.
These MCQs help reinforce the core architecture and internal mechanics that power Kafka’s reliability. This topic is essential for interview preparation and production-grade Kafka deployment knowledge.
1.) What does ISR stand for in Kafka?
2.) What is the role of a leader replica in Kafka?
3.) What component coordinates broker-level activities such as partition leadership?
4.) What is the high watermark in Kafka?
5.) What happens if a follower replica falls behind the ISR threshold?
6.) Which Kafka component maintains the ISR list?
7.) What is the function of the Kafka Controller?
8.) What happens if the Kafka Controller broker fails?
9.) What happens when min.insync.replicas is not met during produce?
10.) What does Kafka use to ensure message durability?