An ecommerce company runs an application that uses an Amazon DynamoDB table in a single AWS Region. The company wants to deploy the application to a…

Amazon DynamoDB global tables provide a fully managed, multi-Region, and multi-active database solution. By converting the existing single-Region table into a global table and adding a replica in the new Region, the company can achieve low-latency reads and writes for users in both locations. This is the most operationally efficient method because DynamoDB handles the complex work of replicating data between Regions automatically, ensuring that changes made to any replica table are propagated to all other replicas, typically within a second. This native feature eliminates the need to build and maintain a custom replication solution.

A: A Global Secondary Index (GSI) is for creating an alternate query pattern, not for multi-Region replication. The steps described for converting the table are also incorrect and overly complex.

B: This describes a custom, self-managed replication solution using DynamoDB Streams and Kinesis. It introduces significant operational overhead for development, deployment, and maintenance compared to the managed global tables feature.

D: Similar to option B, this is a custom replication solution using DynamoDB Streams and AWS Lambda. While serverless, it still requires writing and maintaining custom code, which is less operationally efficient than the native global tables feature.

1. AWS DynamoDB Developer Guide

"Global Tables: How they work": "Amazon DynamoDB global tables provide a fully managed solution for deploying a multi-region

multi-active database... When you create a global table

you specify the AWS Regions where you want the table to be available. DynamoDB performs all of the necessary tasks to create identical tables in these Regions and propagate ongoing data changes to all of them."

2. AWS DynamoDB Developer Guide

"Creating a global table": This section details the process for creating a global table from an existing table. It states

"You can create a global table from an existing DynamoDB table. The process involves enabling DynamoDB Streams on the source table and then adding replicas in other AWS Regions." This confirms the simplicity and managed nature of the process described in option C.

3. AWS Whitepaper

"Build a multi-Region

active-active architecture with Amazon DynamoDB": This paper explicitly states

"DynamoDB global tables eliminate the difficult work of replicating data between Regions and resolving update conflicts

enabling you to focus on your application’s business logic." This highlights the operational efficiency of the service over custom solutions.

4. AWS DynamoDB Developer Guide

"Change data capture for DynamoDB Streams": This page describes how DynamoDB Streams can be used with AWS Lambda to create cross-Region replication solutions

but it presents this as a use case that requires custom implementation

implicitly making it less operationally efficient than the managed global tables service.