Question 1057

The Quarantine Comes Back

Ledger events are keyed by account id. Your consumer retries a failing record three times, sends it to a dead-letter queue, and moves on. An operator later replays the dead-letter queue back into the main topic. What hazard does this design introduce?

A

The replayed event loses its key during dead-letter routing, so it is assigned round-robin and can land on a partition a different consumer owns

B

The replayed event arrives after later events for the same account were already applied, so it must be version-checked or it will overwrite newer state

C

Replaying from the dead-letter queue rewinds the consumer group's committed offset on that account's partition, so every record after it is processed twice

D

Consumer lag on the original partition keeps growing, because the skipped record is still counted as unprocessed until the replay finally commits it