What's changed: Created AZ-120 Chapter 4 (Domain 4 first-half: performance/cost optimization (Azure Advisor recommendations, VM resizing, Reserved Instances vs Savings Plans, storage cost, archiving); network and app/DB optimization (Azure Network Watcher for latency/throughput, proximity/Accelerated Networking/VM size, app-server horizontal/vertical scaling, DB tuning, continuous-improvement cycle)).
4.2Network and app/DB optimization
Understand analyzing/optimizing network performance, identifying latency/throughput bottlenecks, and continuously tuning/scaling SAP application servers and databases.
SAP performance depends on the app-tier↔DB-tier network and each tier’s resources. Continuously measure, identify bottlenecks, and optimize.
4.2.1Network performance optimization
Measure network latency and throughput (visualize paths/latency with Azure Network Watcher / Connection Monitor) and identify bottlenecks against SAP requirements. Remedies include enabling Accelerated Networking, using a proximity placement group to co-locate app↔DB, adjusting to an appropriate VM size (NIC bandwidth scales with VM size), and revisiting ExpressRoute bandwidth. For "high app↔DB latency," revisit proximity/Accelerated Networking/VM size.
4.2.2App server and DB optimization
Scale SAP application servers horizontally (add app instances) or vertically (VM resize) for throughput per load. Tune the database (HANA, etc.) with the right VM (memory/CPU), storage (IOPS/throughput, Write Accelerator), and index/partition design. Run a continuous-improvement cycle (measure → identify bottleneck → optimize → re-measure), leveraging insights from Azure Advisor and Azure Monitor.
Cues: "visualize network paths/latency" = Azure Network Watcher. "lower app↔DB latency" = proximity placement group/Accelerated Networking/VM size. "app-server throughput" = horizontal/vertical scaling. "DB performance" = tune VM, storage (IOPS/Write Accelerator), and design.
Watch the mix-ups: (1) Network optimization is a cycle (Network Watcher) → identify → improve—do not change config by guess. (2) NIC bandwidth scales with VM size—small VMs cap bandwidth. (3) Horizontal (add instances) vs vertical (resize) scaling. (4) DB optimization includes storage (IOPS/Write Accelerator).
4.2.3Section summary
- Measure network latency/throughput with Network Watcher; improve via proximity/Accelerated Networking/VM size
- Scale app servers horizontally/vertically; tune the DB via VM, storage, and design
- Run the continuous-improvement cycle: measure → identify → optimize → re-measure
Sign in to track progress — Log in.
Quick check
(just a quick review)Q1. You want to visualize network paths/latency between SAP app and DB tiers to identify bottlenecks. Best?
Q2. App↔DB latency is high. Most appropriate remedy?
Q3. You want to secure SAP app-server throughput by adding instances. What is this called?
Q4. On a small VM, SAP network throughput is capped. Correct cause?
Q5. What is the correct approach to continuous SAP performance optimization?
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.