Unprocessed items handling in DynamoDB - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to check if there are unprocessed items after a batch write.

DynamoDB

if response.get('[1]'):
    print('There are unprocessed items.')

Drag options to blanks, or click blank then click option'

AUnprocessedItems

BItems

CProcessedItems

DBatchItems

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'ProcessedItems' instead of 'UnprocessedItems'.

Checking a wrong key like 'Items' or 'BatchItems'.

The UnprocessedItems key in the response contains any items that were not processed in the batch write.

2fill in blank

medium

Complete the code to retry unprocessed items in a batch write operation.

DynamoDB

while '[1]' in response and response['[1]']:
    response = client.batch_write_item(RequestItems=response['[1]'])

Drag options to blanks, or click blank then click option'

AProcessedItems

BUnprocessedItems

CItems

DBatchItems

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'ProcessedItems' which will cause an infinite loop or no retry.

Using incorrect key names like 'Items' or 'BatchItems'.

The UnprocessedItems key contains items that need to be retried in batch write operations.

3fill in blank

hard

Fix the error in the code that attempts to handle unprocessed items after a batch write.

DynamoDB

if response['[1]']:
    retry_items = response['UnprocessedItems']

Drag options to blanks, or click blank then click option'

AProcessedItems

BItems

CUnprocessedItems

DBatchItems

Attempts:

3 left

💡 Hint

Common Mistakes

Checking 'ProcessedItems' which does not exist in the response.

Using 'Items' or 'BatchItems' keys incorrectly.

The code must check the UnprocessedItems key to find items that need retrying.

4fill in blank

hard

Fill both blanks to correctly extract and retry unprocessed items in a batch write.

DynamoDB

unprocessed = response.get('[1]', {})
if unprocessed:
    response = client.batch_write_item(RequestItems=[2])

Drag options to blanks, or click blank then click option'

AUnprocessedItems

BProcessedItems

Cunprocessed

Dresponse['UnprocessedItems']

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'ProcessedItems' instead of 'UnprocessedItems'.

Passing the wrong variable or expression to batch_write_item.

First, get the UnprocessedItems from the response. Then retry by passing the unprocessed items to batch_write_item.

5fill in blank

hard

Fill all three blanks to implement a loop that retries unprocessed items until all are processed.

DynamoDB

while response.get('[1]'):
    unprocessed = response['[2]']
    response = client.batch_write_item(RequestItems=[3])

Drag options to blanks, or click blank then click option'

AUnprocessedItems

BProcessedItems

Cunprocessed

Dresponse['UnprocessedItems']

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'ProcessedItems' which does not exist.

Passing the wrong argument to batch_write_item.

Not looping correctly to retry all unprocessed items.

The loop continues while there are UnprocessedItems. It extracts them and retries by passing the unprocessed items to batch_write_item.

Practice

1. What does DynamoDB return when some items in a batch write are not processed immediately?

easy

A. An error stopping the entire batch operation

B. A partial success with no retry information

C. A success message without details

D. A list of unprocessed items to retry later

Solution

1. Step 1: Understand batch write behavior

   DynamoDB may not process all items in a batch due to throttling or limits.

2. Step 2: Identify returned data for unprocessed items

   It returns unprocessed items so the client can retry sending them.

3. Final Answer:

   A list of unprocessed items to retry later -> Option D

4. Quick Check:

   Unprocessed items = retry list [OK]

Hint: Unprocessed items mean retry those items later [OK]

Common Mistakes:

• Thinking DynamoDB throws an error instead
• Assuming all items are processed without feedback
• Ignoring unprocessed items in code

2. Which of the following is the correct way to check for unprocessed items in a DynamoDB BatchWriteItem response in Python?

easy

A. if 'UnprocessedItems' in response and response['UnprocessedItems']:

B. if response['UnprocessedItems'] == None:

C. if response['UnprocessedItems'] is False:

D. if 'UnprocessedItems' not in response:

Solution

1. Step 1: Understand response structure

   The response includes 'UnprocessedItems' key if any items were not processed.

2. Step 2: Correctly check for unprocessed items

   Check if 'UnprocessedItems' exists and is not empty to retry those items.

3. Final Answer:

   if 'UnprocessedItems' in response and response['UnprocessedItems']: -> Option A

4. Quick Check:

   Check key exists and is not empty [OK]

Hint: Check key exists and is not empty to find unprocessed items [OK]

Common Mistakes:

• Checking for None instead of empty dict
• Using 'not in' which misses unprocessed items
• Checking for False which is incorrect

3. Given this Python snippet handling DynamoDB batch write:

response = client.batch_write_item(RequestItems=batch)
if response.get('UnprocessedItems'):
    retry_items = response['UnprocessedItems']
else:
    retry_items = None
print(retry_items)

What will be printed if all items were processed successfully?

medium

A. List of all items

B. {}

C. None

D. An error

Solution

1. Step 1: Understand response when all items processed

   If all items are processed, 'UnprocessedItems' key is empty or missing.

2. Step 2: Analyze code behavior

   response.get('UnprocessedItems') returns None or empty dict; if empty dict is falsy, else branch sets retry_items to None.

3. Final Answer:

   None -> Option C

4. Quick Check:

   No unprocessed items means retry_items = None [OK]

Hint: If no unprocessed items, retry_items is None [OK]

Common Mistakes:

• Expecting empty dict instead of None
• Assuming an error is raised
• Thinking retry_items contains all items

4. You wrote this code to resend unprocessed items but it never stops retrying:

while True:
    response = client.batch_write_item(RequestItems=items)
    items = response.get('UnprocessedItems', {})
    if not items:
        break

What is the likely bug causing infinite retries?

medium

A. Missing a delay between retries causing throttling

B. Using 'break' inside the loop incorrectly

C. Not updating 'items' with the new unprocessed items correctly

D. Not checking for empty dictionary properly

Solution

1. Step 1: Analyze the retry loop

   The code updates items correctly but retries immediately without delay.

2. Step 2: Identify the cause of infinite retries

   Missing delay or exponential backoff leads to rapid retries, causing persistent throttling. DynamoDB continually returns the same unprocessed items.

3. Final Answer:

   Missing a delay between retries causing throttling -> Option A

4. Quick Check:

   Add sleep/backoff between retries [OK]

Hint: Add delay or backoff between batch retries to avoid throttling [OK]

Common Mistakes:

• Blaming item update logic instead of throttling
• Assuming empty dict check prevents infinite loops
• Overlooking need for backoff in tight retry loops

5. You want to ensure all items in a large batch are saved in DynamoDB without loss. Which approach best handles unprocessed items efficiently?

hard

A. Split items into single writes to avoid unprocessed items

B. Check for unprocessed items after each batch write and retry them until none remain

C. Send all items once and ignore unprocessed items since they are rare

D. Use batch write once and log unprocessed items without retrying

Solution

1. Step 1: Understand batch write limitations

   DynamoDB batch writes can return unprocessed items due to throttling or limits.

2. Step 2: Best practice for data safety

   Retry unprocessed items repeatedly until all are saved to avoid data loss.

3. Final Answer:

   Check for unprocessed items after each batch write and retry them until none remain -> Option B

4. Quick Check:

   Retry unprocessed items until empty for safe writes [OK]

Hint: Always retry unprocessed items until all are saved [OK]

Common Mistakes:

• Ignoring unprocessed items causing data loss
• Writing items one by one causing inefficiency
• Logging without retrying unprocessed items