What the Confluent Certified Developer for Apache Kafka (CCDAK) exam covers
- Apache Kafka Application Development189 questions
- Apache Kafka Fundamentals160 questions
- Kafka Connect108 questions
- Application Observability84 questions
- Apache Kafka Streams81 questions
- Application Testing52 questions
Free CCDAK practice test questions
A sample of 10 questions with answers and explanations. A free account includes a fixed set of 20 practice questions for this exam, retryable anytime. Paid access unlocks the full 674-question bank.
-
Which determines the partition a keyed record is written to by default?
- AA hash of the key, so the same key reaches the same partitionCorrect
- BA round robin rotation across all of the available partitions
- CThe partition holding the fewest records at that moment
- DThe order in which the brokers respond to the producer
✓ Correct answer: AThat mapping is what gives per key ordering, because all records for a customer or an account land in one partition and are consumed in order. It also means adding partitions changes the mapping. When the key is null the default partitioner instead sticks to one partition and moves on once a batch fills, which keeps batches large rather than spraying records across partitions.
Why the other options are wrong- BRound robin rotation is a separate partitioner you select deliberately. The default sends a null-keyed record to a sticky partition that changes only when a batch fills.
- CThe number of records a partition holds does not influence the choice.
- DThe order brokers respond in has no bearing on partition selection.
-
Which describes the range assignment strategy?
- APartitions of each topic are divided into contiguous ranges per consumerCorrect
- BPartitions from all topics are dealt out one at a time in rotation
- CPartitions are assigned so that existing assignments are preserved where possible
- DPartitions are assigned at random on every rebalance
✓ Correct answer: ABecause it works topic by topic, a consumer subscribed to several topics with few partitions each can end up carrying the first partition of every one while others sit idle, which is its known weakness. Round robin, sticky and random assignment are the three alternatives being contrasted.
Why the other options are wrong- BDealing partitions out in rotation describes the round robin strategy.
- CPreserving existing assignments where possible is the sticky strategy.
- DAssignment is deterministic rather than random on each rebalance.
-
Which cost follows from increasing the replication factor of a topic?
- AMore disk across the cluster, since each copy is storedCorrect
- BMore partitions, since each copy needs its own partition
- CReduced consumer parallelism across the whole of the topic
- DLoss of the ordering guarantee within each partition
✓ Correct answer: AThe storage a topic occupies is multiplied by the replication factor, which is the term most often forgotten when a cluster is sized and the reason a three way replicated topic needs three times the space its daily volume suggests. Replicas are copies of the same partitions rather than new ones, and the remaining options are not costs of replication.
Why the other options are wrong- BMore partitions are not created, since each copy is a replica of the same partition.
- CConsumer parallelism is bounded by the partition count rather than replicas.
- DOrdering within a partition is unaffected by the replication factor.
-
Which explains why retention alone cannot satisfy a request to delete one person's data?
- ARetention removes records by age rather than selecting particular keysCorrect
- BRetention only applies to topics that use the compact cleanup policy
- CRetention cannot be changed once a topic has been created
- DRetention removes only the records a consumer has already read
✓ Correct answer: AWaiting for a window to pass deletes everybody's records or nobody's, which is neither targeted nor timely when a specific request has to be answered within a deadline. The other options misstate which policy retention belongs to, whether it can change, and what it considers.
Why the other options are wrong- BTime and size retention apply under the delete policy, including a combined delete,compact policy; a compact-only topic does not discard segments by age.
- CRetention can be changed after a topic has been created.
- DWhat a consumer has read is not considered when records are removed.
-
Which improves batching on a producer that sends one record at a time?
- AAllowing the producer to linger briefly before sendingCorrect
- BAllowing the producer to send without waiting for a response
- CReducing the number of partitions on the topic to one
- DDisabling compression so batches are assembled faster
✓ Correct answer: AA batch can only fill if the producer is willing to wait a moment for the next record, so the linger setting is the lever that turns a stream of single record requests into something the cluster handles efficiently. Not waiting for a response is an acknowledgement choice, and the remaining options do not help.
Why the other options are wrong- BAllowing the producer to send without waiting changes durability rather than batching.
- CReducing the topic to one partition destroys parallelism to fix batching.
- DDisabling compression does not make batches assemble any faster.
-
Which TWO problems suit a stream application rather than a connector? (Choose TWO)
- AJoining two topics together to produce an enriched outputCorrect
- BMaintaining a running aggregate per key over a windowCorrect
- CLoading rows from a relational database into a topic
- DWriting records from a topic into an object store
✓ Correct answer: A, BBoth need state and both operate entirely within Kafka, which is precisely the boundary between the two tools. Loading rows from a relational database into a topic and writing records from a topic into an object store are both integrations with an external system and belong to a connector.
Why the other options are wrong- CLoading rows from a relational database into a topic is connector work.
- DWriting records from a topic into an object store is connector work.
-
An operator shortens `retention.ms` on a live topic with `kafka-configs.sh --alter`. When are the existing segments affected?
- AAfter each broker is restarted with the new setting
- BWhen new segments roll, since closed segments keep the old setting
- CAt the next retention check, without restarting any brokerCorrect
- DOnce the topic is recreated with `kafka-topics.sh --create`
✓ Correct answer: CThe operations guide changes topic configuration in place with kafka-configs.sh --entity-type topics --alter --add-config, with no restart or recreation. The broker setting log.retention.check.interval.ms (default 5 minutes) is "The frequency in milliseconds that the log cleaner checks whether any log is eligible for deletion", so at that check every segment whose newest record is past the shortened limit is deleted.
Why the other options are wrong- ATopic configuration is changed in place with kafka-configs.sh; no restart is needed.
- BEvery segment is judged against the topic's current retention at each check.
- Dkafka-configs.sh changes the configuration without recreating the topic.
-
A small reference table has rows deleted from time to time, and the downstream system can safely handle duplicates. Which JDBC source connector mode does the documentation suggest for periodically copying the whole table?
- A`mode=timestamp`
- B`mode=incrementing`
- C`mode=timestamp+incrementing`
- D`mode=bulk`Correct
✓ Correct answer: DThe JDBC Source documentation describes bulk as "unfiltered and therefore not incremental at all. It will load all rows from a table on each iteration. This can be useful if you want to periodically dump an entire table where entries are eventually deleted and the downstream system can safely handle duplicates." The incremental modes track columns so that they query only new or modified rows.
Why the other options are wrong- ATimestamp mode queries only rows modified since the last poll, so it does not periodically copy the whole table.
- BIncrementing mode "can only detect new rows".
- CThis incremental mode detects new and updated rows; it does not reload the table on each poll.
-
How does Kafka Streams compute the `record-lateness-avg` task metric?
- AWall-clock time minus the record's timestamp
- BBroker append time minus the producer's create time
- CTime the record waited in the task's input buffer
- DStream time minus the record's timestampCorrect
✓ Correct answer: DThe Streams Task Metrics table defines record-lateness-avg as 'The average observed lateness in ms of records (stream time - record timestamp)', with record-lateness-max for the largest value; both are recorded at debug level. The record-e2e-latency metrics instead compare 'the record timestamp with the system time when it has been fully processed by the node'.
Why the other options are wrong- AComparing the record timestamp with system time is how the record-e2e-latency metrics work.
- BStreams does not compare broker and producer timestamps for this metric.
- CBuffered records are counted by active-buffer-count, not timed by this metric.
-
A consumer processes each batch and then calls `commitSync()`. A test kills the process after it has processed a batch but before the commit, then restarts it with the same `group.id`. Earlier batches were committed normally. What should the test observe?
- AThe batch is delivered again, so it is processed twiceCorrect
- BThe batch is skipped, because it was already fetched once
- CRedelivery depends on `auto.offset.reset=earliest` being set
- DThe broker drops the repeat, so the batch is processed once
✓ Correct answer: AKafka's design documentation describes this order: the consumer can 'read the messages, process the messages, and finally save its position', and if it 'crashes after processing messages but before saving its position', the new process receives messages that 'will already have been processed. This corresponds to the at-least-once semantics in the case of consumer failure.' The restarted consumer resumes from the last committed offset; auto.offset.reset applies only when there is no initial offset.
Why the other options are wrong- BFetching does not move the committed position; the restart resumes from the last commit.
- Cauto.offset.reset applies only when no committed offset exists, and earlier batches were committed.
- DProducer idempotence prevents duplicate writes; it does not stop a consumer re-reading from its committed offset.
Who this Confluent Certified Developer for Apache Kafka (CCDAK) practice exam is for
This practice set is for anyone preparing for the Confluent Certified Developer for Apache Kafka (CCDAK) exam at the intermediate level - from first-time candidates building a foundation to experienced Data practitioners doing a final review before test day. If you learn best by working through realistic questions and reading why each answer is right or wrong, it is built for you.
How to use this Confluent Certified Developer for Apache Kafka (CCDAK) practice exam
- Start with the free sample questions above to gauge your current baseline.
- Read the full explanation on every question, including why each wrong option is wrong.
- Track your weak domains and focus your study where you are losing the most marks.
- Once you are scoring consistently well, take a timed, full-length mock exam.
- Use your readiness score to decide when you are ready to book the real Confluent Certified Developer for Apache Kafka (CCDAK) exam.
Related Data resources
- Confluent Certified Developer for Apache Kafka (CCDAK) study guideKey concepts
- Data practice examsAll Data
- Certification pathWhere this fits
- Certification exam guides & tipsBlog
- Plans & pricingFree & paid
- How these questions are written and reviewedMethodology
- Report a problem with a questionCorrections
- Databricks Certified Data Analyst Associate practice examRelated
- Databricks Certified Data Engineer Associate practice examRelated
- Databricks Certified Data Engineer Professional practice examRelated
Confluent Certified Developer for Apache Kafka (CCDAK) practice exam FAQ
How many questions are in the Confluent Certified Developer for Apache Kafka (CCDAK) practice exam on CertGrid?
CertGrid has 674 practice questions for Confluent Certified Developer for Apache Kafka (CCDAK), covering 6 exam domains. The real Confluent Certified Developer for Apache Kafka (CCDAK) exam is 60 qs in 90 min. CertGrid's timed mock is a fixed 60 questions.
What is the passing score for Confluent Certified Developer for Apache Kafka (CCDAK)?
The Confluent Certified Developer for Apache Kafka (CCDAK) exam passing score is Pass/Fail, and you have about 90 min to complete it. CertGrid tracks your readiness against the exam objectives so you know where to focus.
Are these official Confluent Certified Developer for Apache Kafka (CCDAK) exam questions?
No. CertGrid is an independent practice platform. We do not provide real or leaked exam questions. Our questions are original and designed to help you practice the concepts, scenarios, and difficulty style of the Confluent Certified Developer for Apache Kafka (CCDAK) exam.
Is there a free CCDAK practice test?
Yes. You can take a free Confluent Certified Developer for Apache Kafka (CCDAK) practice test straight away: a fixed set of 20 practice questions for this exam, retryable as often as you like, with no credit card required. You get readiness scoring and a weak-domain breakdown on those questions. Paid plans unlock the full 674-question bank, timed mock exams and full-bank domain analytics.
What CertGrid is (and is not)
CertGrid is an independent IT certification practice platform for Azure, AWS, Google, Cisco, Security, Linux, Kubernetes, Terraform, and other certification tracks. It provides objective-mapped practice questions, readiness scoring, weak-domain drills, and explanations to help learners understand what to study next.
Independent & original. CertGrid is not affiliated with or endorsed by Microsoft, AWS, Google, Cisco, CompTIA, the Linux Foundation, HashiCorp, or other certification vendors. Questions are original practice items designed to mirror certification concepts and exam style. CertGrid does not provide official exam questions or braindumps.