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

When using Kafka Connect with sink connectors (like S3 Sink), each task is assigned one or more topic partitions. The total number of partitions (6) is evenly distributed across the available tasks (2). Thus, each task will handle 3 partitions.

From Kafka Connect Documentation:

“Kafka Connect divides the topic partitions among available tasks. For example, a topic with six partitions and two tasks results in each task handling three partitions.”

To skip a corrupted record and avoid failing the application, you must seek past the failed offset manually using consumer.seek(). This allows the application to resume consumption from the next offset.

From Kafka Consumer Error Handling Docs:

“On deserialization failure, you can catch RecordDeserializationException, log the error, and call seek() to the next offset to skip the bad record.”

A does not prevent re-processing the bad record.

C is invalid; there's no skip() method in the Kafka consumer API.

D results in service interruption — not ideal for resiliency.

The ConsumerRebalanceListener lets you handle partition assignments and revocations during rebalances. This is critical for managing offsets, stateful processing, or external transactions.

From Kafka Consumer Rebalance Docs:

“Implementing ConsumerRebalanceListener allows your application to take action before and after partitions are reassigned.”

A is true: It lets your app react when partitions assigned to the consumer change.

B, C, and D are unrelated to consumer rebalancing directly.