Cross-region replication (Global Tables) in DynamoDB - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Cross-region replication in DynamoDB Global Tables?

Cross-region replication in DynamoDB Global Tables means automatically copying your table data across multiple AWS regions to keep them in sync. This helps your app stay fast and available worldwide.

intermediate

How does DynamoDB Global Tables handle data conflicts?

DynamoDB Global Tables uses a last-writer-wins approach based on timestamps to resolve conflicts when the same item is updated in different regions at the same time.

beginner

Why use Global Tables instead of a single-region DynamoDB table?

Global Tables improve availability and reduce latency by letting users read and write data in the region closest to them. They also provide automatic replication and disaster recovery.

intermediate

Can you add or remove regions from a DynamoDB Global Table after creation?

Yes, you can add or remove replica regions from a Global Table anytime to adjust to your app’s needs without downtime.

intermediate

What happens if a region goes down in a Global Table setup?

If a region goes down, your app can still read and write data in other regions. When the down region recovers, DynamoDB syncs the data automatically.

What is the main purpose of DynamoDB Global Tables?

A To create indexes on tables

B To backup data to Amazon S3

C To replicate data across multiple AWS regions automatically

D To encrypt data at rest

Global Tables automatically replicate your DynamoDB table data across multiple AWS regions for high availability and low latency.

How does DynamoDB Global Tables resolve write conflicts?

A Last-writer-wins based on timestamps

B First-writer-wins

C Manual conflict resolution by user

D Random selection

DynamoDB Global Tables use last-writer-wins conflict resolution based on timestamps to keep data consistent.

Can you add a new region to an existing Global Table?

A No, you must create a new table

B Only during table creation

C Only if the table is empty

D Yes, anytime without downtime

You can add or remove replica regions from a Global Table anytime without downtime.

What happens if one region in a Global Table fails?

A Other regions continue working and sync later

B Writes are blocked globally

C All data is lost

D The table is deleted

If a region fails, other regions continue to operate and data syncs back when the region recovers.

Which of these is NOT a benefit of using Global Tables?

A Lower latency for global users

B Manual data backup scheduling

C Automatic multi-region replication

D Improved availability

Manual data backup scheduling is not a feature of Global Tables; backups are separate from replication.

Explain how DynamoDB Global Tables keep data consistent across regions.

Think about how updates in different places are merged.

Describe the benefits of using Cross-region replication with DynamoDB Global Tables for a global app.

Consider user experience and data safety worldwide.

Practice

1. What is the main purpose of DynamoDB Global Tables in cross-region replication?

easy

A. To keep data copied and synchronized across multiple AWS regions

B. To create backups of tables in the same region

C. To increase the size limit of a single DynamoDB table

D. To encrypt data only in one region

Solution

1. Step 1: Understand Global Tables concept

   Global Tables replicate data automatically across multiple AWS regions to keep them in sync.

2. Step 2: Identify the main purpose

   This replication helps applications stay fast and available worldwide by having data close to users.

3. Final Answer:

   To keep data copied and synchronized across multiple AWS regions -> Option A

4. Quick Check:

   Global Tables = cross-region data sync [OK]

Hint: Global Tables = data sync across regions [OK]

Common Mistakes:

• Confusing backups with replication
• Thinking Global Tables increase table size
• Assuming encryption is the main feature

2. Which AWS CLI command is used to create a DynamoDB Global Table?

easy

A. aws dynamodb delete-global-table --table-name MyTable

B. aws dynamodb create-table --table-name MyTable --region us-east-1

C. aws dynamodb create-global-table --global-table-name MyTable --replication-group RegionName=us-east-1

D. aws dynamodb update-global-table --table-name MyTable

Solution

1. Step 1: Identify the correct command for creating Global Tables

   The command to create a Global Table is create-global-table with replication group specifying regions.

2. Step 2: Check options

   aws dynamodb create-global-table --global-table-name MyTable --replication-group RegionName=us-east-1 uses create-global-table with replication group, which is correct. Others are for creating normal tables, updating, or deleting.

3. Final Answer:

   aws dynamodb create-global-table --global-table-name MyTable --replication-group RegionName=us-east-1 -> Option C

4. Quick Check:

   Create Global Table = create-global-table command [OK]

Hint: Use create-global-table to make Global Tables [OK]

Common Mistakes:

• Using create-table instead of create-global-table
• Confusing update or delete commands
• Missing replication group parameter

3. Given a DynamoDB Global Table replicated in us-east-1 and eu-west-1, what happens if you write an item in us-east-1?

medium

A. The item is immediately available in eu-west-1 after replication

B. The item is only stored in us-east-1 and not replicated

C. The write fails because cross-region writes are not allowed

D. The item is stored in eu-west-1 but not in us-east-1

Solution

1. Step 1: Understand replication behavior of Global Tables

   Global Tables replicate writes made in one region to all other regions automatically and quickly.

2. Step 2: Apply to the scenario

   Writing an item in us-east-1 will replicate it to eu-west-1, making it available there.

3. Final Answer:

   The item is immediately available in eu-west-1 after replication -> Option A

4. Quick Check:

   Write in one region = replicate to others [OK]

Hint: Writes replicate automatically across regions [OK]

Common Mistakes:

• Thinking writes stay local only
• Assuming writes fail across regions
• Confusing replication direction

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

medium

A. You forgot to enable encryption on the new region

B. The new region's table has a different primary key schema

C. Global Tables do not support more than two regions

D. You used the update-table command instead of update-global-table

Solution

1. Step 1: Check schema requirements for Global Tables

   All replicas in Global Tables must have the same primary key schema to replicate correctly.

2. Step 2: Identify cause of error

   If the new region's table has a different primary key schema, adding it will fail.

3. Final Answer:

   The new region's table has a different primary key schema -> Option B

4. Quick Check:

   Matching primary keys required for Global Tables [OK]

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

Common Mistakes:

• Assuming encryption causes add-region errors
• Believing Global Tables limit regions to two
• Confusing update-table with update-global-table commands

5. You want to design a Global Table for a worldwide app with users in Asia, Europe, and America. Which strategy best reduces latency and ensures data consistency?

hard

A. Create replicas in Asia, Europe, and America with strongly consistent reads enabled

B. Create a single table in one region and route all traffic there

C. Create replicas only in Asia and America to reduce costs

D. Create replicas in Asia, Europe, and America regions with eventual consistency reads

Solution

1. Step 1: Consider latency and availability

   Replicas in all user regions reduce latency by serving data locally.

2. Step 2: Understand consistency trade-offs

   Strongly consistent reads across regions are not supported; eventual consistency is used to balance latency and consistency.

3. Step 3: Evaluate options

   Create replicas in Asia, Europe, and America regions with eventual consistency reads creates replicas in all needed regions with eventual consistency, which is best for performance and availability.

4. Final Answer:

   Create replicas in Asia, Europe, and America regions with eventual consistency reads -> Option D

5. Quick Check:

   Global Tables + eventual consistency = low latency worldwide [OK]

Hint: Use replicas in all regions with eventual consistency [OK]

Common Mistakes:

• Expecting strong consistency across regions
• Using single region causing high latency
• Skipping regions to save cost but hurting users