42 real Kafka 4 / KRaft questions from the Big Data bank, as asked in Indian campus drives and tech interviews. Every question has a verified answer and an AI-tutor explanation on placd — free to start.
1. What is KRaft?
Junior
A.a periodic compacted image of the KRaft metadata log that lets a new controller catch up without replaying the entire log
B.the internal KRaft topic recording all cluster metadata changes as an event log that brokers replay to rebuild state
C.the set of KRaft controller nodes that run the Raft protocol to elect a leader and replicate cluster metadata
D.the Kafka Raft metadata mode that stores cluster metadata in an internal Kafka log, fully replacing ZooKeeper as of Kafka 4.0
A.the Kafka Raft metadata mode that stores cluster metadata in an internal Kafka log, fully replacing ZooKeeper as of Kafka 4.0
B.the next-generation Kafka rebalance protocol, GA in 4.0, where the broker drives incremental partition assignment via heartbeats instead of a stop-the-world rebalance
C.the set of KRaft controller nodes that run the Raft protocol to elect a leader and replicate cluster metadata
D.a periodic compacted image of the KRaft metadata log that lets a new controller catch up without replaying the entire log
A.the internal __cluster_metadata topic in KRaft where all cluster state changes are recorded as an event log
B.the active KRaft node elected by the Raft quorum that processes all metadata writes for the cluster
C.the Kafka Raft metadata mode that stores cluster metadata in an internal Kafka log, fully replacing ZooKeeper as of Kafka 4.0
D.the next-generation Kafka rebalance protocol, GA in 4.0, where the broker drives incremental partition assignment via heartbeats instead of a stop-the-world rebalance
A.Metadata log — the next-generation Kafka rebalance protocol that moves partition assignment to the broker coordinator, reducing stop-the-world rebalances
B.Metadata log — the Kafka Raft metadata mode that stores cluster metadata in an internal Kafka log, fully replacing ZooKeeper as of Kafka 4.0
C.Metadata log — the set of KRaft controller nodes that run the Raft protocol to elect a leader and replicate cluster metadata
D.Metadata log — the internal __cluster_metadata topic in KRaft where all cluster state changes are recorded as an event log
A.the next-generation Kafka rebalance protocol, GA in 4.0, where the broker drives incremental partition assignment via heartbeats instead of a stop-the-world rebalance
B.a Kafka feature that offloads older log segments to cheaper remote object storage while keeping recent data local
C.the active KRaft node elected by the Raft quorum that processes all metadata writes for the cluster
D.a Kafka 4 KIP-932 consumer model enabling queue-like cooperative consumption with per-message acknowledgment and redelivery
11. Which term means: "the next-generation Kafka rebalance protocol, GA in 4.0, where the broker drives incremental partition assignment via heartbeats instead of a stop-the-world rebalance"?
A.KIP-848 consumer protocol — the next-generation Kafka rebalance protocol, GA in 4.0, where the broker drives incremental partition assignment via heartbeats instead of a stop-the-world rebalance
B.KIP-848 consumer protocol — a Kafka feature that offloads older log segments to cheaper remote object storage while keeping recent data local
C.KIP-848 consumer protocol — the internal __cluster_metadata topic in KRaft where all cluster state changes are recorded as an event log
D.KIP-848 consumer protocol — the set of KRaft controller nodes that elect a leader via Raft and replicate the metadata log to manage cluster state
A.the set of KRaft controller nodes that run the Raft protocol to elect a leader and replicate cluster metadata
B.a Kafka feature that offloads older log segments to cheaper remote object storage while keeping recent data local
C.the Kafka Raft metadata mode that stores cluster metadata in an internal Kafka log, fully replacing ZooKeeper as of Kafka 4.0
D.the next-generation Kafka rebalance protocol, GA in 4.0, where the broker drives incremental partition assignment via heartbeats instead of a stop-the-world rebalance
A.Tiered storage — the next-generation Kafka rebalance protocol that moves partition assignment to the broker coordinator, reducing stop-the-world rebalances
B.Tiered storage — the active KRaft node elected by the Raft quorum that processes all metadata writes for the cluster
C.Tiered storage — a Kafka feature that offloads older log segments to cheaper remote object storage while keeping recent data local
D.Tiered storage — a KRaft deployment where a node acts as both broker and controller, recommended only for development not production
A.the Kafka 4 milestone where ZooKeeper support is fully dropped and KRaft becomes the only supported metadata mode
B.the next-generation Kafka rebalance protocol that moves partition assignment to the broker coordinator, reducing stop-the-world rebalances
C.the next-generation Kafka rebalance protocol, GA in 4.0, where the broker drives incremental partition assignment via heartbeats instead of a stop-the-world rebalance
D.a KRaft deployment where a node acts as both broker and controller, recommended only for development not production
A.Combined mode — the next-generation Kafka rebalance protocol that moves partition assignment to the broker coordinator, reducing stop-the-world rebalances
B.Combined mode — the internal __cluster_metadata topic in KRaft where all cluster state changes are recorded as an event log
C.Combined mode — the Kafka Raft metadata mode that stores cluster metadata in an internal Kafka log, fully replacing ZooKeeper as of Kafka 4.0
D.Combined mode — a KRaft deployment where a node acts as both broker and controller, recommended only for development not production
A.Metadata snapshot — a periodic compacted image of the KRaft metadata log that lets a new controller catch up without replaying the entire log
B.Metadata snapshot — the internal KRaft topic recording all cluster metadata changes as an event log that brokers replay to rebuild state
C.Metadata snapshot — the Kafka Raft metadata mode that stores cluster metadata in an internal Kafka log managed by controllers, removing the ZooKeeper dependency
D.Metadata snapshot — a KRaft deployment where a node acts as both broker and controller, recommended only for development not production
A.Quorum controller — a Kafka 4 KIP-932 consumer model enabling queue-like cooperative consumption with per-message acknowledgment and redelivery
B.Quorum controller — the active KRaft node elected by the Raft quorum that processes all metadata writes for the cluster
C.Quorum controller — the Kafka Raft metadata mode that stores cluster metadata in an internal Kafka log managed by controllers, removing the ZooKeeper dependency
D.Quorum controller — a Kafka feature that offloads older log segments to cheaper remote object storage while keeping recent data local
29. Which term means: "the Kafka Raft metadata mode that stores cluster metadata in an internal Kafka log managed by controllers, removing the ZooKeeper dependency"?
Showing 30 of 42 Kafka 4 / KRaft questions — the full set, with answers, explanations and an AI tutor on every question, is inside.
Free to start
Answers, AI explanations, and a scored voice mock interview
Sign up free to check your answers with explanations, ask the AI tutor anything on any question, and take one full AI mock interview — scored like a real panel.