Kafka quotas allow administrators to throttle producer and consumer throughput to avoid resource starvation. They are based on network and disk usage metrics, applied per client ID or user.
From Apache Kafka documentation:
“Quotas can be configured to control the rate at which data is produced or consumed to avoid one client from overwhelming the system.”
A → Correct: Prevents a single client from degrading cluster performance.
B → Incorrect: Kafka quotas are not for prioritization but fairness.
C → Incorrect: Quotas do not control connection limits.
D → Incorrect: Partition limits are managed via topic configs, not quotas.
Page Reference:
Kafka: The Definitive Guide, 1st Edition, Chapter 10, p. 306–308
Apache Kafka Documentation: Quotas
‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit