A team operates legacy applications on physical servers in a colocation facility and on virtual machines in another cloud. Leadership wants a disaster recovery plan into AWS with a recovery point objective measured in seconds and a recovery time objective of minutes, using continuous block-level replication into low-cost staging storage, then launching full EC2 instances only when a recovery is declared. Which AWS service is purpose-built for this requirement?
- AAWS Backup with a backup plan that snapshots the servers every few minutes and copies the recovery points into AWS, then restores them to EC2 when a recovery is declared by the operations team.
- BAWS Application Migration Service configured for ongoing replication, because it keeps source servers synchronised in AWS and can cut them over, serving as the standing disaster recovery target.
- CAWS Elastic Disaster Recovery, which continuously replicates the source servers block by block into low-cost staging on AWS and converts them into fully provisioned EC2 instances during a drill or recovery. Correct
- DAWS Storage Gateway in volume mode to replicate the on-premises disks into Amazon S3, then build EC2 instances from those volumes when the primary site is lost during a regional outage.
Why A is wrong: AWS Backup protects supported AWS resources on a schedule and cannot continuously replicate arbitrary physical and third-party-cloud servers, so it cannot reach a seconds-level RPO for these sources.
Why B is wrong: Application Migration Service is built for one-time lift-and-shift migration and final cutover, not for repeated failover, drills and failback, so it is the wrong tool for an ongoing disaster recovery posture even though it also replicates servers.
Why C is correct: AWS Elastic Disaster Recovery performs continuous block-level replication into lightweight staging and launches full EC2 instances only on failover or drill, delivering seconds of RPO and minutes of RTO for servers from on premises or another cloud.
Why D is wrong: Storage Gateway presents cached or stored volumes backed by S3 for hybrid storage, not orchestrated server-level disaster recovery, so it provides neither the continuous instance replication nor the automated launch that the requirement needs.