**Zookeeper (pre-KRaft)**: (1) Broker registration and metadata. (2) Leader election for partitions. (3) Consumer group coordination (offsets, rebalance). (4) Topic config. **KRaft (Kafka 3.x)**: Kafka Raft; replaces Zookeeper. Metadata in Kafka itself. Simpler ops. **Why It...
This medium-level Spark/Big Data question appears frequently in data engineering interviews at companies like Fragma Data Systems. While less common, it tests deeper understanding that distinguishes strong candidates. Mastering the underlying concepts (partition) will help you answer variations of this question confidently.
Break this problem into components. Identify the core trade-offs involved, then walk the interviewer through your reasoning step by step. Demonstrate awareness of edge cases and production considerations - this is what separates good answers from great ones.
Zookeeper (pre-KRaft): (1) Broker registration and metadata. (2) Leader election for partitions. (3) Consumer group coordination (offsets, rebalance). (4) Topic config.
KRaft (Kafka 3.x): Kafka Raft; replaces Zookeeper. Metadata in Kafka itself. Simpler ops.
Why It Mattered: Zookeeper was single point of coordination. Ensemble of 3, 5, or 7 for HA.
Scalability Trade-offs: Zookeeper session timeouts cause rebalance. KRaft eliminates Zookeeper dependency.
Cost Implications: Zookeeper = extra cluster. KRaft = fewer components.
Want feedback on your answer?
Paste your answer to this question and our AI Coach scores it, finds gaps, and shows you the FAANG-level version.
Get the most asked SQL questions with expert answers. Instant download.
No spam. Unsubscribe anytime.
Paste your answer and get instant AI feedback with a FAANG-level improved version.
Analyze My Answer β FreeAccording to DataEngPrep.tech, this is one of the most frequently asked Spark/Big Data interview questions, reported at 1 company. DataEngPrep.tech maintains a curated database of 1,863+ real data engineering interview questions across 7 categories, verified by industry professionals.