Kafka Cluster Scaling — Concept Check
Questions on Kafka Cluster Scaling. Add brokers and use partition reassignment to rebalance leadership; Kafka 3.x's Cruise Control automates load balancing based on disk, CPU, and network metrics.
Questions in this quiz
8 questions on Kafka Cluster Scaling — Concept Check. Work through them here, then start the quiz to answer them and see your score.
1.A Kafka cluster has recently added a new broker. What must be done to rebalance the partition leadership?
- AKafka automatically rebalances partition leadership when a new broker is added
- BUse kafka-reassign-partitions.sh to generate and execute a reassignment plan
- CRestart the Kafka brokers to trigger automatic rebalancing
- DIncrease the partition count to distribute load evenly across brokers
2.After increasing the partition count of a Kafka topic from 12 to 24, what is a potential consequence?
- AConsumer parallelism will decrease
- BProducer throughput will be limited
- CPartitions will automatically balance across brokers
- DKey-based ordering for existing keys may break
3.A Kafka cluster's throughput is bottlenecked by consumer parallelism. What is a recommended action?
- ADecrease the partition count to consolidate data
- BUse kafka-configs.sh to throttle consumer traffic
- CIncrease the partition count of the topic
- DAdd more brokers without reassigning partitions
4.What is the role of LinkedIn's Cruise Control in a Kafka cluster?
- AAutomates load balancing based on resource utilization metrics
- BReplaces kafka-reassign-partitions.sh for manual rebalancing
- CEnsures key-based ordering is maintained during scaling
- DAutomatically increases partition count to improve throughput
5.A Kafka topic's partitions are being reassigned. What is a crucial step to avoid impacting live traffic?
- AThrottle the reassignment to limit inter-broker replication traffic
- BIncrease the partition count to distribute load
- CUse kafka-leader-election.sh to manually select leaders
- DRestart brokers to speed up the reassignment
6.A Kafka cluster uses key-based routing. What happens if partitions are increased?
- AConsumer parallelism decreases
- BProducer throughput is unaffected
- CKey ordering is maintained as partitions increase
- DKey ordering for existing keys may break
7.What does the command kafka-leader-election.sh --election-type PREFERRED achieve?
- AIncreases the partition count of a topic
- BRestores balanced leadership to the original preferred replica
- CRemoves throttling after partition reassignment
- DAutomatically rebalances partitions across new brokers
8.Why might someone mistakenly believe Kafka automatically rebalances when adding brokers?
- AConfuse partition count with broker count
- BThink increasing partitions triggers rebalancing
- CBelieve Cruise Control is always enabled
- DAssume Kafka's distributed nature handles it