A company wants to migrate its MySQL database from on premises to AWS. The company recently experienced a database outage that significantly impacted the business. To ensure this does not happen again, the company wants a reliable database solution on AWS that minimizes data loss and stores every transaction on at least two nodes.
Which solution meets these requirements?
To ensure a reliable database solution on AWS that minimizes data loss and stores every transaction on at least two nodes, the best approach is to create an Amazon RDS MySQL DB instance with Multi-AZ functionality enabled. This configuration ensures that the primary database instance has a standby replica in a different Availability Zone, and the data is synchronously replicated between them. This setup enhances high availability and data durability, significantly decreasing the risk of data loss. Other options involve asynchronous replication or unnecessary complexity and do not fully meet the requirements for synchronous replication across multiple nodes.
Amazon RDS MySQL DB instance with Multi-AZ functionality enabled to synchronously replicate the data Standby DB in Multi-AZ- synchronous replication Read Replica always asynchronous. so option C is ignored.
RDS Multi-AZ = Synchronous = Disaster Recovery (DR) Read Replica = Asynchronous = High Availability
B is correct but the explanation is flawed ;) RDS Multi-AZ = Synchronous = High Availability Read Replica = Asynchronous = Disaster Recovery (DR)
Option A is incorrect because Amazon RDS does not support synchronous replication to three nodes in three Availability Zones. Option C is incorrect because while you can create a read replica in a separate AWS Region1, the replication from the primary DB instance to the read replica is asynchronous, not synchronous.
I curios to know why A isn't right. Is it just that it would take more effort?
How would you implement A?
Multi-AZ will give at least two nodes as required by the question. The answer is B. Amazon RDS provides high availability and failover support for DB instances using Multi-AZ deployments with a single standby DB instance. https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.MultiAZSingleStandby.html
B. Create an Amazon RDS MySQL DB instance with Multi-AZ functionality enabled to synchronously replicate the data. Enabling Multi-AZ functionality in Amazon RDS ensures synchronous replication of data to a standby replica in a different Availability Zone. This provides high availability and minimizes data loss in the event of a database outage. A. Creating an Amazon RDS DB instance with synchronous replication to three nodes in three Availability Zones would provide even higher availability but is not necessary for the stated requirements. C. Creating a read replica in a separate AWS Region would provide disaster recovery capabilities but does not ensure synchronous replication or meet the requirement of storing every transaction on at least two nodes. D. Using an EC2 instance with a MySQL engine and triggering an AWS Lambda function for replication introduces unnecessary complexity and is not the most suitable solution for ensuring reliable and synchronous replication.
B since all other answers r wrong
Option A is the correct answer in this scenario because it meets the requirements specified in the question. It creates an Amazon RDS DB instance with synchronous replication to three nodes in three Availability Zones, which will provide high availability and durability for the database, ensuring that the data is stored on multiple nodes and automatically replicated across Availability Zones. Option B is not a correct answer because it creates an Amazon RDS MySQL DB instance with Multi-AZ functionality enabled, which only provides failover capabilities. It does not enable synchronous replication to multiple nodes, which is required in this scenario.
I would go with Option B since it meets the company's requirements and is the most suitable solution. By creating an Amazon RDS MySQL DB instance with Multi-AZ functionality enabled, the solutions architect will ensure that data is automatically synchronously replicated across multiple AZs within the same Region. This provides high availability and data durability, minimizing the risk of data loss and ensuring that every transaction is stored on at least two nodes.
Option B is not incorrect: "The primary DB instance is synchronously replicated across Availability Zones to a standby replica to provide data redundancy and minimize latency spikes during system backups" from https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.MultiAZSingleStandby.html
Answer is B Find the below URL for the perfect explanation for the differences between: - Multi-AZ DB - Multi-Region DB - Read replicas DB https://aws.amazon.com/rds/features/read-replicas/
Multi AZ for availability
B Since read replica is async.
Multi AZ is not as protected as Multi-Region Read Replica.
But is IS protected. Read replica is asynchronous, fails to meet the "store EVERY transaction on at least two nodes" requirement.
B is correct C requires more wokr.
Option B
Option B
Maybe C since Amazon RDC now supports cross region read replica https://aws.amazon.com/about-aws/whats-new/2022/11/amazon-rds-sql-server-cross-region-read-replica/
B is correct