Answer-first summary for fast verification
Answer: Convert the application to use Amazon DynamoDB. Use a global table for the center reservation table. Use the correct Regional endpoint in each Regional deployment.
## Explanation **Correct Answer: A** **Why Option A is correct:** 1. **Amazon DynamoDB Global Tables** provide a fully managed, multi-Region, multi-master database solution that automatically replicates data across multiple AWS Regions. 2. **Low latency (<1 second requirement)**: DynamoDB Global Tables provide single-digit millisecond latency for reads and writes, easily meeting the <1 second requirement for updates. 3. **Global consistency**: DynamoDB Global Tables offer eventual consistency across regions, which is suitable for the travel ticketing application's needs. 4. **Regional endpoints**: Each regional deployment can use the local DynamoDB endpoint for low-latency access. 5. **Single logical database**: Despite being distributed across regions, it appears as a single database to the application. **Why other options are incorrect:** **Option B (Aurora MySQL with Read Replicas):** - Aurora Read Replicas are read-only copies. Updates must go to the primary instance, which would create high latency for global users. - Cross-region replication for Aurora has higher latency than DynamoDB Global Tables. - Does not meet the <1 second latency requirement for updates from distant regions. **Option C (RDS MySQL with read replicas):** - Similar issues as Option B - read replicas are read-only. - Cross-region replication for RDS has even higher latency than Aurora. - Updates must go to the primary region, causing high latency for global users. **Option D (Aurora Serverless with Lambda synchronization):** - This creates a complex, custom synchronization solution that is error-prone. - Eventual consistency issues and potential data conflicts. - Higher operational overhead compared to managed DynamoDB Global Tables. - Latency for synchronization would likely exceed 1 second. **Key AWS Services Concepts:** - **DynamoDB Global Tables**: Automatically replicate data across multiple AWS Regions with low latency. - **Multi-Region Architecture**: Allows global applications to serve users with low latency while maintaining data consistency. - **Latency Requirements**: For global applications, choosing the right database technology is critical to meet latency SLAs. This solution provides the best balance of low latency, global consistency, and operational simplicity for the travel ticketing application.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
A company has a web application for travel ticketing. The application is based on a database that runs in a single data center in North America. The company wants to expand the application to serve a global user base. The company needs to deploy the application to multiple AWS Regions. Average latency must be less than 1 second on updates to the reservation database.
The company wants to have separate deployments of its web platform across multiple Regions. However, the company must maintain a single primary reservation database that is globally consistent.
Which solution should a solutions architect recommend to meet these requirements?
A
Convert the application to use Amazon DynamoDB. Use a global table for the center reservation table. Use the correct Regional endpoint in each Regional deployment.
B
Migrate the database to an Amazon Aurora MySQL database. Deploy Aurora Read Replicas in each Region. Use the correct Regional endpoint in each Regional deployment for access to the database.
C
Migrate the database to an Amazon RDS for MySQL database. Deploy MySQL read replicas in each Region. Use the correct Regional endpoint in each Regional deployment for access to the database.
D
Migrate the application to an Amazon Aurora Serverless database. Deploy instances of the database to each Region. Use the correct Regional endpoint in each Regional deployment to access the database. Use AWS Lambda functions to process event streams in each Region to synchronize the databases.