DBS-C01 · Question #312
A financial services company is running a MySQL database on premises. The database holds details about all customer interactions and the financial advice that the company provided. The write traffic…
The correct answer is B. Deploy an Amazon Aurora MySQL DB cluster. Select a Cross-AZ configuration with an Aurora. For an on-premises MySQL database migrating to AWS with consistent writes and variable, high read traffic requiring no downtime during scaling, an Amazon Aurora MySQL DB cluster with Aurora Replicas is the most operationally efficient solution.
Question
A financial services company is running a MySQL database on premises. The database holds details about all customer interactions and the financial advice that the company provided. The write traffic to the database is well known and consistent. However, the read traffic is subject to significant and sudden increases for end-of-month reporting. The database is becoming overloaded during these periods of heavy read activity. The company decides to move the database to AWS. A database specialist needs to propose a solution in the AWS Cloud that will scale to meet the variable read traffic requirements without affecting the performance of write traffic. Scaling events must not require any downtime. What is the MOST operationally efficient solution that meets these requirements?
Options
- ADeploy a MySQL primary node on Amazon EC2 in one Availability Zone. Deploy a MySQL read
- BDeploy an Amazon Aurora MySQL DB cluster. Select a Cross-AZ configuration with an Aurora
- CDeploy an Amazon RDS for MySQL Multi-AZ database as a write database. Deploy a second
- DDeploy an Amazon DynamoDB database. Create a DynamoDB auto scaling policy to adjust the
How the community answered
(33 responses)- A9% (3)
- B64% (21)
- C6% (2)
- D21% (7)
Why each option
For an on-premises MySQL database migrating to AWS with consistent writes and variable, high read traffic requiring no downtime during scaling, an Amazon Aurora MySQL DB cluster with Aurora Replicas is the most operationally efficient solution.
Deploying MySQL on Amazon EC2 requires manual setup for replication and scaling read replicas, which is less operationally efficient than Aurora and does not offer the same seamless scaling capabilities for read traffic without downtime.
An Amazon Aurora MySQL DB cluster automatically separates storage from compute, allowing for very fast scaling of Aurora Replicas to handle sudden increases in read traffic without impacting the primary instance's write performance or incurring downtime. Aurora Replicas share the same underlying storage volume as the primary instance, ensuring low replication lag and efficient read scaling across Availability Zones.
While Amazon RDS for MySQL Multi-AZ provides high availability, its read replicas typically require manual scaling, and promoting a read replica to a primary involves downtime, making it less operationally efficient for seamless read scaling without downtime.
Amazon DynamoDB is a NoSQL database, and migrating a relational MySQL database to DynamoDB would involve significant schema redesign, application refactoring, and data migration efforts, making it not the MOST operationally efficient solution for a lift-and-shift scenario with minimal changes.
Concept tested: Aurora read scaling and high availability
Source: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.Replication.ReadReplicas.html
Topics
Community Discussion
No community discussion yet for this question.