What's changed: Created AZ-120 Chapter 2 (Domain 2: compute (SAP-certified VMs, VM extension for SAP solutions, Marketplace/custom images, Bicep/ARM IaC, SDAF, Azure Center for SAP solutions); networking (VNet, Accelerated Networking, proximity placement group PPG, SAP latency requirements, ExpressRoute, private/service endpoints, Azure DNS); storage (disk types, striping vs simple, Write Accelerator for HANA log, Azure NetApp Files, Azure Files, Azure Disk Encryption)).
2.2Networking
Understand VNets/subnets, Accelerated Networking, proximity placement groups, designing for SAP latency requirements, Private/Service Endpoints, Azure DNS, and ExpressRoute for hybrid connectivity.
SAP app and DB tiers require low-latency, high-throughput communication. Along with VNet design, SAP-specific network optimizations determine performance.
2.2.1Low-latency networking (acceleration, proximity)
Accelerated Networking uses SR-IOV so the VM NIC bypasses the host, lowering latency and raising throughput (recommended for SAP). A proximity placement group (PPG) places app-server and HANA-DB VMs physically close to minimize inter-VM latency (mind placement constraints when combined with availability zones). Designing to meet SAP latency requirements (app↔DB round-trip) is key.
2.2.2Connectivity, endpoints, and name resolution
Hybrid connectivity to on-prem and SAP uses ExpressRoute for dedicated low-latency, bandwidth, and SLA. Closed access to Azure Storage etc. uses private endpoints (private IP; private DNS zone for resolution) or service endpoints (optimized VNet-to-service path). Design name resolution with Azure DNS / private DNS zones to ensure SAP host-name resolution. Segment with network flow control (NSGs/UDRs/firewall).
Cues: "accelerate the VM NIC for latency/throughput" = Accelerated Networking. "place app and DB physically close to minimize inter-VM latency" = proximity placement group (PPG). "low-latency dedicated link to on-prem" = ExpressRoute. "closed/private IP to storage" = private endpoint. Name resolution = Azure DNS/private DNS zones.
Watch the mix-ups: (1) Accelerated Networking (NIC acceleration) vs load balancer (distribution). (2) PPG (minimize latency) and availability zones (fault tolerance) differ; mind placement/capacity constraints when combined. (3) Private endpoint (private IP) vs service endpoint (path optimization). (4) ExpressRoute is lower-latency/higher-SLA than VPN but costlier to build.
2.2.3Section summary
- Accelerated Networking accelerates the NIC; PPG minimizes app↔DB inter-VM latency
- On-prem connectivity = ExpressRoute; closed storage = private endpoints; name resolution = Azure DNS
- Network design meeting SAP latency requirements (app↔DB) is key to performance
Sign in to track progress — Log in.
Quick check
(just a quick review)Q1. You want to physically minimize inter-VM latency between SAP app servers and the HANA DB. Best?
Q2. You want to accelerate the SAP VM NIC to lower latency and raise throughput. Best?
Q3. You want a dedicated low-latency, high-bandwidth, SLA-backed link between on-prem and SAP on Azure. Best?
Q4. You want closed access from SAP VMs to Azure Storage via a private IP. Best?
Q5. Which correctly distinguishes Accelerated Networking from a proximity placement group?
Keep track of your progress
The full study guide is free to read. Sign up free to practice with the question bank, track what you have read, review your mistakes, and highlight passages.