ZooKeeper & KRaft Mode — Concept Check
Questions on ZooKeeper & KRaft Mode. ZooKeeper stored Kafka metadata historically; KRaft (Kafka Raft, 3.x) replaces it with an internal quorum controller, eliminating the external dependency and simplifying operations.
Questions in this quiz
8 questions on ZooKeeper & KRaft Mode — Concept Check. Work through them here, then start the quiz to answer them and see your score.
1.A Kafka cluster using ZooKeeper is experiencing slow controller failover times. What is a likely cause?
- AInsufficient disk space on brokers
- BNetwork latency between brokers
- CIncorrect broker configurations
- DZooKeeper's inability to handle large partition counts efficiently
2.In KRaft mode, what happens if the active controller node fails?
- AZooKeeper is used to elect a new controller
- BAnother controller node takes over using the Raft consensus algorithm
- CThe entire Kafka cluster shuts down until manual intervention
- DAll metadata operations halt permanently
3.While migrating from ZooKeeper to KRaft, a team leaves ZooKeeper configurations in place after migration. What is a likely outcome?
- AZooKeeper will automatically decommission
- BThe cluster will fail to start
- CThe cluster may not fully utilize KRaft benefits
- DKRaft will ignore ZooKeeper settings
4.A developer claims that KRaft mode requires ZooKeeper for storing cluster metadata. What is the correct understanding?
- AZooKeeper is essential for KRaft to function
- BKRaft stores metadata internally, eliminating the need for ZooKeeper
- CKRaft uses ZooKeeper for backup purposes
- DKRaft uses ZooKeeper only for ACLs
5.What is a key benefit of migrating from ZooKeeper to KRaft in Kafka 3.x?
- ALower memory usage on brokers
- BFaster startup and failover times
- CSimplified broker configurations
- DReduced need for network bandwidth
6.A team manages a Kafka cluster with millions of partitions using ZooKeeper. What challenge might they face?
- AZooKeeper's inefficiency in handling large numbers of partitions
- BIncreased memory usage on ZooKeeper nodes
- CNetwork congestion between brokers
- DIncreased disk usage on brokers
7.What is a necessary step before starting a Kafka broker in KRaft mode?
- ASet up a dedicated network for KRaft
- BConfigure a separate JVM for KRaft
- CFormat storage with a cluster ID
- DStart ZooKeeper first
8.A developer believes that KRaft mode still requires a separate ZooKeeper cluster for metadata. What is the correct understanding?
- AZooKeeper is optional but recommended
- BZooKeeper is used for backup in KRaft mode
- CKRaft uses ZooKeeper for leader election
- DKRaft eliminates the need for ZooKeeper by storing metadata internally