Learn how to use AWS Elastic Disaster Recovery and Amazon FSx for Windows File Server to replicate on-premises servers to AWS and meet RTO and RPO requirements cost-effectively.
Table of Contents
Question
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 fallback 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 tailback, 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.
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
Option D is the most cost-effective solution because it allows for native failover and fallback capabilities while minimizing the need for additional infrastructure and data transfer costs. AWS Elastic Disaster Recovery (AWS DRT) simplifies and accelerates disaster recovery by automating the failover and failback of on-premises servers to AWS. AWS DRT supports Windows-based servers, and it can replicate data to an Amazon FSx for Windows File Server file system by using AWS DataSync. This ensures that the common share that all the servers mount is replicated and available in AWS.
During a disaster, AWS DRT can be used to fail over the on-premises servers to AWS, and during failback, it can be used to fail back to new or existing servers. This ensures that the RTO of 15 minutes and RPO of 5 minutes are met.
Options A and C are not the most cost-effective solutions because they require additional infrastructure and data transfer costs. Option A requires daily backups and recovery from backups, which can be time-consuming and may not meet the RTO and RPO requirements. Option C requires setting up a multi-site active-active environment, which can be complex and expensive.
Option B is not the most cost-effective solution because it requires creating CloudFormation templates and using AWS CodePipeline to deploy the templates. This can be complex and time-consuming, and it may not meet the RTO and RPO requirements.
Amazon AWS Certified Solutions Architect – Professional SAP-C02 certification exam practice question and answer (Q&A) dump with detail explanation and reference available free, helpful to pass the Amazon AWS Certified Solutions Architect – Professional SAP-C02 exam and earn Amazon AWS Certified Solutions Architect – Professional SAP-C02 certification.