Question 710
A financial stored procedure sporadically fails with deadlocks, and the client needs safe retry behavior. Initial testing shows: Retried requests never create duplicate invoices and deadlock rate decreases. Which limitation should the team still consider?
Explanation
Correct Answer
Retries cannot replace remediation of severe lock contention. Deadlock victims roll back their transaction and require bounded idempotent retry at a suitable boundary. Apply bounded retries after rollback with idempotency checks and fix locking order.
Incorrect Answers
That residual-risk statement assumes an invalid guarantee: Deadlock rollback covers DB transaction state, not all downstream effects; idempotency is needed.
This limitation misstates what the feature provides: Backoff, bounded attempts and root-cause locking changes are required for robust retry behavior.
This is not the governing limitation because Inspect XACT_STATE and rollback before a new idempotent attempt; do not mask failure. That assertion removes or misidentifies the relevant residual risk and does not follow from the feature semantics.