A company is hosting its SAP workloads on AWS. An SAP solutions architect is designing high availability architecture for the company's production SAP S/4HANA and SAP BW/4HANA workloads. These workloa

Deploying ASCS and ERS cluster nodes in different subnets within the same Availability Zone provides only subnet-level separation and does not protect against an AZ-level failure, leaving both cluster nodes unavailable simultaneously.

Like option A, placing both cluster nodes in the same AZ with only subnet separation is insufficient for true high availability because a single AZ outage would take down the entire ASCS/ERS failover cluster.

Deploying ASCS and ERS cluster nodes in different subnets across two Availability Zones ensures that a failure in one AZ does not bring down both cluster nodes simultaneously, satisfying SAP's failover cluster HA requirements. Combined with cross-AZ deployment of PAS and AAS as redundant application servers and a primary-secondary DB pair across AZs, this architecture provides comprehensive HA for both the SAP application layer and the database layer.

Option D likely deploys the PAS, AAS, or DB tier in a configuration that does not fully satisfy all three stated HA requirements - redundant app servers, cross-AZ ASCS/ERS cluster, and DB primary-secondary HA - as completely as option C.