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

Using assign() givesmanual controlover partition assignment. In this mode:

B is true: The applicationchooses partitionsdirectly without involving the group coordinator.

C is true: Since no group coordination occurs,no rebalancinghappens if a consumer dies.

FromKafka Consumer API Docs:

“assign() manually assigns a list of partitions to this consumer. No coordination takes place and no rebalancing is triggered.”

A is false: subscribe() and assign() aremutually exclusive.

D is incorrect: Partitions don't need to be equal across topics.

Kafka Connectsource connectorsuse theoffset.storage.topicconfiguration parameter to define where to storeoffsets that track the connector's positionin the source system (e.g., database, file, etc.).

FromKafka Connect Worker Configuration:

“offset.storage.topic specifies the topic in Kafka where the connector stores offsets for each source partition.”

This allows Kafka Connect toresumefrom the correct position on restart.

The other options (B–D) are not valid Kafka configs.

unclean.leader.election.enable=false→ Prevents data loss by only considering in-sync replicas when rebalancing.

replication.factor→ Specifies how many redundant copies of partitions are distributed across brokers.

min.insync.replicas=2→ Sets the standard for the number of partition instances that must keep up with the latest committed message.

unclean.leader.election.enable=false ensures that onlyin-sync replicascan be elected as leaders. If disabled, an out-of-sync replica may become leader, potentially leading to data loss.

replication.factor defineshow many brokerswill maintain copies of each partition, directly impacting durability and availability.

min.insync.replicas determineshow many replicas must acknowledgea write when acks=all is used, enforcing write durability.