
Answer-first summary for fast verification
Answer: Install the AWS Replication Agent on the source servers, including the MySQL servers. Initialize AWS Elastic Disaster Recovery in the target AWS Region. Define the launch settings. Frequently perform failover and fallback from the most recent point in time.
The solution in answer B leverages AWS Elastic Disaster Recovery (AWS DRS), which provides fully automated failover and fallback capabilities with minimal operational overhead. Here's a detailed explanation: 1. **AWS Replication Agent:** Installing the AWS Replication Agent on the source servers, including the MySQL servers, ensures continuous data replication from the on-premises servers to AWS. This agent simplifies the replication process, reduces the need for extensive manual configurations, and ensures that the data is kept up-to-date in the target AWS Region. 2. **Initialize AWS Elastic Disaster Recovery:** AWS DRS simplifies disaster recovery by automating the entire replication, failover, and fallback process. It continuously replicates applications and databases, ensuring minimal downtime and data loss. Therefore, in the event of a failure, the company can quickly switch over to AWS with minimal disruption. 3. **Define Launch Settings:** By defining the launch settings, the company can preconfigure how the instances will be launched during a failover. This preconfiguration further reduces operational complexity and overhead by automating the launch process. 4. **Perform Failover and Fallback:** Regularly performing failover and fallback operations from the most recent point in time ensures that the disaster recovery plan is always up-to-date and that the team is prepared for real-world failover events. This approach also helps to validate that the replication is functioning correctly and that the recovery process can be executed without issues. Overall, this solution minimizes operational overhead by providing an automated and managed service that handles the complexities of disaster recovery, ensuring that the company's critical applications can be restored quickly and efficiently with minimal manual intervention.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
A company wants to use AWS to create a business continuity solution in case the company's main onpremises application fails. The application runs on physical servers that also run other applications. The onpremises application that the company is planning to migrate uses a MySQL database as a data store. All the company's on-premises applications use operating systems that are compatible with Amazon EC2. Which solution will achieve the company's goal with the LEAST operational overhead?
A
Install the AWS Replication Agent on the source servers, including the MySQL servers. Set up replication for all servers. Launch test instances for regular drills. Cut over to the test instances to fail over the workload in the case of a failure event.
B
Install the AWS Replication Agent on the source servers, including the MySQL servers. Initialize AWS Elastic Disaster Recovery in the target AWS Region. Define the launch settings. Frequently perform failover and fallback from the most recent point in time.
C
Create AWS Database Migration Service (AWS DMS) replication servers and a target Amazon Aurora MySQL DB cluster to host the database. Create a DMS replication task to copy the existing data to the target DB cluster. Create a local AWS Schema Conversion Tool (AWS SCT) change data capture (CDC) task to keep the data synchronized. Install the rest of the software on EC2 instances by starting with a compatible base AMI.
D
Deploy an AWS Storage Gateway Volume Gateway on premises. Mount volumes on all on-premises servers. Install the application and the MySQL database on the new volumes. Take regular snapshots. Install all the software on EC2 Instances by starting with a compatible base AMI. Launch a Volume Gateway on an EC2 instance. Restore the volumes from the latest snapshot. Mount the new volumes on the EC2 instances in the case of a failure event.