CCDAK Exam Dumps : Confluent Certified Developer for Apache Kafka Certification Examination

Kafka Streams usestransactional producersto guaranteeexactly-once semantics (EOS). This ensures that both theoutput recordsandstate store updatesare committed atomically, avoiding duplication or partial writes.

FromKafka Streams Documentation > Processing Guarantees:

“Kafka Streams leveragesKafka’s transactional APIsto commit the output records and internal state updatesas a single atomic unit, thereby providing exactly-once semantics.”

Option A is incorrect because log compaction is not disabled for EOS.

Option C incorrectly describes a checkpointing system Kafka Streams does not use.

Option D refers to deduplication, which is not how EOS is achieved in Streams.

RetriableException is a subclass of KafkaException, indicating transient issues thatmight succeed if retried. Examples include:

LeaderNotAvailableException: Happens when metadata is not yet propagated or leader election is in progress.

NotEnoughReplicasException: Happens when the number of in-sync replicas is insufficient. This can be transient if replicas come back online.

From theApache Kafka Java Client documentation:

"These exceptions (like LeaderNotAvailableException, NotEnoughReplicasException) are transient and the client will retry them automatically depending on retry configuration."

RecordTooLargeExceptionandAuthorizationExceptionarenon-retriableas they indicate client-side or permission errors.

The default maximum message size that a Kafka broker accepts is1MB (1,048,576 bytes), controlled by the config propertymessage.max.bytes.

FromKafka Broker Configuration Docs:

“The default maximum message size is 1MB. To accept larger messages, configure message.max.bytes and the producer’s max.request.size.”

Producers also have a matching limit via max.request.size, and consumers via fetch.message.max.bytes.