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

The offset in the RecordMetadata object returned by the producer represents the position of the record in the partition — i.e., the sequential ID assigned by Kafka once the message is committed.

From Kafka Producer API Documentation:

“The offset is the position of the record in the partition. This is a unique, sequential number assigned by the broker.”

D refers to metadata.partition(), not offset().

B and C are unrelated to how Kafka handles committed offsets.

In Kafka Streams, the number of stream tasks = number of input partitions × num.stream.threads × number of instances, but only as many as the number of partitions can actively consume at once.

However, in this case, Kafka Streams assigns one task per partition, and because there are 5 partitions and 15 threads (3 instances × 5 threads), 15 tasks are created, and all 15 can be active depending on processing topology.

From Kafka Streams Developer Guide:

"Kafka Streams creates one task per input partition. If you increase the number of stream threads, it runs multiple tasks in parallel within a single instance."

So, 15 stream tasks will be created and 15 will be actively consuming.

To send failed records to a dead letter queue (DLQ), you must configure:

errors.tolerance=all: Tells the connector to not fail on errors but handle them (e.g., send to DLQ).

errors.deadletterqueue.topic.name=DLQ-Topic: Specifies the DLQ topic.

errors.deadletterqueue.context.headers.enable=true: Includes error context in message headers.

From Kafka Connect Error Handling Docs:

“Kafka Connect supports directing problematic records to a separate topic (DLQ) using errors.* configs. Headers can include failure metadata.”

Options D, E, F are related to logging, not DLQ behavior.