Offset management in Kafka - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to commit the current offset synchronously.

Kafka

consumer.commitSync([1]);

Drag options to blanks, or click blank then click option'

Aoffsets

Btrue

Cnull

Dfalse

Attempts:

3 left

💡 Hint

Common Mistakes

Passing true or false causes errors because commitSync expects an offset map or null.

Passing 'offsets' without defining it causes runtime errors.

Passing null to commitSync commits the latest offsets for the consumer's assigned partitions.

2fill in blank

medium

Complete the code to seek to a specific offset for a partition.

Kafka

consumer.seek(new TopicPartition('my-topic', 0), [1]);

Drag options to blanks, or click blank then click option'

A5

B-1

C'5'

DlatestOffset

Attempts:

3 left

💡 Hint

Common Mistakes

Using a string like '5' instead of number 5 causes type errors.

Using -1 is invalid for seek and causes runtime errors.

The seek method requires a numeric offset to move the consumer to that position.

3fill in blank

hard

Fix the error in committing offsets asynchronously with a callback.

Kafka

consumer.commitAsync([1], (err, data) => {
  if (err) console.error('Commit failed', err);
  else console.log('Commit succeeded', data);
});

Drag options to blanks, or click blank then click option'

Anull

Bundefined

C{}

Doffsets

Attempts:

3 left

💡 Hint

Common Mistakes

Passing undefined causes the commitAsync to fail silently.

Passing an empty object {} commits nothing and may cause unexpected behavior.

Passing null commits the latest offsets; passing undefined or empty object causes errors.

4fill in blank

hard

Fill both blanks to create a map for committing offset 10 for partition 0 of 'my-topic'.

Kafka

const offsets = new Map();
offsets.set(new [1]('my-topic', [2]), { offset: 10 });

Drag options to blanks, or click blank then click option'

ATopicPartition

BPartition

C0

D1

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Partition' instead of 'TopicPartition' causes errors.

Using partition 1 commits offset to the wrong partition.

TopicPartition is the class representing topic and partition; partition number is 0 here.

5fill in blank

hard

Fill all three blanks to commit offset 15 for partition 2 of 'orders' topic asynchronously.

Kafka

const offsets = new Map();
offsets.set(new [1]('[2]', [3]), { offset: 15 });
consumer.commitAsync(offsets, (err) => {
  if (err) console.error('Commit error', err);
  else console.log('Commit successful');
});

Drag options to blanks, or click blank then click option'

ATopicPartition

Borders

C2

D3

Attempts:

3 left

💡 Hint

Common Mistakes

Using partition 3 commits to the wrong partition.

Using wrong topic name causes commit to fail.

TopicPartition class with topic 'orders' and partition 2 is used to commit offset 15 asynchronously.

Practice

1. What is the main purpose of offset management in Kafka?

easy

A. To track which messages have been read by a consumer

B. To store the actual message data in Kafka topics

C. To manage the number of partitions in a topic

D. To control the replication factor of Kafka brokers

Solution

1. Step 1: Understand offset management role

   Offset management keeps track of the last message a consumer has read in a partition.

2. Step 2: Differentiate from other Kafka features

   Storing messages, partition count, and replication are unrelated to offset tracking.

3. Final Answer:

   To track which messages have been read by a consumer -> Option A

4. Quick Check:

   Offset management = track read messages [OK]

Hint: Offset management tracks read messages, not data storage [OK]

Common Mistakes:

• Confusing offset with message storage
• Mixing offset with partition or replication management
• Thinking offset controls message content

2. Which of the following is the correct way to manually commit offsets in Kafka consumer API?

easy

A. consumer.offsetCommit()

B. consumer.commitOffset()

C. consumer.saveOffset()

D. consumer.commitSync()

Solution

1. Step 1: Recall Kafka consumer API methods

   The official method to commit offsets manually is commitSync() or commitAsync().

2. Step 2: Identify the exact method name

   Only commitSync() matches the correct Kafka API method for synchronous commit.

3. Final Answer:

   consumer.commitSync() -> Option D

4. Quick Check:

   Manual commit method = commitSync() [OK]

Hint: Manual commit uses commitSync() or commitAsync() [OK]

Common Mistakes:

• Using incorrect method names like commitOffset()
• Confusing commitSync() with offsetCommit()
• Assuming saveOffset() exists

3. Given the following code snippet, what will be the output if the consumer seeks to offset 5 and reads one message?

consumer.assign(Collections.singleton(topicPartition));
consumer.seek(topicPartition, 5);
ConsumerRecords records = consumer.poll(Duration.ofMillis(1000));
for (ConsumerRecord record : records) {
    System.out.println(record.offset());
    break;
}

medium

A. 5

B. 0

C. 1

D. Exception thrown

Solution

1. Step 1: Understand seek behavior

   Calling seek sets the consumer's position to offset 5 in the assigned partition.

2. Step 2: Poll and print offset

   The poll fetches messages starting at offset 5; printing record.offset() outputs 5.

3. Final Answer:

   5 -> Option A

4. Quick Check:

   seek to 5 then poll = offset 5 [OK]

Hint: seek sets start offset; first polled message offset matches [OK]

Common Mistakes:

• Assuming poll starts from offset 0
• Expecting offset 1 instead of 5
• Thinking seek causes an exception

4. What is wrong with the following code snippet for committing offsets manually?

consumer.poll(Duration.ofMillis(1000));
consumer.commitAsync();
consumer.close();

medium

A. consumer.close() should be called before commitAsync()

B. commitAsync() should be called before poll()

C. commitAsync() is called without processing polled records

D. poll() duration is too short for commitAsync()

Solution

1. Step 1: Check offset commit timing

   Offsets should be committed after processing records, not just after poll().

2. Step 2: Identify missing processing step

   The code commits offsets without handling any messages, so it commits offsets that may not be processed.

3. Final Answer:

   commitAsync() is called without processing polled records -> Option C

4. Quick Check:

   Commit after processing, not just after poll [OK]

Hint: Always process records before committing offsets [OK]

Common Mistakes:

• Calling commit before processing messages
• Closing consumer before committing
• Misunderstanding poll duration effect

5. You want to restart a Kafka consumer and continue reading from the last committed offset, but also have the option to start from the beginning if no offset is found. Which approach correctly manages offsets to achieve this?

hard

A. Always call consumer.seekToEnd() before polling messages

B. Use consumer.seekToBeginning() if no committed offset exists, else start from committed offset

C. Manually set offset to 0 every time before polling

D. Disable offset commits and rely on auto.offset.reset = latest

Solution

1. Step 1: Understand offset reset behavior

   If no committed offset exists, consumer can seek to beginning to read all messages.

2. Step 2: Combine offset check and seek

   Check for committed offset; if found, start there; if not, call seekToBeginning() to start fresh.

3. Final Answer:

   Use consumer.seekToBeginning() if no committed offset exists, else start from committed offset -> Option B

4. Quick Check:

   Seek beginning if no offset, else resume from committed [OK]

Hint: Seek beginning only if no committed offset found [OK]

Common Mistakes:

• Always seeking to end loses old messages
• Resetting offset to 0 blindly every time
• Disabling commits causes loss of progress