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.

With acks=all and min.insync.replicas=2, Kafka requires at least two in-sync replicas to acknowledge a write. If only one broker is alive, the condition fails, and NotEnoughReplicasException is thrown by the producer.

From Kafka Producer Exception Docs:

“NotEnoughReplicasException is thrown when the number of in-sync replicas is insufficient to satisfy acks=all with min.insync.replicas.”

NetworkException is generic and not raised here.

NotCoordinatorException is related to consumer group coordination.

NotLeaderForPartitionException is unrelated unless accessing an unassigned leader.

The official Apache Kafka Connect documentation explains that connectors run within the same worker JVM, and all logs are written through the worker’s logging framework (Log4j or Log4j2). To isolate logs for a specific connector, Kafka Connect supports connector-specific logging contexts, which can be routed to separate log files using logging configuration.

By modifying the log4j.properties (or log4j2.xml) file to define a dedicated logger and appender for the connector’s package or class name, you can direct logs from that connector to a separate file. This is the recommended and documented approach for debugging individual connectors in a shared Connect cluster.

Option A is incorrect because there is no generic “enable connector context” switch. Option B may increase verbosity but does not isolate logs per connector. Option D is false; Kafka Connect explicitly supports connector-level log separation through logging configuration.

Therefore, the correct approach is to configure a dedicated log appender for the specific connector.