A batch job runs many threads that each call a DynamoDB write, and under load the calls return ProvisionedThroughputExceededException. The developer adds a fixed two-second delay before every retry, but throughput stays poor because all threads retry in lockstep and collide again. Which retry strategy resolves the synchronised collisions most effectively?
- AApply pure exponential backoff without jitter so the wait doubles each attempt and the gap between retries grows large enough to clear the throttle.
- BApply exponential backoff with random jitter so each thread waits a randomised, growing interval and the retries spread out instead of colliding together. Correct
- CRaise the SDK maxRetries value so the client keeps retrying the throttled write many more times until DynamoDB eventually accepts each request.
- DShorten the fixed delay to a few milliseconds so throttled threads retry sooner and finish the batch before the throttle window can reset itself.
Why A is wrong: Doubling the wait helps somewhat, but without jitter every thread still computes the same delay and retries in lockstep, so the synchronised collisions persist.
Why B is correct: Jitter randomises each thread's wait while exponential growth eases pressure, so the threads no longer retry at the same instant and the throttling collisions disperse.
Why C is wrong: More retries with the same fixed delay only adds more synchronised attempts, which deepens the contention rather than spreading the load out over time.
Why D is wrong: A shorter fixed delay makes the lockstep retries hit even faster and harder, so the table throttles more aggressively rather than clearing the backlog.