Kafka Performance Tuning Playbook — Concept Check
Questions on Kafka Performance Tuning Playbook. Kafka throughput and latency are tunable via producer batching, compression, consumer fetch settings, and broker I/O configuration. Understanding the trade-offs lets you hit SLA targets.
Questions in this quiz
8 questions on Kafka Performance Tuning Playbook — Concept Check. Work through them here, then start the quiz to answer them and see your score.
1.A Kafka producer is configured with linger.ms=50 and batch.size=65536. What is the expected impact on throughput and latency?
- AHigher throughput, lower latency
- BLower throughput, lower latency
- CHigher throughput, higher latency
- DLower throughput, higher latency
2.You notice that a Kafka consumer is processing messages slower than expected. It is configured with fetch.min.bytes=1 and max.poll.records=500. What is a likely cause?
- AThe consumer is fetching too few bytes per request
- BThe consumer's max.poll.records is too high
- CThe consumer is fetching too many bytes per request
- DThe consumer's max.poll.records is too low
3.A Kafka producer uses compression.type=none and linger.ms=0. What is the main advantage of this configuration?
- AReduced network usage
- BImproved data compression
- CMaximized throughput
- DMinimized latency
4.A Kafka broker is experiencing high I/O wait times. Which configuration change might help alleviate this issue?
- ADecrease fetch.min.bytes
- BIncrease num.io.threads
- CIncrease fetch.min.bytes
- DDecrease num.io.threads
5.A Kafka producer's throughput is lower than expected. It is configured with compression.type=lz4 and batch.size=16384. What change could improve throughput?
- AIncrease batch.size
- BUse compression.type=none
- CDecrease batch.size
- DSet linger.ms to 0
6.Which configuration is likely to result in the lowest latency for a Kafka producer?
- Alinger.ms=0, compression.type=none
- Blinger.ms=50, compression.type=gzip
- Clinger.ms=20, compression.type=lz4
- Dlinger.ms=10, compression.type=snappy
7.A Kafka consumer is configured with fetch.min.bytes=65536 and fetch.max.wait.ms=500. What happens if the broker cannot provide 64KB of data within 500ms?
- AThe consumer fetches whatever is available after 500ms
- BThe consumer fetches immediately after 500ms
- CThe consumer fetches only if 64KB is available
- DThe consumer waits until 64KB is available
8.If a Kafka producer has max.in.flight.requests.per.connection set to 1, what is a potential downside?
- AHigher latency
- BReduced throughput
- CIncreased risk of message duplication
- DIncreased CPU usage