You send a BatchWriteItem request to DynamoDB with 5 items. The response contains 2 unprocessed items. What does this mean?
Unprocessed items are those DynamoDB could not write due to capacity limits.
When BatchWriteItem returns unprocessed items, it means those items were not saved and should be retried.
Which of the following is the main reason DynamoDB returns unprocessed items in a BatchWriteItem response?
Think about capacity and limits on writes per second.
DynamoDB returns unprocessed items when the write capacity is exceeded, so it cannot process all items immediately.
Given a BatchWriteItem response with unprocessed items, which code snippet correctly retries them until all are processed?
Retry while unprocessed items exist.
Option D loops while unprocessed items exist, retrying the batch write with those items.
Which approach best optimizes handling unprocessed items returned by BatchWriteItem to avoid throttling?
Think about how to reduce load and avoid repeated throttling.
Exponential backoff with jitter helps spread retries over time, reducing throttling and improving success.
Consider this Python code snippet retrying unprocessed items from BatchWriteItem:
while response['UnprocessedItems']:
response = client.batch_write_item(RequestItems=response['UnprocessedItems'])Why might this cause an infinite loop?
while response['UnprocessedItems']: response = client.batch_write_item(RequestItems=response['UnprocessedItems'])
Think about what happens if you retry too fast.
Retrying immediately without delay can cause repeated throttling, so unprocessed items remain and loop never ends.