Transaction error handling in DynamoDB - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ query_result

intermediate

What happens when a DynamoDB transaction fails due to a condition check?

Consider a DynamoDB transaction that includes a condition check on an item attribute. If the condition fails, what is the result of the transaction?

DynamoDB

TransactWriteItems with ConditionCheck failing

A The entire transaction is rolled back and no changes are applied.

B Only the condition check fails but other writes in the transaction succeed.

C The transaction partially commits changes before the failure.

D The transaction ignores the condition check and commits all writes.

💡 Hint

Think about atomicity in transactions.

DynamoDB transactions are atomic. If any condition check fails, the entire transaction is rolled back and no changes are applied.

🧠 Conceptual

intermediate

Which error code indicates a transaction conflict in DynamoDB?

When two transactions try to modify the same item simultaneously, DynamoDB returns a specific error code. Which one is it?

A InternalServerError

B ConditionalCheckFailedException

C ProvisionedThroughputExceededException

D TransactionConflictException

💡 Hint

Look for the error related to transaction conflicts.

TransactionConflictException is returned when concurrent transactions conflict on the same item.

📝 Syntax

advanced

Identify the syntax error in this DynamoDB transaction request snippet

Which option contains a syntax error in the TransactWriteItems request?

DynamoDB

TransactWriteItems({
  [
    {
      Put: {
        TableName: "Users",
        Item: { UserId: { S: "123" }, Name: { S: "Alice" } }
      }
    },
    {
      Update: {
        TableName: "Users",
        Key: { UserId: { S: "123" } },
        UpdateExpression: "SET Age = :age",
        ExpressionAttributeValues: { ":age": { N: "30" } }
      }
    }
  ]
})

A TransactWriteItems request is missing the required 'TransactItems' array.

B ExpressionAttributeValues key ":age" is missing the colon.

C UpdateExpression uses SET but ExpressionAttributeValues is empty.

D Missing ConditionCheck in one of the TransactItems.

💡 Hint

Check the structure of the request object.

The TransactWriteItems request must include a 'TransactItems' array. If missing, it causes a syntax error.

🔧 Debug

advanced

Why does this DynamoDB transaction return a ConditionalCheckFailedException?

Given this transaction includes a ConditionCheck on an attribute that does not exist, why does it fail?

DynamoDB

TransactWriteItems({
  TransactItems: [
    {
      ConditionCheck: {
        TableName: "Orders",
        Key: { OrderId: { S: "order123" } },
        ConditionExpression: "attribute_exists(Status) AND Status = :val",
        ExpressionAttributeValues: { ":val": { S: "Pending" } }
      }
    },
    {
      Update: {
        TableName: "Orders",
        Key: { OrderId: { S: "order123" } },
        UpdateExpression: "SET Status = :newval",
        ExpressionAttributeValues: { ":newval": { S: "Processed" } }
      }
    }
  ]
})

A The UpdateExpression syntax is invalid and causes the failure.

B The attribute 'Status' does not exist on the item, so the condition fails.

C ExpressionAttributeValues keys are duplicated causing a conflict.

D The transaction is missing a required ReturnValuesOnConditionCheckFailure parameter.

💡 Hint

Check the condition expression and the item attributes.

If the attribute 'Status' does not exist on the item, the condition 'attribute_exists(Status)' fails, causing the transaction to abort with ConditionalCheckFailedException.

❓ optimization

expert

How to reduce transaction conflicts in high-concurrency DynamoDB applications?

You have a high-concurrency application using DynamoDB transactions that often fail with TransactionConflictException. Which approach best reduces conflicts?

A Increase provisioned throughput to handle more transactions simultaneously.

B Remove condition checks to avoid transaction aborts.

C Partition data to minimize overlapping writes and use smaller transactions.

D Use batch writes instead of transactions to improve speed.

💡 Hint

Think about how to avoid multiple transactions modifying the same items.

Partitioning data to reduce overlapping writes and keeping transactions small reduces conflicts and improves success rates.

Practice

1. What is the main purpose of transaction error handling in DynamoDB?

easy

A. To ensure all changes in a transaction happen together or not at all

B. To speed up query performance

C. To allow partial updates in a transaction

D. To automatically backup data after each transaction

Solution

1. Step 1: Understand transaction atomicity

   Transactions in DynamoDB ensure that either all operations succeed or none do, preventing partial updates.

2. Step 2: Identify the role of error handling

   Error handling detects when a transaction fails and prevents inconsistent data states.

3. Final Answer:

   To ensure all changes in a transaction happen together or not at all -> Option A

4. Quick Check:

   Transaction atomicity = To ensure all changes in a transaction happen together or not at all [OK]

Hint: Remember: transactions are all-or-nothing operations [OK]

Common Mistakes:

• Thinking transactions allow partial success
• Confusing error handling with performance tuning
• Assuming automatic backups happen on errors

2. Which of the following is the correct way to catch a transaction error in DynamoDB using JavaScript?

easy

A. try { await client.transactWrite(params); } catch (error) { if (error.code === 'TransactionCanceledException') { /* handle */ } }

