Q75 — AWS SAP-C02 Ch.1

Question 75 of 75 | ← Chapter 1

Q150. A company wants to use AWS to create a business continuity solution in case the company's main on- premises application fails. The application runs on physical servers that also run other applications. The on- premises 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 failback 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

Correct Answer: 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 failback from the most recent point in time

Explanation

The solution that will achieve the company's goal with the LEAST operational overhead is: 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 failback from the most recent point in time. Here's the rationale behind this choice: Option B suggests installing the AWS Replication Agent on the source servers, including the MySQL servers, and initializing AWS Elastic Disaster Recovery in the target AWS Region. This approach utilizes AWS services to replicate the on-premises application and provide a business continuity solution. The replication agent will replicate the data and configurations to the target AWS region, ensuring that the application is available in case of a failure event. Frequent failover and failback can be performed from the most recent point in time, minimizing the impact of a failure event with minimal operational overhead. The other options may involve higher operational overhead or may not be as suitable for the given scenario: Option A suggests installing the AWS Replication Agent on the source servers and setting up replication for all servers. While this approach can provide a business continuity solution, it may require regular manual interventions and cutovers to test instances, leading to higher operational overhead. Option C involves creating AWS Database Migration Service (AWS DMS) replication servers, setting up an Amazon Aurora MySQL DB cluster, and using AWS Schema Conversion Tool (AWS SCT) for data synchronization. This solution may require additional configuration and monitoring for maintaining data synchronization, resulting in higher operational overhead. Option D proposes deploying an AWS Storage Gateway Volume Gateway on premises and taking regular snapshots. While this approach can provide a backup solution, it may not offer real-time replication and may require additional steps for restoring the volumes and mounting them on EC2 instances in the case of a failure event. Therefore, the solution with the least operational overhead for achieving the company's goal is: 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 failback from the most recent point in time.