Kafka Performance Tuning — Concept Check
Questions on Kafka Performance Tuning. Throughput levers: batch.size, linger.ms, compression, partition count; latency levers: acks, buffer.memory, fetch.min.bytes; monitor under-replicated partitions and GC pauses.
Questions in this quiz
8 questions on Kafka Performance Tuning — Concept Check. Work through them here, then start the quiz to answer them and see your score.
1.A Kafka producer is configured with a linger.ms of 0 and a small batch.size. What is the likely impact on performance?
- ALow latency, high throughput
- BHigh latency, low throughput
- CHigh latency, high throughput
- DLow latency, low throughput
2.Your Kafka consumer experiences high latency. Which configuration change could reduce this?
- AIncrease fetch.max.wait.ms
- BIncrease max.poll.records
- CDecrease session.timeout.ms
- DDecrease fetch.min.bytes
3.A Kafka topic has a peak throughput of 200 MB/s. If a single partition supports 50 MB/s, how many partitions should you configure?
- A8
- B6
- C2
- D4
4.After enabling compression on your Kafka producer, you notice reduced network usage but increased CPU load. What compression type might you be using?
- Alz4
- Bnone
- Cgzip
- Dsnappy
5.A Kafka service shows under_replicated_partitions > 0 in production. What does this indicate?
- ANetwork throughput is saturated
- BAll partitions are healthy
- CConsumer lag is too high
- DSome partitions are missing replicas
6.You want to maximize throughput for a Kafka producer. Which configuration should you choose?
- Abatch.size=64 KB, linger.ms=20
- Bbatch.size=16 KB, linger.ms=0
- Cbatch.size=64 KB, linger.ms=0
- Dbatch.size=16 KB, linger.ms=20
7.What is the effect of setting acks=0 in Kafka producer configuration?
- ANo effect on throughput or durability
- BIncreased throughput, reduced durability
- CReduced throughput, increased durability
- DIncreased durability, reduced throughput
8.A Kafka consumer is configured with fetch.min.bytes=1 and fetch.max.wait=0. What is the expected behavior?
- AImmediate data return, low throughput
- BImmediate data return, high throughput
- CDelayed data return, high throughput
- DDelayed data return, low throughput