Expressions with SDK helpers in DynamoDB - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ query_result

intermediate

What is the output of this DynamoDB update expression?

Given a DynamoDB table with an item having attribute counter = 5, what will be the value of counter after running this update expression using AWS SDK helpers?

UpdateExpression: 'SET counter = counter + :inc'
ExpressionAttributeValues: { ':inc': 3 }

A counter = 8

B counter = 3

C counter = 5

D SyntaxError: invalid update expression

💡 Hint

Think about how the SET operation with addition works in DynamoDB update expressions.

The update expression adds the value of ':inc' (3) to the existing 'counter' value (5), resulting in 8.

📝 Syntax

intermediate

Which option is a valid DynamoDB condition expression using SDK helpers?

You want to check if the attribute status equals active before updating an item. Which condition expression is valid?

A ConditionExpression: 'status == :val', ExpressionAttributeValues: { ':val': 'active' }

B ConditionExpression: 'status = :val', ExpressionAttributeValues: { ':val': 'active' }

C ConditionExpression: '#st = :val', ExpressionAttributeNames: { '#st': 'status' }, ExpressionAttributeValues: { ':val': 'active' }

D ConditionExpression: 'status equals :val', ExpressionAttributeValues: { ':val': 'active' }

💡 Hint

Remember that attribute names sometimes need placeholders and the equality operator is a single equals sign.

Option C correctly uses an attribute name placeholder '#st' and the '=' operator for equality. Option C misses the placeholder which is required if 'status' is a reserved word or to avoid ambiguity. Options C and D use invalid operators.

❓ optimization

advanced

Which update expression is the most efficient to append an element to a list attribute tags?

You want to add the string 'new' to the end of the tags list attribute in a DynamoDB item. Which update expression is best?

A UpdateExpression: 'ADD tags :newTag', ExpressionAttributeValues: { ':newTag': ['new'] }

B UpdateExpression: 'SET tags = list_append(tags, :newTag)', ExpressionAttributeValues: { ':newTag': ['new'] }

C UpdateExpression: 'SET tags = append(tags, :newTag)', ExpressionAttributeValues: { ':newTag': ['new'] }

D UpdateExpression: 'SET tags = tags + :newTag', ExpressionAttributeValues: { ':newTag': ['new'] }

💡 Hint

Check which function is supported by DynamoDB to append to lists.

DynamoDB supports the list_append function to concatenate lists. Option B uses it correctly. Option B uses '+' which is invalid for lists. Option B uses ADD which is for sets or numbers, not lists. Option B uses a non-existent function 'append'.

🔧 Debug

advanced

What error will this DynamoDB update expression cause?

Consider this update expression:
UpdateExpression: 'SET #name = :val'
ExpressionAttributeValues: { ':val': 'John' }
But ExpressionAttributeNames is missing. What happens?

A SyntaxError: invalid expression syntax

B TypeError: ExpressionAttributeValues missing key ':name'

C No error, updates attribute named '#name' literally

D ValidationException: ExpressionAttributeNames missing for placeholder '#name'

💡 Hint

Placeholders starting with '#' must be defined in ExpressionAttributeNames.

Using '#name' without defining it in ExpressionAttributeNames causes a ValidationException because DynamoDB cannot resolve the placeholder.

🧠 Conceptual

expert

Which statement about DynamoDB condition expressions with SDK helpers is TRUE?

Select the correct statement about using condition expressions with AWS SDK helpers in DynamoDB.

A Condition expressions support logical operators like AND, OR, and NOT to combine multiple conditions.

B You must always use ExpressionAttributeNames for all attribute names in condition expressions.

C Condition expressions cannot check for attribute existence or absence.

D Condition expressions can only compare attributes to constant values, not to other attributes.

💡 Hint

Think about how you combine multiple conditions in DynamoDB.

DynamoDB condition expressions support logical operators AND, OR, and NOT to combine multiple conditions. Option A is false because you can compare attributes to other attributes. Option A is false because ExpressionAttributeNames are only needed when attribute names are reserved words or ambiguous. Option A is false because functions like attribute_exists and attribute_not_exists are supported.

Practice

1. What is the main purpose of using SDK helpers for expressions in DynamoDB?

easy

A. To safely build expressions and avoid syntax errors

B. To speed up the network connection to DynamoDB

C. To automatically create tables in DynamoDB

D. To encrypt data stored in DynamoDB

Solution

1. Step 1: Understand what expressions do

   Expressions tell DynamoDB what data to read or write and how to filter or update it.

2. Step 2: Role of SDK helpers

   SDK helpers help build these expressions safely, avoiding syntax mistakes and making code clearer.

3. Final Answer:

   To safely build expressions and avoid syntax errors -> Option A

4. Quick Check:

   SDK helpers = safe expressions [OK]

Hint: Helpers build expressions safely and clearly [OK]

Common Mistakes:

• Thinking SDK helpers speed up network
• Confusing helpers with table creation
• Assuming helpers encrypt data

2. Which of the following is the correct way to import the DynamoDB DocumentClient and ExpressionAttributeNames helper in JavaScript SDK v3?

