A company hosts an SAP HANA database on an Amazon EC2 instance in the us-east-1 Region. The company needs to implement a disaster recovery (DR) site in the us-west-1 Region. The company needs a cost-o

Question

Options

• ADeploy a single EC2 instance to support the secondary database in us-west-1 with additional
• BDeploy a secondary staging server on an EC2 instance in us-west-1. Use CloudEndure Disaster
• CSet up the primary SAP HANA database in us-east-1 to constantly replicate the data to a
• DCreate an SAP HANA database AMI by using Amazon Elastic Block Store (Amazon EBS)

• A
  5% (1)
• B
  82% (18)
• C
  5% (1)
• D
  9% (2)

Explanation

The requirements are cost optimization, guaranteed capacity reservation, RPO < 30 minutes, and RTO < 30 minutes. Answer B using CloudEndure Disaster Recovery (now AWS Elastic Disaster Recovery) meets all four. It maintains a lightweight staging server in us-west-1 at low cost, uses continuous block-level replication to achieve sub-second RPO (well under 30 minutes), and performs fast machine conversion and launch to meet RTO under 30 minutes. Critically, it supports capacity reservation for the recovery instances, satisfying that requirement. Answer A lacks specifics on how capacity reservation and sub-30-minute RTO are guaranteed. Answer C describes active-active or synchronous HANA System Replication which is more expensive and typically used for higher availability tiers rather than cost-optimized DR. Answer D relies on periodic AMI snapshots, which would not guarantee RPO under 30 minutes since snapshots are not continuous, and cold-start from an AMI typically exceeds a 30-minute RTO for SAP HANA.

No community discussion yet for this question.