You are planning high availability for an SAP environment on Azure. The SAP environment will use datacenters in to different zones. Testing shows…

The scenario requires a high-availability solution that can withstand the failure of an entire Azure datacenter within a zone. Azure Availability Zones are the appropriate construct for this, as they are physically separate locations within an Azure region. Deploying virtual machines across two zones meets this requirement.

An active/passive cluster configuration is a standard and cost-effective high-availability pattern for critical single-point-of-failure SAP components like the ASCS/ERS instance and the database. This setup provides the required automatic failover using clustering software (e.g., Pacemaker) and aligns with the goal of minimizing costs, as the passive node is on standby and may not require the same resource consumption or licensing as the active node until a failover occurs.

B. Azure Site Recovery: This is a disaster recovery (DR) service, not a high-availability (HA) solution. It has a higher Recovery Time Objective (RTO) and typically involves manual failover, which does not meet the automatic failover requirement.

C. Azure Availability Sets with active/passive clustering: Azure Availability Sets protect against hardware failures within a single datacenter (rack or host failure), not the failure of an entire datacenter, which is the scenario's core requirement.

D. Azure Availability Sets with active/active clustering: This option is incorrect for the same reason as C. It uses Azure Availability Sets, which do not provide protection across different datacenters or zones.

1. Microsoft Learn | SAP workload configurations with Azure Availability Zones: "For high availability

you can deploy SAP workloads across Azure Availability Zones. An Azure Availability Zone is a physically separate location within an Azure region... Deploying your VMs running the SAP application layer across two Availability Zones

you can protect your SAP application layer from a datacenter failure." This document explicitly recommends Availability Zones for datacenter-level fault tolerance. It also details active/passive cluster configurations for ASCS/SCS and DBMS layers across zones.

2. Microsoft Learn | High-availability architecture and scenarios for SAP NetWeaver: Under the section "High availability for SAP NetWeaver on Azure IaaS

" the document describes clustering the SAP ASCS/SCS instance. The typical configuration across Availability Zones is an active/passive setup managed by a cluster manager to provide automatic failover.

3. Microsoft Learn | Azure Virtual Machines high availability for SAP NetWeaver: This document contrasts Availability Sets and Availability Zones. In the "Availability Zones" section

it states

"Azure Availability Zones are physically separate locations within each Azure region that are tolerant to local failures... To achieve SAP system high availability across Zones

you can deploy the active and passive systems in two different zones." This confirms the use of zones for an active/passive HA design.