easy

A. import { DynamoDBDocumentClient } from "aws-sdk";

B. import { DynamoDBClient, ExpressionAttributeNames } from "@aws-sdk/client-dynamodb";

C. const { DynamoDBClient, ExpressionAttributeNames } = require("aws-sdk");

D. import { DynamoDBDocumentClient, ExpressionAttributeNames } from "@aws-sdk/lib-dynamodb";

Solution

1. Step 1: Identify correct SDK package for helpers

   Expression helpers like ExpressionAttributeNames are in "@aws-sdk/lib-dynamodb", not "@aws-sdk/client-dynamodb".

2. Step 2: Correct import syntax for v3

   Use ES module import syntax with curly braces from "@aws-sdk/lib-dynamodb" for DocumentClient and helpers.

3. Final Answer:

   import { DynamoDBDocumentClient, ExpressionAttributeNames } from "@aws-sdk/lib-dynamodb"; -> Option D

4. Quick Check:

   Helpers come from lib-dynamodb package [OK]

Hint: Helpers are in lib-dynamodb, not client-dynamodb [OK]

Common Mistakes:

• Importing helpers from client-dynamodb package
• Using require() instead of import in v3
• Importing from aws-sdk (v2) instead of @aws-sdk

3. Given the following code snippet using DynamoDB SDK helpers, what will be the value of the UpdateExpression string?

const { UpdateExpression, ExpressionAttributeNames, ExpressionAttributeValues } = DynamoDBDocumentClient.update({
  TableName: "Users",
  Key: { userId: "123" },
  UpdateExpression: "set #n = :name",
  ExpressionAttributeNames: { "#n": "name" },
  ExpressionAttributeValues: { ":name": "Alice" }
});
console.log(UpdateExpression);

medium

A. SyntaxError

B. "set #n = :name"

C. "set #name = :name"

D. "set name = :name"

Solution

1. Step 1: Understand UpdateExpression usage

   The UpdateExpression uses placeholders like #n for attribute names and :name for values.

2. Step 2: Check what is logged

   The code logs the UpdateExpression string exactly as set: "set #n = :name" without substitution.

3. Final Answer:

   "set #n = :name" -> Option B

4. Quick Check:

   UpdateExpression logs raw string with placeholders [OK]

Hint: UpdateExpression logs placeholders, not replaced names [OK]

Common Mistakes:

• Expecting placeholders to be replaced in string
• Confusing attribute names with values
• Assuming syntax error due to placeholders

4. You wrote this update expression using SDK helpers but get an error: "ExpressionAttributeNames contains invalid key: #name". What is the likely cause?

UpdateExpression: "set #name = :val",
ExpressionAttributeNames: { "name": "username" },
ExpressionAttributeValues: { ":val": "Bob" }

medium

A. ExpressionAttributeNames keys must start with #

B. ExpressionAttributeValues keys must start with #

C. UpdateExpression should not use placeholders

D. ExpressionAttributeNames values must start with :

Solution

1. Step 1: Check ExpressionAttributeNames format

   Keys in ExpressionAttributeNames must start with # to match placeholders in UpdateExpression.

2. Step 2: Identify mismatch

   The key "name" lacks #, causing invalid key error.

3. Final Answer:

   ExpressionAttributeNames keys must start with # -> Option A

4. Quick Check:

   Attribute name keys start with # [OK]

Hint: Attribute name keys always start with # [OK]

Common Mistakes:

• Using keys without # in ExpressionAttributeNames
• Confusing keys in ExpressionAttributeValues
• Removing placeholders from UpdateExpression

5. You want to update a DynamoDB item to increment a numeric attribute "score" by 5 using SDK helpers. Which code snippet correctly builds the UpdateExpression and attribute values?

hard

A. UpdateExpression: "set score = score + :inc",
ExpressionAttributeValues: { ":inc": 5 }

B. UpdateExpression: "add score :inc",
ExpressionAttributeValues: { ":inc": 5 }

C. UpdateExpression: "set #s = #s + :inc",
ExpressionAttributeNames: { "#s": "score" },
ExpressionAttributeValues: { ":inc": 5 }

D. UpdateExpression: "increment score by 5"

Solution

1. Step 1: Use placeholders for attribute names

   Since "score" is an attribute name, use ExpressionAttributeNames with #s placeholder.

2. Step 2: Build UpdateExpression correctly

   Use "set #s = #s + :inc" to increment score by value in :inc.

3. Step 3: Provide ExpressionAttributeValues

   Set ":inc" to 5 to add 5 to score.

4. Final Answer:

   UpdateExpression: "set #s = #s + :inc", ExpressionAttributeNames: { "#s": "score" }, ExpressionAttributeValues: { ":inc": 5 } -> Option C

5. Quick Check:

   Use placeholders for names and values [OK]

Hint: Use # for names and : for values in expressions [OK]

Common Mistakes:

• Not using ExpressionAttributeNames for attribute names
• Using unsupported syntax like 'increment score by 5'
• Using 'add' without placeholders