You plan to deploy an SAP production landscape on Azure. You need to minimize latency between SAP HANA database servers and SAP NetWeaver servers. What should you implement?

Question

Options

• AAzure Private Link
• Ban Availability Set
• Ca proximity placement group
• Da virtual machine scale set

• A
  4% (2)
• C
  93% (42)
• D
  2% (1)

Explanation

A proximity placement group (PPG) logically groups Azure VMs to ensure they are physically located close together within the same datacenter, minimizing network latency - which is critical for the high-throughput, low-latency communication required between SAP HANA and SAP NetWeaver application servers.

Why the distractors are wrong:

• A (Azure Private Link): Provides private connectivity to Azure services over a private endpoint - it's about network security/isolation, not co-location or latency reduction between VMs.
• B (Availability Set): Spreads VMs across fault/update domains to maximize availability, which can actually place VMs further apart physically, potentially increasing latency.
• D (VM Scale Set): Used for auto-scaling instances of identical VMs for load handling - it has no mechanism for controlling physical placement or reducing inter-VM latency.

Memory tip: Think of PPG as "pinning" your VMs to the same rack neighborhood. When SAP HANA and NetWeaver need to "whisper" to each other constantly, you want them as physically close as possible - that's the PPG's job.

No community discussion yet for this question.