You have an SAP landscape on Azure that contains the virtual machines shown in the following table. You need to ensure that the Application Server role is available if a single Azure datacenter…

Question

Options

• AAzure Private Link
• BAzure Load Balancer Standard
• Ca local network gateway
• DAzure Application Gateway v1

• A
  6% (1)
• B
  78% (14)
• C
  6% (1)
• D
  11% (2)

Explanation

Azure Load Balancer Standard supports zone-redundant configurations, meaning it can distribute traffic across Virtual Machines in multiple Availability Zones (separate physical datacenters within a region) - this is precisely how you keep the SAP Application Server role available if a single Azure datacenter fails. SAP on Azure high-availability architectures specifically require Standard Load Balancer to front ASCS/ERS and Application Server clusters because it supports floating IP (Direct Server Return) needed by SAP cluster configurations.

Why the distractors are wrong:

• A. Azure Private Link - enables private connectivity to Azure services over a private endpoint; it's a network isolation/security tool, not a high-availability mechanism.
• C. Local network gateway - represents your on-premises VPN device in a hybrid connection; it has nothing to do with inter-datacenter failover.
• D. Azure Application Gateway v1 - is a web application firewall/HTTP load balancer operating at Layer 7, and the v1 SKU does not support Availability Zones; it's also not suited for SAP's TCP-based cluster traffic.

Memory tip: Think "Standard = Zone-aware." The Standard SKU of Azure Load Balancer is the only one that supports Availability Zones and is the mandatory choice for any SAP HA scenario on Azure - if you see SAP + datacenter failure + HA, the answer almost always involves Load Balancer Standard.

No community discussion yet for this question.