An SAP system on AWS needs to be highly available across multiple Availability Zones (AZs). The SAP Central Services (ASCS) and the database are both critical. Which architecture should be used?
This provides HA for both ASCS and database across AZs.
Why this answer
SAP ASCS requires a cluster (e.g., Pacemaker with SBD fencing) across two AZs to provide failover for the central services, while HANA System Replication (HSR) synchronously replicates the database to a secondary AZ for automatic failover. This dual-cluster architecture ensures both critical components remain highly available, meeting SAP's certified HA patterns on AWS.
Exam trap
The trap here is that candidates often confuse AWS-managed services like RDS Multi-AZ with SAP-certified HA solutions, failing to recognize that SAP HANA requires native replication and that ASCS must be clustered, not simply load-balanced.
How to eliminate wrong answers
Option A is wrong because an Application Load Balancer operates at Layer 7 and cannot manage SAP ASCS or HANA database failover; it is designed for HTTP/HTTPS traffic distribution, not SAP-specific cluster heartbeats or replication. Option C is wrong because placing all components in a single AZ creates a single point of failure; AWS best practices require multi-AZ deployment to survive AZ outages, and cross-AZ latency is negligible (typically <1 ms) for SAP workloads. Option D is wrong because Amazon RDS Multi-AZ does not support SAP HANA or SAP-certified databases; SAP requires native HANA System Replication or a certified DBMS, and a single ASCS instance lacks the clustering needed for high availability.