Which setting enables manual control of offset commits?

Which setting enables manual control of offset commits?

• A. enable.auto.commit=true
• B. enable.auto.commit=false
• C. auto.offset.reset
• D. retry.backoff.ms

Answer: (B)

Turning off automatic offset commits lets you control when offsets are saved. The setting enable.auto.commit determines this behavior: when it’s true, the consumer periodically commits the current offset on a timer, which may advance offsets even if you haven’t finished processing. When you set it to false, commits only happen when you explicitly call commitSync or commitAsync after your processing logic completes. This gives you the ability to ensure processing has succeeded before advancing the offset, which is crucial for reliable fault tolerance and tighter control over processing semantics. The other options don’t enable manual commits: auto.offset.reset governs where to start reading if there’s no committed offset or if the offset is out of range, and retry.backoff.ms is about retry timing for failed operations, not offset committing.

Turning off automatic offset commits lets you control when offsets are saved. The setting enable.auto.commit determines this behavior: when it’s true, the consumer periodically commits the current offset on a timer, which may advance offsets even if you haven’t finished processing. When you set it to false, commits only happen when you explicitly call commitSync or commitAsync after your processing logic completes. This gives you the ability to ensure processing has succeeded before advancing the offset, which is crucial for reliable fault tolerance and tighter control over processing semantics. The other options don’t enable manual commits: auto.offset.reset governs where to start reading if there’s no committed offset or if the offset is out of range, and retry.backoff.ms is about retry timing for failed operations, not offset committing.