You manage a cluster with a large number of topics, and each topic has many partitions. You need to significantly increase the number of partitions for some topics. What should you check before…

The correct answer is C. Ensure each broker does not exceed 4,000 partitions. Kafka performance and broker stability degrade when a broker manages too many partitions. Before increasing topic partitions, you must verify that adding more partitions will not push any broker beyond a safe operational limit. Keeping partitions per broker below approximately…

Managing Topics, Partitions, and Replicas

Question

You manage a cluster with a large number of topics, and each topic has many partitions. You need to significantly increase the number of partitions for some topics. What should you check before increasing the partitions?

Options

AEnsure compression.type is set to 'none' at the cluster level.
BEnsure all producers are set with 'acks=0' and 'compression.type=none'.
CEnsure each broker does not exceed 4,000 partitions.
DEnsure all producers are set with 'acks=all' and 'compression.type=none'.

How the community answered

(38 responses)

A
3% (1)
B
3% (1)
C
84% (32)
D
11% (4)

Explanation

Kafka performance and broker stability degrade when a broker manages too many partitions. Before increasing topic partitions, you must verify that adding more partitions will not push any broker beyond a safe operational limit. Keeping partitions per broker below approximately 4,000 helps maintain reliable performance and avoids excessive memory and CPU pressure.

Topics

#partition limits#broker capacity#4000 partitions#topic scaling

Community Discussion

No community discussion yet for this question.

Full CCAAK Practice