Pass the Confluent Confluent Certified Administrator CCAAK Questions and answers with CertsForce

Upon detecting a broker failure, the Controller performs leader election among in-sync replicas and updates the new leader and ISR information in ZooKeeper. It then broadcasts this metadata update to all brokers in the cluster.

From Kafka documentation:

“The controller writes the new leader and ISR list to ZooKeeper and informs all brokers so they can update their metadata cache.”

B → Correct: New metadata written to ZooKeeper.

C → Correct: Brokers are updated via metadata propagation.

A → Incorrect: The Controller makes the decision, not ZooKeeper.

D → Incorrect: Producers and consumers learn about changes via brokers, not directly.

Page Reference:

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

Apache Kafka Documentation: Controller Behavior & ZooKeeper Interactions

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

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

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

In Kafka Connect, sink connectors consume data from Kafka topics and send it to external systems (e.g., databases, object storage, search indexes).

From Kafka documentation:

“Sink connectors receive data from Kafka topics and write it to external systems.”

A → Correct: Moves data out of Kafka.

B → Moves data into Kafka.

C → Not a connector type.

D → Not a standard connector classification.

Page Reference:

Kafka: The Definitive Guide, 1st Edition, Chapter 8, p. 241

Apache Kafka Documentation: Kafka Connect – Sink Connectors

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

Kafka uses ZooKeeper as its distributed coordination system. ZooKeeper helps manage cluster metadata and leader election.

A → Correct: Brokers retrieve leader/partition assignments from ZooKeeper.

D → Correct: ZooKeeper is used to elect the controller broker responsible for cluster-wide administrative tasks.

From Kafka documentation:

“ZooKeeper maintains metadata for Kafka, including broker registration and controller election.”

B → Incorrect: Broker scaling is not handled via ZooKeeper.

C → Incorrect: Replication across clusters is not related to ZooKeeper.

Page Reference:

Kafka: The Definitive Guide, 1st Edition, Chapter 6, p. 189–191

Apache Kafka Documentation: ZooKeeper Integration

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

Apache Kafka supports several security protocols for configuring broker listeners, which define how clients connect to brokers securely or insecurely. As per the official Apache Kafka documentation (“Security Overview” and “Broker Configuration” sections):

PLAINTEXT:“PLAINTEXT – Unauthenticated, unencrypted connections.”This is the default protocol when no security is configured.

SSL:“SSL – SSL authentication and encryption.”It provides secure communication between clients and brokers using SSL/TLS.

SASL_SSL:“SASL_SSL – SASL authentication and SSL encryption.”This combines SASL-based authentication with SSL encryption for secure and authenticated connections.

SASL_PLAINTEXTis also supported, but it was not listed in your options.

Option C (SASL)is not a valid protocol on its own—it’s a mechanism used within SASL_PLAINTEXT or SASL_SSL.

Option E (GSSAPI)is a SASL mechanism (often used with Kerberos), not a protocol.

Therefore, the correct answers are:

A. PLAINTEXT

B. SSL

D. SASL_SSL

Page Reference:

Confluent Kafka: The Definitive Guide, 1st Edition, Chapter 9 (“Kafka Security”), p. 282–283.

Apache Kafka Documentation, “Security Overview” and “Configuring Broker Listeners”.

Each Kafka partition is associated with log files and index files that are opened and maintained by the broker. Increasing the number of partitions increases the number of file descriptors (open files). Therefore, it is critical to verify that the broker's system-level max open file count (ulimit -n) is sufficiently high.

From Kafka documentation:

“Each partition uses multiple open files. When the number of partitions increases significantly, make sure to increase the max open file descriptors allowed for the Kafka process.”

C → Correct: Prevents file descriptor exhaustion.

A/B/D → Unrelated to partition count scalability.

Page Reference:

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

Apache Kafka Documentation: Production Deployment and Scaling Tips

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