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

RetriableException is a subclass of KafkaException, indicating transient issues that might 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 the Apache Kafka Java Client documentation:

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

RecordTooLargeException and AuthorizationException are non-retriable as they indicate client-side or permission errors.

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.

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.