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.

Kafka Connect can run in standalone mode or distributed mode. For simple tasks like reading logs from a file on a single host, standalone mode is recommended.

From Kafka Connect User Guide:

“Standalone mode is useful when running connectors on a single machine (e.g., for development or simple deployments like log collection from a local file).”

Distributed mode is preferred for scalability and fault tolerance but overkill for this use case.

According to the official Apache Kafka producer metrics documentation, the I/O thread ratio and I/O thread wait ratio indicate how busy the producer’s network I/O thread is and how much time it spends waiting. When both metrics are low, it means the I/O thread is underutilized and not blocked on network operations.

This strongly suggests that the bottleneck is not network-related. If there were network latency or a bad data link (Option B), the I/O thread wait ratio would be high. Similarly, large batches (Option A) or compression (Option D) generally increase throughput and would result in higher I/O utilization.

An expensive or blocking callback function (for example, heavy logic in onCompletion()) executes in the producer’s sender thread context. Kafka documentation explicitly warns that slow callbacks can throttle producer throughput because they delay the processing of acknowledgements and subsequent sends.

Therefore, the most likely and documented cause of low producer throughput with low I/O utilization is expensive callback logic in the producer code.

=========================