Memory hook: Certified VM, low latency, reproducible build.
Must remember
- Select SAP-certified VM families/sizes and supported OS images. Use Marketplace images or controlled custom images, then configure required extensions and SAP monitoring integration.
- Bicep/ARM templates and the SAP Deployment Automation Framework make infrastructure repeatable. Azure Center for SAP solutions provides supported discovery/deployment and management capabilities; match the tool to the supported scenario.
- Separate application, database and management traffic with intentional subnets, NSGs and route control. Keep administrative paths private or tightly restricted and integrate DNS with existing SAP dependencies.
- Accelerated Networking reduces supported VM network overhead. Proximity placement groups target physical proximity; availability zones target failure isolation. Balance latency against resiliency rather than maximizing one blindly.
- ExpressRoute supports private hybrid connectivity but needs redundant circuits/paths and appropriate encryption design. Private endpoints and service endpoints for Storage have different addressing and access semantics.
- Measure application-to-database latency and test failover paths. Region/zone placement, DNS, firewall rules and name resolution must work during normal operation and DR.
Choose under exam pressure
| Requirement | Choice and reason |
|---|---|
| SAP database latency is critical | Supported nearby placement and measured network performance, balanced against HA requirements. |
| Repeatable multi-system deployment | Reviewed infrastructure code and supported SAP automation tooling. |
Traps
- A proximity placement group is not an availability-zone guarantee.
- A private endpoint does not automatically fix DNS resolution from on-premises.
Active recall
1. Why use certified VM combinations?
SAP supportability and performance requirements constrain acceptable infrastructure.
2. What does Accelerated Networking improve?
Supported VM network latency/throughput by reducing virtualization overhead.
3. How do service and private endpoints differ?
Service endpoints secure access over the service endpoint model; private endpoints provide private IP interfaces for supported services.
4. Why automate deployment?
Repeatability, review, consistent configuration and easier recovery.
5. What must be measured across zones?
Actual workload latency and throughput as well as failure isolation.