Question 130
A payment API retries a transaction after deadlock but creates duplicate messages in the downstream queue. The team is considering this step: Implement transactional outbox or idempotent message publishing with bounded retry. What evidence should they review before proceeding?
Explanation
Correct Answer
Compare transaction ID, outbox event table, retry count and queue messages. Database rollback and downstream effects require end-to-end idempotency strategy. Repeated deadlocks yield one committed payment and one downstream event.
Incorrect Answers
Use a transactional outbox and idempotent consumers to reconcile DB commit with downstream delivery.
Bound retries with idempotency keys and dedupe on producer/consumer boundaries.
Retries require bounds and idempotency; persistent contention must be remediated. The pertinent evidence includes: Compare transaction ID, outbox event table, retry count and queue messages.