Confluent Updated CCDAK Exam Questions and Answers by odin

The Apache Kafka documentation states that consumer offsets are stored per consumer group and must be explicitly reset if an application needs to reprocess data from an earlier position. The officially supported and safest way to reset offsets for an existing consumer group is by using the kafka-consumer-groups CLI tool with the --reset-offsets option and the --to-earliest flag.

Setting auto.offset.reset=earliest (Option D) only applies when no committed offset exists for a partition. Since this consumer is already running in production, offsets are already committed, making this option ineffective. Option C does not change offsets because Kafka identifies consumers by group ID, not application instance. Option B is extremely dangerous and incorrect, as setting retention.ms=0 deletes data for all consumers and impacts other applications.

Therefore, using the CLI to reset offsets for the specific consumer group ensures controlled, auditable, and targeted offset management without affecting other consumers or the topic itself. This approach is explicitly documented in Kafka’s consumer group administration tools.

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

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.

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.

From Kafka 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.

Kafka Connect sink connectors use the standard Kafka consumer mechanism to track offsets, which means offsets are stored in the __consumer_offsets internal topic.

From Kafka 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 to source connectors or worker configuration.

offsets.storage.topic is relevant for source connectors.