TransactGetItems in DynamoDB - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the operation type for a TransactGetItems request.

DynamoDB

{
  "TransactItems": [
    {
      "[1]": {
        "Key": {"Id": {"S": "123"}},
        "TableName": "Users"
      }
    }
  ]
}

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

ADelete

BGet

CUpdate

DPut

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Put' or 'Update' instead of 'Get' in TransactGetItems.

Confusing TransactGetItems with TransactWriteItems.

The TransactGetItems request requires the operation type to be Get for each item to retrieve.

2fill in blank

medium

Complete the code to specify the primary key attribute name in the Key object.

DynamoDB

{
  "TransactItems": [
    {
      "Get": {
        "Key": {"[1]": {"S": "abc123"}},
        "TableName": "Orders"
      }
    }
  ]
}

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

AOrderId

BUserId

CProductId

DTransactionId

Attempts:

3 left

💡 Hint

Common Mistakes

Using a non-primary key attribute in the Key object.

Misspelling the key attribute name.

The primary key attribute for the Orders table is typically OrderId, which identifies the item to get.

3fill in blank

hard

Fix the error in the TransactGetItems request by completing the missing field.

DynamoDB

{
  "TransactItems": [
    {
      "Get": {
        "Key": {"UserId": {"S": "user789"}},
        "[1]": "Customers"
      }
    }
  ]
}

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

AProjectionExpression

BIndexName

CConditionExpression

DTableName

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting the TableName field causes errors.

Using IndexName instead of TableName in TransactGetItems.

The TableName field is required to specify which table to get the item from.

4fill in blank

hard

Fill both blanks to create a TransactGetItems request with two items from different tables.

DynamoDB

{
  "TransactItems": [
    {
      "[1]": {
        "Key": {"Id": {"S": "101"}},
        "TableName": "Products"
      }
    },
    {
      "[2]": {
        "Key": {"UserId": {"S": "u202"}},
        "TableName": "Users"
      }
    }
  ]
}

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

AGet

BPut

CUpdate

DDelete

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing 'Put' or 'Update' operations in TransactGetItems.

Using different operation types for items in the same request.

Both items in a TransactGetItems request must use the Get operation to retrieve data.

5fill in blank

hard

Fill all three blanks to build a TransactGetItems request with condition expression and projection expression.

DynamoDB

{
  "TransactItems": [
    {
      "Get": {
        "Key": {"OrderId": {"S": "ord303"}},
        "TableName": "Orders",
        "[1]": "attribute_exists(OrderId)",
        "[2]": "OrderDate, TotalAmount",
        "[3]": "OrdersIndex"
      }
    }
  ]
}

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

AConditionExpression

BProjectionExpression

CIndexName

DFilterExpression

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing FilterExpression with ConditionExpression in TransactGetItems.

Omitting IndexName when querying a secondary index.

The ConditionExpression ensures the item exists, ProjectionExpression limits returned attributes, and IndexName specifies the index to query.

Practice

1. What is the main purpose of using TransactGetItems in DynamoDB?

easy

A. To delete multiple items in separate requests

B. To write multiple items atomically in a single request

C. To update a single item with conditional checks

D. To read multiple items atomically in a single request

Solution

1. Step 1: Understand the function of TransactGetItems

   TransactGetItems is designed to read multiple items from one or more tables atomically, meaning all reads succeed or fail together.

2. Step 2: Differentiate from other operations

   Unlike TransactWriteItems which writes or updates, TransactGetItems only reads items in a single atomic request.

3. Final Answer:

   To read multiple items atomically in a single request -> Option D

4. Quick Check:

   TransactGetItems = atomic multi-item read [OK]

Hint: TransactGetItems reads multiple items atomically [OK]

Common Mistakes:

• Confusing TransactGetItems with write operations
• Thinking it updates or deletes items
• Assuming it reads items one by one

2. Which of the following is the correct way to specify an item key in a TransactGetItems request?

easy

A. "Key": { "UserId": "123" }

B. "Key": { "UserId": 123 }

C. "Key": { "UserId": { "S": "123" } }

D. "Key": { "UserId": { "N": "123" } }

Solution

1. Step 1: Recall DynamoDB key format in requests

   DynamoDB expects attribute values to be typed, so string keys use {"S": "value"} format.

2. Step 2: Check each option's key format

   "Key": { "UserId": { "S": "123" } } uses the correct string type format. "Key": { "UserId": "123" } lacks type wrapper, C uses number without type, D uses number type but key is string.

3. Final Answer:

   "Key": { "UserId": { "S": "123" } } -> Option C

4. Quick Check:

   Keys need type wrappers like {"S": "value"} [OK]

Hint: DynamoDB keys need type wrappers like {"S": "value"} [OK]

Common Mistakes:

• Omitting the type wrapper for attribute values
• Using number type for string keys
• Passing raw values without attribute type

