Confluent Updated CCDAK Exam Questions and Answers by odin

Kafka Connectsink connectorsuse thestandard Kafka consumer mechanismto track offsets, which means offsets are stored in the__consumer_offsets internal topic.

FromKafka Connect Documentation:

“Sink connectors are regular Kafka consumers and store their offsets in the __consumer_offsets topic like any other consumer.”

The other options refer tosource connectorsor worker configuration.

offsets.storage.topic is relevant forsource connectors.

With acks=all, the leader waits formin.insync.replicasto acknowledge the message. Since min.insync.replicas=3, Kafka will only commit the messageonce 3 brokers (leader + 2 followers)confirm they have the message.

FromKafka Documentation > Acks and Durability:

“If acks=all is specified, the producer will wait until the full set of in-sync replicas has acknowledged the record. The minimum number of in-sync replicas is controlled by min.insync.replicas.”

Even though the replication factor is 4, only3 acknowledgments are needed, as defined by min.insync.replicas.

The official CLI utility for consuming messages from Kafka topics is kafka-console-consumer.sh. It connects to the broker, consumes messages, and prints them to standard output.

FromKafka CLI Tools Documentation:

"kafka-console-consumer.sh is used to read data from a Kafka topic and write it to standard output."

The other options are not valid Kafka CLI tools.

To reset offsets for anexisting consumer group, you must use thekafka-consumer-groups.shtool with the --reset-offsets and --to-earliest flags.

FromKafka Consumer Group Tool Documentation:

“You can use the kafka-consumer-groups tool to reset offsets for a consumer group. This is required if the consumer has already committed offsets.”

Setting auto.offset.reset=earliest only worksif no committed offset exists.

Starting a new consumer with the same group won’t reset offsets.

Retention settings don’t affect committed offsets.