Confluent CCAAK Exam With Confidence Using Practice Dumps

Kafka's Controller is a broker that also performs controller duties. It is not a dedicated node. Therefore, it continues to host topics, partitions, and leaders just like any other broker.

From Kafka documentation:

“The controller is one of the brokers in the cluster and continues to perform all normal broker functions.”

A → Correct: The controller is also a normal broker with partitions.

B/C/D → Incorrect: Replication and consumer fetches are not tied to the controller.

Page Reference:

Kafka: The Definitive Guide, 1st Edition, Chapter 6, p. 190

Apache Kafka Documentation: Kafka Controller Behavior

‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾

Kafka supports quotas to limit the broker resources each client can use. This is used to prevent one client from monopolizing cluster bandwidth.

From Kafka documentation:

“Quotas can be applied to both producers and consumers. These quotas are enforced based on the number of bytes per second, and they are applied to ensure fair usage of broker resources.”

A. Quotas → Correct: Admins can define quotas on throughput per client ID or user.

B. Consumer Groups → Incorrect: This controls parallelism in consumption but not resource fairness.

C. Rebalancing → Incorrect: This helps with load balancing but not with resource limitation.

D. ACLs → Incorrect: ACLs define access permissions but not resource usage.

Page Reference:

Kafka: The Definitive Guide, 1st Edition, Chapter 10 (“Administering Kafka”), p. 306–308

‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾

To support gradual migration to SSL, Kafka supports configuring multiple listeners. You can run both a PLAINTEXT listener (for legacy clients) and an SSL listener (for new clients), allowing dual access.

From Kafka documentation:

“You can configure multiple listeners on a broker with different security protocols. This allows rolling out SSL while supporting legacy connections.”

A → Incorrect: Modifying the current listener breaks current clients.

B → Misleading: Changing advertised listeners affects how clients connect, which breaks backward compatibility.

C → Correct: Dual listeners allow phased SSL migration.

D → SSL must be configured on both ends to be effective.

Page Reference:

Kafka: The Definitive Guide, 1st Edition, Chapter 10, p. 305

Apache Kafka Documentation: Configuring Multiple Listeners

‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