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

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.

Session windows are ideal for tracking periods of activity separated by inactivity, such as user sessions.

From Kafka Streams Documentation > Windowing:

“A session window captures streams of events that are intermittent and separated by a gap of inactivity.”

Tumbling/Hopping/Sliding windows are fixed in size

Session windows are dynamic and close after inactivity timeout

This makes them perfect for identifying gaps in user interaction.

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.