B. await client.transactWrite(params).catch(error => if error.code == 'TransactionCanceledException' { /* handle */ })

C. try { client.transactWrite(params); } catch error { if error.code = 'TransactionCanceledException' { /* handle */ } }

D. client.transactWrite(params).then().catch(error => if (error.code === 'TransactionCanceledException') { /* handle */ })

Solution

1. Step 1: Check syntax for try-catch with async/await

   try { await client.transactWrite(params); } catch (error) { if (error.code === 'TransactionCanceledException') { /* handle */ } } correctly uses try-catch with await and compares error.code with 'TransactionCanceledException'.

2. Step 2: Identify syntax errors in other options

   await client.transactWrite(params).catch(error => if error.code == 'TransactionCanceledException' { /* handle */ }) has incorrect arrow function syntax; try { client.transactWrite(params); } catch error { if error.code = 'TransactionCanceledException' { /* handle */ } } misses parentheses and uses wrong assignment; client.transactWrite(params).then().catch(error => if (error.code === 'TransactionCanceledException') { /* handle */ }) uses then() without await which is less clear.

3. Final Answer:

   try { await client.transactWrite(params); } catch (error) { if (error.code === 'TransactionCanceledException') { /* handle */ } } -> Option A

4. Quick Check:

   Correct try-catch syntax = try { await client.transactWrite(params); } catch (error) { if (error.code === 'TransactionCanceledException') { /* handle */ } } [OK]

Hint: Use try-catch with await and check error.code string [OK]

Common Mistakes:

• Missing parentheses in catch block
• Using assignment '=' instead of comparison '==='
• Incorrect arrow function syntax in catch

3. Given this code snippet, what will be the output if the transaction fails due to a conditional check failure?

try {
  await client.transactWrite(params);
  console.log('Transaction succeeded');
} catch (error) {
  if (error.code === 'TransactionCanceledException') {
    console.log('Transaction failed: ' + error.message);
  } else {
    console.log('Other error');
  }
}

medium

A. Other error

B. Transaction succeeded

C. Transaction failed: ConditionalCheckFailed

D. No output

Solution

1. Step 1: Understand error handling flow

   If the transaction fails due to a conditional check, DynamoDB throws TransactionCanceledException with a message indicating ConditionalCheckFailed.

2. Step 2: Trace the catch block output

   The catch block checks error.code and prints 'Transaction failed: ' plus the error message, so it outputs the failure message.

3. Final Answer:

   Transaction failed: ConditionalCheckFailed -> Option C

4. Quick Check:

   Error code check prints failure message = Transaction failed: ConditionalCheckFailed [OK]

Hint: TransactionCanceledException means failure message logs [OK]

Common Mistakes:

• Assuming success message prints on failure
• Ignoring error.code check
• Confusing error messages with other exceptions

4. Identify the error in this DynamoDB transaction error handling code snippet:

try {
  client.transactWrite(params);
} catch (error) {
  if (error.code === 'TransactionCanceledException') {
    console.log('Transaction failed');
  }
}

medium

A. Try block should not be used with transactWrite

B. Incorrect error code string in if condition

C. Using console.log inside catch is invalid

D. Missing await before client.transactWrite causing unhandled promise

Solution

1. Step 1: Check async call handling

   client.transactWrite returns a promise; without await, errors won't be caught by try-catch.

2. Step 2: Confirm error handling correctness

   The error code string and console.log usage are correct; try-catch is valid for async with await.

3. Final Answer:

   Missing await before client.transactWrite causing unhandled promise -> Option D

4. Quick Check:

   Async calls need await for try-catch to work [OK]

Hint: Always await async calls inside try to catch errors [OK]

Common Mistakes:

• Omitting await on async functions
• Misnaming error codes
• Thinking console.log is disallowed in catch

5. You want to retry a DynamoDB transaction only if it fails due to a TransactionCanceledException caused by a conditional check failure. Which approach correctly implements this retry logic?

hard

A. Use try-catch but do not check error code; retry only once

B. Use a loop with try-catch; inside catch, check if error.code is 'TransactionCanceledException' and error.message contains 'ConditionalCheckFailed', then retry up to max attempts

C. Retry unconditionally on any error without checking error type

D. Ignore errors and assume transaction will succeed eventually

Solution

1. Step 1: Understand selective retry conditions

   Retry should happen only if error.code is 'TransactionCanceledException' and message indicates conditional check failure.

2. Step 2: Implement retry with loop and max attempts

   Use a loop with try-catch, check error details, and retry up to a limit to avoid infinite loops.

3. Final Answer:

   Use a loop with try-catch; inside catch, check if error.code is 'TransactionCanceledException' and error.message contains 'ConditionalCheckFailed', then retry up to max attempts -> Option B

4. Quick Check:

   Retry only on specific error with loop and checks = Use a loop with try-catch; inside catch, check if error.code is 'TransactionCanceledException' and error.message contains 'ConditionalCheckFailed', then retry up to max attempts [OK]

Hint: Retry only on specific error codes and messages [OK]

Common Mistakes:

• Retrying on all errors causing infinite loops
• Not checking error.message for conditional failure
• Ignoring max retry limits