Exam AWS Certified SAP on AWS - Specialty PAS-C01 topic 1 question 36 discussion

apply QA on DR site will satisfy cost-optimized solution.

Its B !. CloudEndure Disaster Recovery continuously replicates your machines (including operating system, system state configuration, databases, applications, and files) into a low-cost staging area in your target AWS account and preferred Region. https://aws.amazon.com/blogs/awsforsap/sap-disaster-recovery-solution-using-cloudendure-part-1-failover/

Running a QA system in another region will implicate on NFS issues. Hence I think the best option is B.

"A" looks correct

A is the answer. It was a close call between A & B until you read the requirement for capacity reservation, which B only promises a smaller instance, and they could face capacity issues when the EC2 instance is scalled to the prod size one.

I think A is the only cost-effective option that offers guaranteed capacity reservation. CloudEndure would work but it doesn't solve the capacity reservation requirement as it uses a staging area and launch the instances in case of a disaster. What it there is no spare capacity in the DR region?

Only C provide guaranteed capacity reservation as required by the question. With option B, during DR you can try to launch instance an get an error that there is no capacity in the AZ or region of the desired instance type.

You can use CloudEndure Disaster Recovery to protect your most critical databases, including Oracle, MySQL, and Microsoft SQL Server, as well as enterprise applications such as SAP. For HANA DB, Async replication is the best option to achieve RTO and RPO of less than 30mins. So option A is correct.

Using a single EC2 instance in us-west-1 for both QA and production may not be ideal because it doesn't offer guaranteed capacity reservation for DR, which is one of the requirements. Shutting down QA to enable production may also lead to other issues and is not optimal.

A: This approach provides a cost-effective solution by utilizing a single EC2 instance to serve dual purposes - supporting both QA and production. By using SAP HANA system replication with preload off, it ensures a constant replication of data from the primary database to the secondary one. In case of a disaster recovery scenario, the QA SAP HANA instance can be shut down and production services can be restarted at the secondary site. This meets the RPO and RTO requirements of less than 30 minutes.

voting C

CloudEndure Disaster Recovery continuously replicates your machines (including operating system, system state configuration, databases, applications, and files) into a low-cost staging area in your target AWS account and preferred Region. In the case of a disaster, you can instruct CloudEndure Disaster Recovery to automatically launch thousands of your machines in their fully provisioned state in minutes. By replicating your machines into a low-cost staging area while still being able to launch fully provisioned machines within minutes, CloudEndure Disaster Recovery can significantly reduce the cost of your disaster recovery infrastructure. The two key concepts when it comes to DR planning are Recovery Time Objective (RTO) and Recovery Point Objective (RPO). RTO is the maximum period you want your systems to be unavailable due to an outage. RPO refers to the point of data processing you wish to recover to if there is a disaster. The following diagram illustrates the correlation of RTO and RPO:

B is the answer

I think A