Conditional expressions in DynamoDB - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ query_result

intermediate

What is the output of this conditional expression in DynamoDB?

Consider a DynamoDB table with an item having attribute age = 30. Which conditional expression will evaluate to true for this item?

DynamoDB

ConditionExpression: "age >= :min_age",
ExpressionAttributeValues: {":min_age": {"N": "25"}}

A Evaluates to true because 30 >= 25

B Evaluates to false because 30 is not less than 25

C Syntax error due to missing attribute name

D Evaluates to false because 30 equals 25

💡 Hint

Check if the attribute value meets the condition compared to the provided value.

The condition age >= :min_age checks if the attribute age is greater than or equal to 25. Since 30 is greater than 25, the condition is true.

📝 Syntax

intermediate

Which conditional expression syntax is valid in DynamoDB?

Identify the valid conditional expression syntax for checking if attribute status equals active.

A

ConditionExpression: "status equals :val",
ExpressionAttributeValues: {":val": {"S": "active"}}

B

ConditionExpression: "status == :val",
ExpressionAttributeValues: {":val": {"S": "active"}}

C

ConditionExpression: "status := :val",
ExpressionAttributeValues: {":val": {"S": "active"}}

D

ConditionExpression: "status = :val",
ExpressionAttributeValues: {":val": {"S": "active"}}

💡 Hint

Remember DynamoDB uses single equals = for equality in condition expressions.

DynamoDB condition expressions use = for equality. Double equals ==, equals, or := are invalid syntax.

❓ optimization

advanced

Which conditional expression is more efficient for checking multiple attribute values?

You want to check if attribute category is either books or electronics. Which conditional expression is more efficient?

A

ConditionExpression: "category = :books AND category = :electronics",
ExpressionAttributeValues: {":books": {"S": "books"}, ":electronics": {"S": "electronics"}}

B

ConditionExpression: "category BETWEEN :books AND :electronics",
ExpressionAttributeValues: {":books": {"S": "books"}, ":electronics": {"S": "electronics"}}

C

ConditionExpression: "category IN (:books, :electronics)",
ExpressionAttributeValues: {":books": {"S": "books"}, ":electronics": {"S": "electronics"}}

D

ConditionExpression: "category = :books OR category = :electronics",
ExpressionAttributeValues: {":books": {"S": "books"}, ":electronics": {"S": "electronics"}}

💡 Hint

Consider which expression is simpler and more readable for multiple values.

The IN operator is more efficient and clearer for checking if an attribute matches any value in a list. Using OR works but is longer. AND and BETWEEN are incorrect here.

🔧 Debug

advanced

Why does this conditional expression cause an error?

Given the expression below, why does DynamoDB return a syntax error?

DynamoDB

ConditionExpression: "attribute_exists(#sz) AND #sz = :val",
ExpressionAttributeNames: {"#sz": "size"},
ExpressionAttributeValues: {":val": {"S": "active"}}

A Because <code>attribute_exists</code> cannot be combined with other conditions using AND

B Because <code>size</code> is a reserved word and needs to be replaced with an expression attribute name

C Because <code>ExpressionAttributeValues</code> is missing a value for <code>:size</code>

D Because <code>attribute_exists</code> requires a value to compare

💡 Hint

Check if any attribute names are reserved keywords in DynamoDB.

size is a reserved word in DynamoDB. To use it in expressions, you must use an expression attribute name placeholder like #sz and define it in ExpressionAttributeNames.

🧠 Conceptual

expert

What happens if a conditional expression evaluates to false during a DynamoDB write operation?

When you perform a PutItem or UpdateItem with a conditional expression that evaluates to false, what is the result?

A The write operation is aborted and DynamoDB returns a <code>ConditionalCheckFailedException</code>

B The write operation proceeds but logs a warning internally

C The write operation ignores the condition and updates the item anyway

D The write operation retries automatically until the condition is true

💡 Hint

Think about how DynamoDB enforces conditions to maintain data integrity.

If the condition is false, DynamoDB stops the write and returns a ConditionalCheckFailedException to indicate the condition was not met.

Practice

1. What is the main purpose of using ConditionExpression in a DynamoDB operation?

easy

A. To create a new table automatically

B. To speed up the query execution

C. To ensure the operation only happens if certain conditions are met

D. To backup data before updating

Solution

1. Step 1: Understand what ConditionExpression does

   ConditionExpression is used to specify rules that must be true for the operation to proceed.

2. Step 2: Identify the purpose in data safety

   This helps prevent unwanted changes by checking conditions before updating or deleting.

3. Final Answer:

   To ensure the operation only happens if certain conditions are met -> Option C

