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

Correct Matches

path.format→Only valid for some Source Connectors

value.converter→Valid for all Source Connectors

input.path→Only valid for some Source Connectors

errors.retry.timeout→Valid for all Source Connectors

tasks.max→Valid for all Source Connectors

path.formatThis is a connector-specific configuration, commonly used by file-based or storage-based source connectors (for example, HDFS, S3, or FilePulse connectors). It isnot part of the Kafka Connect framework itself, so it is only valid for some source connectors.

value.converterThis is aworker-level configurationthat defines how record values are converted (JSON, Avro, Protobuf, etc.). It applies toall connectorsrunning on the worker unless overridden at the connector level.

input.pathThis configuration is specific to file-based source connectors (e.g., FileStreamSourceConnector). It isnot universally supported, so it is only valid for some source connectors.

errors.retry.timeoutThis is part of Kafka Connect’serror handling framework, introduced to support retries and tolerance of transient errors. It is ageneric Connect configurationand valid for all connectors.

tasks.maxThis is amandatory, generic connector configurationthat controls the maximum number of tasks a connector may create. It is valid forall source (and sink) connectors.

As documented in the official Apache Kafka Connect framework documentation, Kafka Connect workers form a logical cluster by using a Kafka consumer group. The configuration property that identifies this cluster is group.id.

All Kafka Connect workers configured with the same group.id automatically join the same Connect cluster. Kafka’s group coordination protocol is then used to distribute connector and task configurations among the workers, providing fault tolerance, scalability, and automatic rebalancing.

Option A (cluster.id) is a Kafka internal identifier used by brokers and is not configurable for Kafka Connect workers. Option B (worker.id) does not exist as a valid Kafka Connect configuration. Option D (connector.id) identifies individual connectors within a Connect cluster, not the worker cluster itself.

Therefore, the group.id property is the correct and officially documented configuration that determines which Kafka Connect cluster a worker belongs to.

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.