You have a highly available deployment of SAP NetWeaver on Azure virtual machines. The database tier is hosted on two virtual machines that run Windows Server 2019 and have Microsoft SQL Server 2017…

Question

Options

• ARedeploy the NetWeaver, application, and SQL Server virtual machines to the same proximity
• BIncrease the tempdb size on the SQL Server virtual machines.
• CConfigure the SQL Server database to use asynchronous replication.
• DMove the application virtual machines to the same subnet as the SQL Server virtual machines.

• A
  68% (15)
• B
  5% (1)
• C
  18% (4)
• D
  9% (2)

Explanation

Acc DB (Accumulated Database time) measures round-trip latency between the application tier and the database tier. Redeploying all tiers into an Azure Proximity Placement Group places the VMs on physically co-located hardware, minimizing network latency and directly reducing the Acc DB metric - making A the correct fix.

B is wrong because increasing tempdb size addresses SQL Server's workspace for temporary operations, not the network-layer latency that Acc DB captures. C is wrong because asynchronous replication is a high-availability/DR strategy and does nothing to reduce query response time; it could actually worsen consistency. D is wrong because Azure subnets are logical constructs - moving VMs to the same subnet doesn't change their physical location, so latency remains unchanged; proximity placement does.

Memory tip: Think of it this way - Acc DB = Accumulated Distance to DB. The fix is always to shrink the physical distance, which in Azure means Proximity Placement Groups.

No community discussion yet for this question.