Browse Confluent Certification Guides

Confluent CCDAK Troubleshooting Guide

Study Confluent CCDAK Troubleshooting: key concepts, common traps, and exam decision cues.

This chapter closes the loop between theory and real application behavior. CCDAK is not only about knowing what the right configuration should be. It is also about recognizing the symptom pattern that tells you what actually went wrong.

Poison message: A record that repeatedly causes processing failure or retry churn.

Platform capability: A Confluent or Kafka ecosystem tool such as Streams, Connect, or Schema Registry that changes how applications are built or debugged.

Work this chapter in order

Lesson Focus
5.1 Lag, Duplicates, Ordering & Timeouts Learn how to classify the main Kafka client symptom patterns without guessing.
5.2 Streams, Connect & Boundaries Understand when an issue belongs to Kafka core client logic and when it belongs to Streams, Connect, or surrounding platform capabilities.

Fast routing inside this chapter

If the question is really about… Go first to…
lag, duplicates, ordering, or timeout patterns 5.1 Lag, Duplicates, Ordering & Timeouts
Streams, Connect, or broader platform-capability awareness 5.2 Streams, Connect & Boundaries

What strong answers usually do

  • classify the symptom before changing settings
  • know whether the failure is producer-side, consumer-side, or contract-side
  • distinguish Kafka core behavior from surrounding platform components

Common CCDAK traps

  • tuning the producer when the real problem is consumer lag
  • calling every duplicate problem a broker problem
  • blaming Kafka core for an issue that belongs to Streams or Connect behavior

In this section

Revised on Sunday, May 10, 2026
4. Transactions, Schemas & Streams
Study Plan