You plan to deploy an SAP on Azure landscape that will use Microsoft SQL Server 2019 as the database platform. You deploy an Azure virtual machine and SQL Server 2019 Cumulative Update (CU) 10. You…

Question

Options

• AConfigure a distributed network name (DNN).
• BConfigure a virtual name (VNN).
• CDeploy an Azure Application Gateway.
• DDeploy an Azure Standard Load Balancer.

• A
  77% (47)
• B
  3% (2)
• C
  5% (3)
• D
  15% (9)

Explanation

Distributed Network Name (DNN) was introduced in SQL Server 2019 CU8 specifically for Azure environments, and since CU10 is already deployed, it's immediately available - no additional infrastructure required. DNN allows SQL Server Always On Availability Groups or Failover Cluster Instances to be reached via a lightweight name registered directly in SQL Server, bypassing the need for Azure networking constructs entirely.

Why the distractors are wrong:

• B (VNN): A Virtual Network Name is the older approach and requires an Azure Load Balancer to handle IP failover, since Azure doesn't support floating IPs - adding extra administrative overhead.
• C (Application Gateway): This is a Layer 7 HTTP/HTTPS load balancer designed for web apps, not SQL Server database traffic.
• D (Azure Standard Load Balancer): Previously required alongside VNN for SQL Server HA in Azure, but DNN makes it unnecessary. Deploying one increases administrative effort rather than minimizing it.

Memory tip: Think "DNN = Done, Nothing extra needed." DNN was built for Azure to eliminate the Load Balancer dependency - if the SQL Server version supports it (2019 CU8+), it's always the lowest-effort path.

No community discussion yet for this question.