Why update expressions modify attributes in DynamoDB - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does the SET action in an UpdateExpression work?

In DynamoDB, when you use an UpdateExpression with the SET action, what happens to the specified attribute?

A It deletes the attribute from the item.

B It only creates the attribute if it doesn't exist; otherwise, it leaves it unchanged.

C It creates the attribute if it doesn't exist or replaces its value if it does.

D It appends the new value to the existing attribute value.

💡 Hint

Think about whether SET replaces or preserves existing values.

The SET action in an UpdateExpression either creates the attribute if it is missing or replaces the existing value with the new one.

❓ query_result

intermediate

What is the result of using REMOVE in an UpdateExpression?

Given an item with attribute status set to "active", what will be the result after applying this UpdateExpression?

REMOVE status

A The attribute <code>status</code> value changes to an empty string.

B The attribute <code>status</code> is deleted from the item.

C The attribute <code>status</code> value remains unchanged.

D The attribute <code>status</code> is set to <code>null</code> but remains in the item.

💡 Hint

Consider what REMOVE does to attributes in DynamoDB.

REMOVE deletes the specified attribute entirely from the item, so it no longer exists after the update.

📝 Syntax

advanced

Identify the correct UpdateExpression syntax to increment a numeric attribute

Which UpdateExpression correctly increments the numeric attribute counter by 1?

A SET counter = counter + :inc

B ADD counter :inc

C SET counter + :inc

D INCREMENT counter BY :inc

💡 Hint

Remember the syntax for arithmetic operations in UpdateExpression.

The correct syntax to increment is SET counter = counter + :inc. The ADD action is used differently and requires a number or set, but the question asks for UpdateExpression syntax.

❓ optimization

advanced

Why prefer UpdateExpression over GetItem + PutItem for modifying attributes?

What is the main advantage of using an UpdateExpression to modify attributes instead of reading the item with GetItem and then writing it back with PutItem?

A GetItem + PutItem avoids conflicts better than UpdateExpression.

B GetItem + PutItem is faster because it uses two separate operations.

C UpdateExpression requires more data transfer than GetItem + PutItem.

D UpdateExpression modifies attributes atomically and reduces network calls.

💡 Hint

Think about atomicity and efficiency in database operations.

UpdateExpression modifies attributes atomically in a single request, reducing network overhead and avoiding race conditions compared to separate GetItem and PutItem calls.

🔧 Debug

expert

Why does this UpdateExpression fail to modify the attribute?

Consider this UpdateExpression:

SET #attr = :val

with ExpressionAttributeNames = {"#attr": "score"} and ExpressionAttributeValues = {":val": 10}.

Why might this update not change the score attribute?

A The attribute <code>score</code> is part of the primary key and cannot be updated.

B The ExpressionAttributeValues is missing the colon prefix for the value.

C The UpdateExpression syntax is invalid because it lacks a WHERE clause.

D The attribute name placeholder is not defined in ExpressionAttributeNames.

💡 Hint

Remember which attributes DynamoDB allows to be updated.

Attributes that are part of the primary key (partition key or sort key) cannot be updated. Attempting to do so will fail silently or with an error depending on the SDK.