3. Given the following TransactGetItems request, what will be the result if both items exist?

{
  "TransactItems": [
    { "Get": { "TableName": "Users", "Key": { "UserId": { "S": "u1" } } } },
    { "Get": { "TableName": "Orders", "Key": { "OrderId": { "N": "101" } } } }
  ]
}

medium

A. Returns both items in the order specified

B. Returns only the first item found

C. Returns an error because keys have different types

D. Returns items but unordered

Solution

1. Step 1: Understand TransactGetItems behavior

   It returns all requested items atomically if they exist, preserving the order of requests.

2. Step 2: Analyze the request keys and tables

   Keys are correctly typed and tables exist, so no error occurs and both items are returned in order.

3. Final Answer:

   Returns both items in the order specified -> Option A

4. Quick Check:

   TransactGetItems returns all requested items in order [OK]

Hint: TransactGetItems returns all items in request order if found [OK]

Common Mistakes:

• Assuming only one item is returned
• Thinking keys with different types cause errors
• Believing items are returned unordered

4. You wrote this TransactGetItems request but get a validation error:

{
  "TransactItems": [
    { "Get": { "TableName": "Users", "Key": { "UserId": "u1" } } }
  ]
}

What is the likely cause?

medium

A. Missing attribute type wrapper for the key value

B. TableName is incorrect

C. TransactItems must have at least two items

D. Key attribute name is invalid

Solution

1. Step 1: Check key format in the request

   The key value "UserId": "u1" lacks the required attribute type wrapper like {"S": "u1"}.

2. Step 2: Validate other parts

   TableName is valid, TransactItems can have one or more items, and key attribute name is valid.

3. Final Answer:

   Missing attribute type wrapper for the key value -> Option A

4. Quick Check:

   Key values need type wrappers like {"S": "value"} [OK]

Hint: Always wrap key values with attribute types like {"S": "value"} [OK]

Common Mistakes:

• Omitting attribute type wrappers in keys
• Assuming TransactItems needs multiple items
• Mistaking table name or key attribute name as error

5. You want to atomically read two items from different tables: Users with key {"UserId": {"S": "u1"}} and Orders with key {"OrderId": {"N": "101"}}. Which TransactGetItems request correctly achieves this?

hard

A. { "TransactItems": [ { "Get": { "TableName": "Users", "Key": { "UserId": "u1" } } }, { "Get": { "TableName": "Orders", "Key": { "OrderId": 101 } } } ] }

B. { "TransactItems": [ { "Get": { "TableName": "Users", "Key": { "UserId": { "S": "u1" } } } }, { "Get": { "TableName": "Orders", "Key": { "OrderId": { "N": "101" } } } } ] }

C. { "TransactItems": [ { "Get": { "TableName": "Users", "Key": { "UserId": { "N": "u1" } } } }, { "Get": { "TableName": "Orders", "Key": { "OrderId": { "S": "101" } } } ] }

D. { "TransactItems": [ { "Get": { "TableName": "Users", "Key": { "UserId": { "S": "u1" } } } }, { "Get": { "TableName": "Orders", "Key": { "OrderId": { "S": "101" } } } ] }

Solution

1. Step 1: Verify key attribute types match expected data types

   UserId is a string, so it needs {"S": "u1"}. OrderId is a number, so it needs {"N": "101"}.

2. Step 2: Check each option for correct key typing

   { "TransactItems": [ { "Get": { "TableName": "Users", "Key": { "UserId": { "S": "u1" } } } }, { "Get": { "TableName": "Orders", "Key": { "OrderId": { "N": "101" } } } } ] } correctly uses {"S": "u1"} and {"N": "101"}. { "TransactItems": [ { "Get": { "TableName": "Users", "Key": { "UserId": "u1" } } }, { "Get": { "TableName": "Orders", "Key": { "OrderId": 101 } } } ] } omits type wrappers. { "TransactItems": [ { "Get": { "TableName": "Users", "Key": { "UserId": { "N": "u1" } } } }, { "Get": { "TableName": "Orders", "Key": { "OrderId": { "S": "101" } } } ] } swaps types incorrectly. { "TransactItems": [ { "Get": { "TableName": "Users", "Key": { "UserId": { "S": "u1" } } } }, { "Get": { "TableName": "Orders", "Key": { "OrderId": { "S": "101" } } } ] } uses string type for OrderId which should be number.

3. Final Answer:

   { "TransactItems": [ { "Get": { "TableName": "Users", "Key": { "UserId": { "S": "u1" } } } }, { "Get": { "TableName": "Orders", "Key": { "OrderId": { "N": "101" } } } } ] } -> Option B

4. Quick Check:

   Match key types exactly with attribute types [OK]

Hint: Match key attribute types exactly: string = {"S"}, number = {"N"} [OK]

Common Mistakes:

• Using raw values without type wrappers
• Mixing up string and number attribute types
• Assuming string type for numeric keys