Practice Kafka operations vocabulary: consumer group lag, partition leaders, consumer rebalancing, topic retention, and broker replication configuration.
0 / 5 completed
1 / 5
An engineer says 'the consumer group lag is 50K messages'. What does consumer group lag indicate?
Consumer group lag is the difference between the latest offset written to a topic partition and the current offset of the consumer group. A lag of 50K means the consumer is 50K messages behind — it's not processing fast enough. High lag indicates the consumer needs scaling or the producer volume has spiked.
2 / 5
'The partition leader is on broker 2.' What is a partition leader in Kafka?
In Kafka, each partition has one leader broker that handles all reads and writes for that partition. Other brokers may hold replicas (followers). If the leader broker fails, Kafka elects a new leader from the in-sync replicas. Knowing which broker is the partition leader helps diagnose performance bottlenecks.
3 / 5
'We rebalanced the consumer group after adding a new instance.' What happens during a Kafka consumer group rebalance?
A consumer group rebalance reassigns which partitions are consumed by which consumer instances. When a new consumer joins (or leaves), Kafka rebalances to distribute partitions evenly. During a rebalance all consumers briefly pause — this is called 'stop the world' and can cause temporary processing delays.
4 / 5
'The topic retention is 7 days.' What does Kafka topic retention control?
Kafka topic retention is time-based (or size-based) and controls how long messages are kept on brokers. A 7-day retention means messages are available for replay or new consumers to read for 7 days. After that, they are deleted. Retention is independent of consumption — even read messages stay until retention expires.
5 / 5
'The Kafka cluster has 3 brokers with replication factor 3.' What does replication factor 3 mean?
Replication factor 3 means each partition has 3 copies distributed across 3 different brokers. With 3 brokers and replication factor 3, the cluster can tolerate up to 2 broker failures without losing data. This is a common production configuration — it balances fault tolerance with storage cost.