4. Quick Check:

   ConditionExpression controls operation execution [OK]

Hint: ConditionExpression controls when changes happen [OK]

Common Mistakes:

• Thinking it speeds up queries
• Confusing with table creation
• Assuming it backs up data

2. Which of the following is the correct syntax to use a conditional expression that checks if attribute status equals active in a DynamoDB update?

easy

A. ConditionExpression: "status = 'active'"

B. ConditionExpression: "status != 'active'"

C. ConditionExpression: "status == active"

D. ConditionExpression: "#s = :active" with ExpressionAttributeNames and ExpressionAttributeValues

Solution

1. Step 1: Recognize reserved word handling

   Since status can be a reserved word, use placeholders like #s and :active.

2. Step 2: Correct syntax for equality check

   The expression must use single equals = and placeholders, not direct attribute names or double equals.

3. Final Answer:

   ConditionExpression: "#s = :active" with ExpressionAttributeNames and ExpressionAttributeValues -> Option D

4. Quick Check:

   Use placeholders for reserved words [OK]

Hint: Use placeholders (#, :) for reserved words in conditions [OK]

Common Mistakes:

• Using double equals (==) instead of single equals (=)
• Not using placeholders for reserved words
• Using wrong inequality operator

3. Given this DynamoDB update command snippet:

UpdateExpression: "SET #qty = :newQty"
ConditionExpression: "#qty < :maxQty"
ExpressionAttributeNames: {"#qty": "quantity"}
ExpressionAttributeValues: {":newQty": 10, ":maxQty": 20}

What happens if the current quantity is 25?

medium

A. The update fails because condition is false

B. The update throws a syntax error

C. The update ignores the condition and sets quantity to 10

D. The update succeeds and sets quantity to 10

Solution

1. Step 1: Understand the condition check

   The condition requires current quantity to be less than 20 for update to proceed.

2. Step 2: Compare current quantity with maxQty

   Since current quantity is 25, which is not less than 20, the condition fails.

3. Final Answer:

   The update fails because condition is false -> Option A

4. Quick Check:

   Condition false blocks update [OK]

Hint: Update only if condition is true, else it fails [OK]

Common Mistakes:

• Assuming update ignores condition
• Thinking condition causes syntax error
• Believing update always succeeds

4. You wrote this DynamoDB update:

UpdateExpression: "SET total = :p"
ConditionExpression: "total > :min"
ExpressionAttributeValues: {":p": 100, ":min": 50}

But it returns a validation error. What is the likely cause?

medium

A. Using total directly without placeholder in ConditionExpression

B. Using incorrect operator in ConditionExpression

C. Missing ExpressionAttributeNames for reserved word total

D. Missing comma in ExpressionAttributeValues

Solution

1. Step 1: Check if total is reserved

   total is a reserved word in DynamoDB, so it must use a placeholder like #pr.

2. Step 2: Identify missing placeholder usage

   The ConditionExpression uses total directly, causing validation error.

3. Final Answer:

   Using total directly without placeholder in ConditionExpression -> Option A

4. Quick Check:

   Reserved words need placeholders [OK]

Hint: Always use placeholders for reserved words in conditions [OK]

Common Mistakes:

• Ignoring reserved word rules
• Assuming operators cause error
• Overlooking syntax in ExpressionAttributeValues

5. You want to update a user's score only if the current score is less than 100 and the status is active. Which is the correct ConditionExpression to use?

hard

A. "score < 100 AND status = 'active'" without placeholders

B. "#sc < :maxScore AND #st = :activeStatus" with ExpressionAttributeNames {"#sc": "score", "#st": "status"} and ExpressionAttributeValues {":maxScore": 100, ":activeStatus": "active"}

C. "score <= 100 OR status = 'active'" with placeholders

D. "#sc > :maxScore AND #st = :activeStatus" with placeholders

Solution

1. Step 1: Use placeholders for reserved words

   Both score and status can be reserved, so use #sc and #st.

2. Step 2: Combine conditions correctly

   Use AND to require both conditions: score less than 100 and status equals active.

3. Step 3: Use correct operators and values

   Use < for less than, and equals = for status check with placeholders for values.

4. Final Answer:

   "#sc < :maxScore AND #st = :activeStatus" with ExpressionAttributeNames {"#sc": "score", "#st": "status"} and ExpressionAttributeValues {":maxScore": 100, ":activeStatus": "active"} -> Option B

5. Quick Check:

   Use AND with placeholders for multiple conditions [OK]

Hint: Use AND and placeholders for multiple conditions [OK]

Common Mistakes:

• Using OR instead of AND
• Not using placeholders for reserved words
• Using wrong comparison operators