This guide targets the current Confluent Certified Developer for Apache Kafka (CCDAK) exam. As of April 13, 2026, Confluent’s live certification page still described CCDAK as the certification for developers and solution architects who build applications with Apache Kafka, validating the knowledge needed to develop, deploy, and maintain robust, real-time streaming applications using Kafka’s core APIs and platform capabilities. The same public certification page also still said Confluent certification exams are 90 minute proctored exams, that question types vary across multiple-choice, matching, and list order, that all exams are in English, and that certifications expire after two years.
Offset: Kafka position marker for a record within a partition, used by consumers to track where they are in the log.
Consumer group: Coordinated set of consumers that share work across partitions while maintaining position state.
Current exam snapshot
Item
Current Confluent signal
Official exam name
Confluent Certified Developer for Apache Kafka
Exam code
CCDAK
Public role framing
developers and solution architects building Kafka applications
Current exam style signal
90 minute proctored exam
Question types
multiple-choice, matching, list order
Language
English
Certification validity
2 years
Guide model
5 chapters -> 10 section lessons
What CCDAK is really testing
CCDAK is not a generic event-streaming exam and it is not a Kafka cluster-admin exam. Confluent is testing whether you can build Kafka clients and streaming applications that keep ordering, offsets, duplicates, replay, and schema evolution under control. Strong candidates consistently do four things:
separate producer guarantees from consumer coordination
protect correctness before optimizing throughput
understand that ordering is a partition question, not a topic-wide promise
distinguish settings that change delivery semantics from settings that mostly tune performance
Confluent’s public certification page does not publish a weighted domain table for CCDAK, so this guide organizes the live developer role scope into five practical chapters that match what Confluent publicly says the exam covers: Kafka core APIs, application behavior, and platform-capability awareness.
The exam habit that usually wins
Read CCDAK stems in this order:
decide whether the issue is really about partitioning, producer semantics, consumer coordination, transaction/schema behavior, or platform boundary
identify the failing correctness boundary before you tune anything: ordering, duplicate risk, offset progress, or compatibility safety
preserve semantics first, then improve throughput or convenience
prefer the answer that keeps the cleanest partition model, offset story, and consumer compatibility
How to use this guide well
flowchart LR
S["Study Plan"] --> D["5 developer chapters"]
D --> L["10 scenario-first lessons"]
L --> C["Cheat Sheet and Glossary"]
C --> M["Mixed client-behavior review"]
M --> R["Resources and final fact check"]