CCAAK Exam Questions & Answers
Certified Administrator for Apache Kafka • Confluent
100% money-back guarantee
Sample CCAAK Questions
Practice with real exam-style questions, each with the verified correct answer and explanation.
A topic 'recurring payments' is created on a Kafka cluster with three brokers (broker id '0', '1', '2') and nine partitions. The 'min.insync replicas' is set to three, and producer is set with 'acks' as 'all'. Kafka Broker with id '0' is down.
Which statement is correct?
With 9 partitions spread across 3 brokers, each broker typically hosts 3 leaders (assuming even distribution). When Broker 0 fails, the partitions for which it was leader will elect new leaders on brokers 1 or 2 if enough in-sync replicas (ISRs) remain. But since min.insync.replicas=3 and only 2 brokers are up, no partition can meet the minimum in-sync replica requirement, so producers with acks=all will fail to write. However, for partitions where Broker 0 is not the leader, consumers can still read committed messages. Given that only 3 partitions likely had Broker 0 as leader, six partitions remain accessible for reads, but not writes.
When using Kafka ACLs, when is the resource authorization checked?
Kafka ACLs (Access Control Lists) perform authorization checks every time a client attempts to access a resource (e.g., topic, consumer group). This ensures continuous enforcement of permissions, not just at connection time or intervals. This approach provides fine-grained security, preventing unauthorized actions at any time during a session.
The Consumer property 'auto offset reset' determines what to do if there is no valid offset for a Consumer Group.
Which scenario is an example of a valid offset and therefore the 'auto.offset.reset' does NOT apply?
In this scenario, the offset itself is still valid, even though the record at that offset was compacted away. The consumer can continue consuming from the next available record. Therefore, auto.offset.reset does NOT apply, because there is a valid offset present.
A Kafka cluster with three brokers has a topic with 10 partitions and a replication factor set to three. Each partition stores 25 GB data per day and data retention is set to 24 hours.
How much storage will be consumed by the topic on each broker?
10 partitions 25 GB/day = 250 GB total per day for the topic (primary data).
With a replication factor of 3, there are 3 full copies of the data: 250 GB 3 = 750 GB total across the entire cluster.
The cluster has 3 brokers, and Kafka tries to distribute replicas evenly among them: 750 GB 3 brokers = 250 GB per broker on average.
However, due to replication, some partitions have leaders and followers, so there's some overlap and not-perfect distribution. Each broker stores approximately 2/3 of the total topic data (since each broker holds replicas for around 2/3 of the partitions).
2/3 750 GB = 500 GB, but this is shared, so each broker ends up storing ~300 GB of replicated data, including its share of leaders and followers.
Why does Kafka use ZooKeeper? (Choose two.)
ZooKeeper stores metadata such as partition leadership and ISR (in-sync replicas), which brokers use to coordinate.
Kafka uses ZooKeeper to perform leader election for the Controller broker, which manages cluster metadata and leadership changes.
Get access to all 54 verified questions with detailed answers.
Unlock All CCAAK Questions