If a consumer hasn't read new data for 7 days, which broker setting controls the retention of its offset?

If a consumer hasn't read new data for 7 days, which broker setting controls the retention of its offset?

• A. offset.retention.minutes
• B. log.retention.hours
• C. segment.bytes
• D. message.max.bytes

Answer: (A)

Offsets retention for inactive consumer groups is what this tests. Kafka stores each consumer group's committed offsets in the broker and keeps them for a configurable period. The setting that controls how long those offsets are retained is the offsets retention window, defined in minutes. If a consumer hasn’t read new data for seven days, and the retention window is shorter than that, the broker will drop that group's offsets. When the consumer comes back, it may start from the reset point defined by auto.offset.reset, since no committed offset exists anymore. The option you chose reflects offset retention in minutes. The other settings control topic log retention (log.retention.hours) or segment size and maximum message size (segment.bytes, message.max.bytes), which do not manage offsets.

Offsets retention for inactive consumer groups is what this tests. Kafka stores each consumer group's committed offsets in the broker and keeps them for a configurable period. The setting that controls how long those offsets are retained is the offsets retention window, defined in minutes. If a consumer hasn’t read new data for seven days, and the retention window is shorter than that, the broker will drop that group's offsets. When the consumer comes back, it may start from the reset point defined by auto.offset.reset, since no committed offset exists anymore. The option you chose reflects offset retention in minutes. The other settings control topic log retention (log.retention.hours) or segment size and maximum message size (segment.bytes, message.max.bytes), which do not manage offsets.