Q45 — AWS SAP-C02 Ch.2
Question 45 of 75 | ← Chapter 2
Q195. A company wants to use AWS for disaster recovery for an on-premises application. The company has hundreds of Windows-based servers that run the application. All the servers mount a common share. The company has an RTO of 15 minutes and an RPO of 5 minutes. The solution must support native failover and falback capabilities.Which solution will meet these requirements MOST cost-effectively?
- A. Create an AWS Storage Gateway File Gateway. Schedule daily Windows server backups. Save the data to Amazon S3. During a disaster, recover the on-premises servers from the backup. During failback, run the on-premises servers on Amazon EC2 instances
- B. Create a set of AWS CloudFormation templates to create infrastructure. Replicate all data to Amazon Elastic File System (Amazon EFS) by using AWS DataSync During a disaster, use AWS CodePipeline to deploy the templates to restore the on- premises servers. Fail back the data by using DataSync
- C. Create an AWS Cloud Development Kit (AWS CDK) pipeline to stand up a multi-site active-active environment on AWS. Replicate data into Amazon S3 by using the S3 sync command. During a disaster, swap DNS endpoints to point to AWS Fail back the data by using the S3 sync command
- D. Use AWS Elastic Disaster Recovery to replicate the on-premises servers. Replicate data to an Amazon FSx for Windows File Server file system by using AWS DataSync. Mount the file system to AWS servers. During a disaster, fail over the on: premises servers to AWS. Fail back to new or existing servers by using Elastic Disaster Recovery ✓
Correct Answer: D. Use AWS Elastic Disaster Recovery to replicate the on-premises servers. Replicate data to an Amazon FSx for Windows File Server file system by using AWS DataSync. Mount the file system to AWS servers. During a disaster, fail over the on: premises servers to AWS. Fail back to new or existing servers by using Elastic Disaster Recovery
Explanation
To meet the requirements of a cost-effective disaster recovery solution for the company's on-premises application with an RTO of 15 minutes and an RPO of 5 minutes, the following solution should be implemented: D. Use AWS Elastic Disaster Recovery to replicate the on-premises servers. Replicate data to an Amazon FSx for Windows File Server file system using AWS DataSync. Mount the file system to AWS servers. During a disaster, fail over the on-premises servers to AWS. Fail back to new or existing servers using Elastic Disaster Recovery. Explanation: Option D provides a comprehensive solution that meets the company's requirements in the most cost-effective manner: - Use AWS Elastic Disaster Recovery: This service enables replication of on-premises servers to AWS for disaster recovery purposes. It ensures that the replicated servers are continuously updated with the latest data changes, meeting the RPO of 5 minutes. - Replicate data to Amazon FSx for Windows File Server: AWS DataSync can be utilized to replicate the common share mounted by the Windows-based servers on-premises to an Amazon FSx for Windows File Server file system. This ensures that the data is available in AWS during a disaster. - Mount the file system to AWS servers: The replicated file system can be mounted to AWS servers, allowing the application to access the data in AWS during failover. - Failover and failback using Elastic Disaster Recovery: During a disaster, the on-premises servers can be failed over to AWS, enabling the application to continue running with minimal downtime and meeting the RTO of 15 minutes. In the event of failback, Elastic Disaster Recovery can be used to move the data back to new or existing on-premises servers. By leveraging AWS Elastic Disaster Recovery, AWS DataSync, and Amazon FSx for Windows File Server, the solution provides native failover and failback capabilities, meets the RTO and RPO requirements, and offers a cost-effective approach for disaster recovery. Therefore, option D is the most suitable and cost-effective solution for the company's disaster recovery needs.