CCDAK Mock Exams & Practice Exam Questions | Confluent Certified Developer for Apache Kafka

Tip: Begin with 15–25 question topic drills (producer, consumer groups, offsets), then shift to mixed sets. Aim for consistent ~75–80% on mixed sets before scheduling.

Suggested progression

1. Topic drills (daily): 2× 15–25 questions focused on one topic from the Syllabus .
2. Mixed sets (alternate days): 1× 25–35 questions combining 2–3 topics.
3. Timed runs (final 1–2 weeks): 2–3 mixed runs under time; review every miss and re-drill weak objectives.

What to pair with practice

• Syllabus: objective-by-topic outline → view
• Cheatsheet: configs + code patterns → open
• Study Plan: 30/60/90 day schedules → read

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.

What to read next

• Study Plan: 30/60/90 day schedules → Open
• Syllabus: objectives by topic → Open
• Cheatsheet: configs + code + quick pickers → Open
• Practice: drills and mixed sets → Start