Ultimate access to all questions.
A company has developed a Windows Server-based application running on VMware vSphere VMs hosted on-premises. The application data, stored in a proprietary format, is accessed exclusively through the application. The company manually manages server and application provisioning. In its disaster recovery plan, the company seeks the capability to temporarily migrate the application to AWS in the event of on-premises infrastructure failure, with the intention to revert to on-premises hosting post-recovery. The recovery point objective (RPO) is set at 5 minutes. What solution offers the least operational burden to meet these disaster recovery requirements?
A
Utilize AWS DataSync to replicate data to Amazon EBS volumes. In the event of on-premises unavailability, deploy Amazon EC2 instances using AWS CloudFormation templates and attach the EBS volumes.
B
Employ AWS Elastic Disaster Recovery to replicate data to Amazon EC2 instances with attached EBS volumes. During on-premises outages, leverage Elastic Disaster Recovery to initiate EC2 instances using the replicated volumes.
C
Deploy an AWS Storage Gateway file gateway to replicate data to an Amazon S3 bucket. In case of on-premises failure, restore data to Amazon EBS volumes using AWS Backup and start Amazon EC2 instances from these volumes.
D
Set up an Amazon FSx for Windows File Server file system on AWS to replicate data. Upon on-premises infrastructure failure, provision Amazon EC2 instances with AWS CloudFormation templates and mount the Amazon FSx file shares using AWS::CloudFormation::Init commands.