CCDAK Overview — What’s Tested, Common Traps & How to Prepare

Everything to know before CCDAK (Confluent Certified Developer for Apache Kafka): what skills are tested, the mental models that matter (partitions, offsets, semantics), and a practical prep funnel.

On this page

Exam snapshot (high level)

Certification: Confluent Certified Developer for Apache Kafka (CCDAK)
Audience: developers and solution architects building applications with Kafka
Skills level: you should be comfortable writing producers/consumers, reading configs, and reasoning about failure modes
Official details: registration, pricing, and delivery mode can change—use the official links in Resources for the most current info.

Study funnel: Follow the Study Plan → work the Syllabus objective-by-objective → use the Cheatsheet for recall → validate with Practice.

What CCDAK measures (what you should be able to do)

1) Understand Kafka’s core architecture

Topics, partitions, offsets, brokers, replication, and the “unit of ordering” model (ordering is per partition).
How consumer groups scale reads and how rebalancing affects processing.

2) Build reliable producers

Choose the right producer configuration for durability, throughput, and latency.
Handle retries safely (idempotence, ordering, duplicate risk).
Use keys and partitioners intentionally.

3) Build correct consumers

Implement a correct poll loop and reason about consumer liveness (heartbeats/poll interval).
Manage offsets (auto vs manual commits) and handle rebalance events safely.
Distinguish common semantics: at-most-once, at-least-once, and effectively exactly-once patterns.

4) Choose serialization and schema strategies

Understand serializers/deserializers and schema evolution (compatibility rules).
Know the purpose of Schema Registry and why it reduces breaking changes.

5) Apply practical security awareness

TLS basics, SASL mechanisms (high level), and the difference between authentication and authorization (ACLs).

6) Diagnose common runtime issues

Consumer lag, throughput bottlenecks, timeouts, rebalances, and common exception patterns.

Who should take CCDAK?

Backend engineers integrating services through event streams
Platform engineers supporting Kafka-based application development
Engineers moving into streaming and event-driven architecture roles

If you’re brand new to Kafka, you can still pass—but budget time to internalize partitioning + offsets + consumer groups, because those show up everywhere.

Readiness checklist

I can explain partition ordering and why keys matter.
I can choose producer configs for durability vs latency (acks, batching, retries).
I can reason about offset commits and rebalances without hand-waving.
I can explain at-least-once vs exactly-once trade-offs at the client/API level.
I can describe what Schema Registry does and why compatibility matters.

Browse Exams — Mock Exams & Practice Tests