Q26 — AWS SAA-C03 Ch.15

Question 26 of 100 | ← Chapter 15

Q1126. A company is launching a new gaming application. The company will use Amazon EC2 Auto Scaling groups to deploy the application. The application stores user data in a relational database.The company has office locations around the world that need to run analytics on the user data in the database.The company needs a cost-effective database solution that provides cross-Region disaster recovery with low-latency read performance across AWS Regions.Which solution will meet these requirements?

Correct Answer: C. Create an Amazon Aurora global database. Configure the primary cluster to be in the Region where the application is deployed. Configure the secondary Aurora replicas to be in the Regions where the company offices are located. Ensure the company offices read from the Aurora replicas.

Explanation

The best solution to meet the requirements for a cost-effective database solution that provides cross- Region disaster recovery with low-latency read performance across AWS Regions is:C. Create an Amazon Aurora global database. Configure the primary cluster to be in the Region where the application is deployed. Configure the secondary Aurora replicas to be in the Regions where the company offices are located. Ensure the company offices read from the Aurora replicas.Explanation:Amazon Aurora Global Database: This solution allows for low-latency reads from multiple Regions and offers cross-Region disaster recovery capabilities. It automatically replicates data with minimal latency to secondary Regions, ensuring that offices can access data quickly and reliably. Cost-effective and efficient: Aurora is designed for high availability and performance, making it suitable for applications with global reach.Why Other Options Are Not Suitable:A: While ElastiCache can provide fast in-memory data access, it is not designed for persistent storage of user data and does not offer cross-Region disaster recovery for a relational database.B: Amazon DynamoDB global tables are suitable for non-relational data and may not fit the requirement for a relational database solution.D: An RDS Multi-AZ deployment provides high availability within a single Region but does not support cross-Region replication or disaster recovery, which is a key requirement. Thus, option C is the most appropriate solution for the company's needs.To meet the requirements of a cost-effective database solution that provides cross-Region disaster recovery (DR) with low-latency read performance across AWS Regions for analytics, the solution must:Support multi-Region replication (for DR and low-latency reads). Provide read replicas in multiple Regions (for analytics close to office locations). Be cost-effective (avoiding over-provisioning or expensive NoSQL solutions if not needed). Support relational data (since the application stores user data in a relational database).Key Requirements:Relational Database: The solution must work with a relational database (not NoSQL like DynamoDB). Cross-Region DR: The database must replicate data across Regions for failover. Low-Latency Reads for Analytics: Offices worldwide should read from replicas in their Region. Cost-Effective: Avoids expensive solutions like global DynamoDB tables unless necessary.Option Analysis:Option A:Create an Amazon ElastiCache (Redis OSS) cluster in the Region where the application is deployed. Create read replicas in Regions where the company offices are located. Ensure the company offices read from the read replica instances.Why This Fails:ElastiCache (Redis) is a caching layer, not a primary database. It does not store persistent relational data (only caches it). Not suitable for analytics on user data (which requires direct database access).Option B:Create Amazon DynamoDB global tables. Deploy the tables to the Regions where the company offices are located and to the Region where the application is deployed. Ensure that each company office reads from the tables that are in the same Region as the office.Why This Fails:DynamoDB is NoSQL, not relational (violates the requirement for a relational database). While DynamoDB global tables support multi-Region replication, it is not the right fit if the application already uses a relational database.Not Cost-Effective for Relational Workloads: DynamoDB would require a complete rewrite of the application.Option C:Create an Amazon Aurora global database. Configure the primary cluster to be in the Region where the application is deployed. Configure the secondary Aurora replicas to be in the Regions where the company offices are located. Ensure the company offices read from the Aurora replicas.Why This Works:Amazon Aurora Global Database:Relational Database: Aurora is a managed MySQL/PostgreSQL-compatible database. Cross-Region DR: Supports one primary Region and up to five secondary Regions (for failover). Low-Latency Reads: Offices can read from local Aurora replicas (with <1-second replication lag). Cost-Effective: Cheaper than DynamoDB global tables for relational workloads. Best Fit: Meets all requirements (relational, multi-Region DR, low-latency reads).Option D:Create an Amazon RDS Multi-AZ DB cluster deployment in the Region where the application is deployed. Ensure the company offices read from read replica instances.Why This Fails:RDS Multi-AZ: Provides high availability within a single Region (not cross-Region DR). No Multi-Region Read Replicas: RDS read replicas can be deployed in the same Region but not across Regions (unless using Aurora Global Database).Does Not Meet Cross-Region Requirements: Fails to provide low-latency reads in other Regions.Best Choice: Option CAmazon Aurora Global Database provides:Relational Database Support (MySQL/PostgreSQL-compatible). Cross-Region Disaster Recovery (primary in one Region, secondaries in others).Low-Latency Reads (offices read from local replicas).Cost-Effective (compared to DynamoDB global tables for relational workloads).Final Answer:C. Create an Amazon Aurora global database. Configure the primary cluster to be in the Region where the application is deployed. Configure the secondary Aurora replicas to be in the Regions where the company offices are located. Ensure the company offices read from the Aurora replicas.Additional Notes:Aurora Global Database is ideal for multi-Region relational workloads requiring DR and low-latency reads. DynamoDB Global Tables would only be suitable if the application were already using NoSQL. RDS Multi-AZ is for same-Region high availability, not cross-Region DR.ElastiCache is for caching, not persistent data storage.