[Solved] You tried to add a new region to an existing Global Table but got an error. What is a common cause? - Ans: The new region's table has a different primary key schema | DynamoDB

DynamoDB - Backup and Recovery

You tried to add a new region to an existing Global Table but got an error. What is a common cause?

AYou forgot to enable encryption on the new region

BThe new region's table has a different primary key schema

CGlobal Tables do not support more than two regions

DYou used the update-table command instead of update-global-table

Step-by-Step Solution

Solution:

Step 1: Check schema requirements for Global Tables
All replicas in Global Tables must have the same primary key schema to replicate correctly.
Step 2: Identify cause of error
If the new region's table has a different primary key schema, adding it will fail.
Final Answer:
The new region's table has a different primary key schema -> Option B
Quick Check:
Matching primary keys required for Global Tables [OK]

Quick Trick: All regions must share the same primary key schema [OK]

Common Mistakes:

MISTAKES

Master "Backup and Recovery" in DynamoDB

9 interactive learning modes - each teaches the same concept differently

More DynamoDB Quizzes

You tried to add a new region to an existing Global Table but got an error. What is a common cause?