Confluent CCDAK Kafka Fundamentals Guide

This chapter is the foundation for the whole exam. If you do not understand how topics, partitions, keys, offsets, and consumer groups interact, producer and consumer configuration questions start to look like memorization when they are really behavior questions.

Partition: A log shard that defines the real ordering boundary in Kafka.

Key: Record field often used to control partition choice and per-entity ordering.

Public role alignment

Confluent’s current public CCDAK description says developers use Kafka’s core APIs and platform capabilities to build and maintain real-time streaming applications. This chapter covers the basics those applications depend on.

Work this chapter in order

Fast routing inside this chapter

What strong answers usually do

• remember that ordering is per partition, not per topic
• separate work-sharing behavior from durability behavior
• reason from partition count before assuming more consumers will help

Common CCDAK traps

• treating the topic like one global queue
• forgetting that idle consumers often mean too few partitions
• confusing replication with parallelism

In this section

• Confluent CCDAK Topics and Partitions Guide
  Study Confluent CCDAK Topics and Partitions: key concepts, common traps, and exam decision cues.
• Confluent CCDAK Keys and Ordering Guide
  Study Confluent CCDAK Keys and Ordering: key concepts, common traps, and exam decision cues.