Step Functions with DynamoDB - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the DynamoDB table name in the Step Functions task.

DynamoDB

{
  "Type": "Task",
  "Resource": "arn:aws:states:::dynamodb:putItem",
  "Parameters": {
    "TableName": "[1]",
    "Item": {
      "ID": { "S": "123" },
      "Status": { "S": "Pending" }
    }
  },
  "End": true
}

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

ADynamoDBTable

BTableName

CMyTable

DStepFunctionTable

Attempts:

3 left

💡 Hint

Common Mistakes

Using a placeholder like 'TableName' instead of the actual table name.

Confusing parameter names with values.

The TableName parameter must be set to the actual DynamoDB table name, such as MyTable.

2fill in blank

medium

Complete the code to specify the attribute name for the item key in the DynamoDB putItem task.

DynamoDB

"Item": {
  "[1]": { "S": "123" },
  "Status": { "S": "Pending" }
}

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

AItemKey

BKey

CPrimaryKey

DID

Attempts:

3 left

💡 Hint

Common Mistakes

Using generic names like 'Key' instead of the actual attribute name.

Confusing attribute names with parameter names.

The attribute name for the primary key in the item must match the table's key attribute, commonly ID.

3fill in blank

hard

Fix the error in the DynamoDB updateItem parameters by completing the attribute update expression.

DynamoDB

"UpdateExpression": "SET Status = [1]",
"ExpressionAttributeValues": {
  ":newStatus": { "S": "Completed" }
}

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

AnewStatus

B:newStatus

C"Completed"

D:Status

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting the colon in the placeholder name.

Using the actual string value instead of a placeholder.

The UpdateExpression must use a placeholder starting with a colon, like :newStatus, to refer to the value in ExpressionAttributeValues.

4fill in blank

hard

Fill both blanks to complete the DynamoDB getItem parameters for retrieving an item by its key.

DynamoDB

"TableName": "[1]",
"Key": {
  "[2]": { "S": "123" }
}

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

AMyTable

BStatus

CID

DItemKey

Attempts:

3 left

💡 Hint

Common Mistakes

Using attribute names that do not match the table schema.

Confusing table name with attribute names.

The TableName must be the actual table name, and the Key attribute must match the primary key attribute name, usually ID.

5fill in blank

hard

Fill all three blanks to complete the DynamoDB query parameters filtering items by status.

DynamoDB

"TableName": "[1]",
"KeyConditionExpression": "[2] = :statusVal",
"ExpressionAttributeValues": {
  ":statusVal": { "S": "[3]" }
}

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

AOrdersTable

BStatus

CPending

DOrderID

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing attribute names and table names.

Using incorrect values in the expression attribute values.

The TableName is the DynamoDB table name, the KeyConditionExpression uses the attribute name to filter, and the ExpressionAttributeValues provides the value to match, such as Pending.

Practice

1. What is the main purpose of using AWS Step Functions with DynamoDB?

easy

A. To automate workflows that involve storing and retrieving data step by step

B. To create visual dashboards for DynamoDB data

C. To replace DynamoDB with a different database

D. To manually update DynamoDB tables without code

Solution

1. Step 1: Understand Step Functions role

   Step Functions help run tasks in a specific order automatically.

2. Step 2: Connect with DynamoDB usage

   DynamoDB stores data quickly and safely, and Step Functions can automate tasks that read or write this data.

3. Final Answer:

   To automate workflows that involve storing and retrieving data step by step -> Option A

4. Quick Check:

   Step Functions + DynamoDB = automated data workflows [OK]

Hint: Step Functions automate tasks; DynamoDB stores data fast [OK]

Common Mistakes:

• Thinking Step Functions create dashboards
• Believing Step Functions replace DynamoDB
• Assuming manual updates are the main use

2. Which of the following is the correct Resource ARN for a DynamoDB operation (e.g., PutItem) in a Step Functions state using Amazon States Language (ASL)?

easy

A. "Resource": "arn:aws:s3:::TableName"

B. "Resource": "dynamodb://TableName"

C. "Resource": "arn:aws:states:::dynamodb:putItem"

D. "Resource": "lambda:TableName"

Solution

1. Step 1: Identify correct ARN format for DynamoDB

   Step Functions uses optimized integrations for DynamoDB with ARNs starting with "arn:aws:states:::dynamodb:" followed by the action like putItem.

2. Step 2: Check options for correct ARN

   "Resource": "arn:aws:states:::dynamodb:putItem" matches the correct optimized integration format; others reference wrong services or formats.

3. Final Answer:

   "Resource": "arn:aws:states:::dynamodb:putItem" -> Option C

4. Quick Check:

   Step Functions DynamoDB ARN = "arn:aws:states:::dynamodb:putItem" [OK]

Hint: Step Functions DynamoDB ARNs: arn:aws:states:::dynamodb:[action] [OK]

Common Mistakes:

• Using S3 or Lambda ARNs for DynamoDB
• Using URL-like syntax instead of ARN
• Missing optimized integration format

3. Given this Step Functions task state calling DynamoDB PutItem:

{
  "Type": "Task",
  "Resource": "arn:aws:states:::dynamodb:putItem",
  "Parameters": {
    "TableName": "Users",
    "Item": {
      "UserId": {"S": "123"},
      "Name": {"S": "Alice"}
    }
  },
  "End": true
}

What will happen when this state runs?

medium

A. It will add a new item with UserId 123 and Name Alice to the Users table

B. It will delete the item with UserId 123 from the Users table

C. It will update the Name of UserId 123 only if it exists

D. It will cause a syntax error and fail

Solution

1. Step 1: Understand the PutItem action

   PutItem adds a new item or replaces an existing item in DynamoDB with the given attributes.

2. Step 2: Analyze the Parameters

   The Parameters specify the table "Users" and an item with UserId "123" and Name "Alice" to be added.

3. Final Answer:

   It will add a new item with UserId 123 and Name Alice to the Users table -> Option A

4. Quick Check:

   PutItem adds or replaces item = It will add a new item with UserId 123 and Name Alice to the Users table [OK]

Hint: PutItem adds or replaces items in DynamoDB [OK]

Common Mistakes:

• Confusing PutItem with DeleteItem
• Thinking PutItem only updates existing items
• Assuming syntax error without checking JSON

4. You have this Step Functions state to get an item from DynamoDB:

{
  "Type": "Task",
  "Resource": "arn:aws:states:::dynamodb:getItem",
  "Parameters": {
    "TableName": "Orders",
    "Key": {
      "OrderId": {}
    }
  },
  "End": true
}

What is the problem with this state?

medium

A. TableName should be lowercase

B. The Resource ARN is incorrect for getItem

C. End cannot be true in a Task state

D. The Key value for OrderId is empty, causing a runtime error

Solution

1. Step 1: Check the Key parameter

   The Key must have a valid AttributeValue (with type like S/N); here OrderId is an empty object {}, which is invalid for DynamoDB keys.

2. Step 2: Validate other parameters

   Resource ARN is correct, TableName case is fine, and End:true is allowed in Task states.

3. Final Answer:

   The Key value for OrderId is empty, causing a runtime error -> Option D

4. Quick Check:

   Empty key value causes error = The Key value for OrderId is empty, causing a runtime error [OK]

Hint: DynamoDB keys must have non-empty values [OK]

Common Mistakes:

• Thinking ARN is wrong
• Believing TableName must be lowercase
• Assuming End:true is invalid

5. You want to create a Step Functions workflow that first writes a new user to DynamoDB, then reads the user back to confirm. Which sequence of states correctly achieves this?

hard

A. First a Task state with arn:aws:states:::dynamodb:getItem, then a Task state with arn:aws:states:::dynamodb:putItem

B. First a Task state with Resource arn:aws:states:::dynamodb:putItem, then a Task state with arn:aws:states:::dynamodb:getItem

C. A single Task state with arn:aws:states:::dynamodb:updateItem

D. Two parallel states both using arn:aws:states:::dynamodb:putItem

Solution

1. Step 1: Determine the write then read order

   You must first add the user with putItem, then read it with getItem to confirm.

2. Step 2: Check the options for correct sequence

   First a Task state with Resource arn:aws:states:::dynamodb:putItem, then a Task state with arn:aws:states:::dynamodb:getItem correctly sequences putItem followed by getItem; others have wrong order or wrong actions.

3. Final Answer:

   First a Task state with Resource arn:aws:states:::dynamodb:putItem, then a Task state with arn:aws:states:::dynamodb:getItem -> Option B

4. Quick Check:

   Write then read = First a Task state with Resource arn:aws:states:::dynamodb:putItem, then a Task state with arn:aws:states:::dynamodb:getItem [OK]

Hint: Write with putItem before reading with getItem [OK]

Common Mistakes:

• Reading before writing
• Using updateItem instead of putItem
• Running writes in parallel without read