nerdexam
Microsoft

AZ-120 · Question #335

You have two Azure virtual machines that host a Microsoft SQL Server 2019 failover cluster instance (FCI) named FCI1. FCI1 hosts the database tier of an SAP NetWeaver system. The application tier…

The correct answer is D. In the private DNS zone, create an A record. Configure a DNN for failover cluster instance On Azure Virtual Machines, the distributed network name (DNN) routes traffic to the appropriate clustered resource. It provides an easier way to connect to the SQL Server failover cluster instance (FCI) than the virtual network name…

Design and implement high availability and disaster recovery (HA/DR)

Question

You have two Azure virtual machines that host a Microsoft SQL Server 2019 failover cluster instance (FCI) named FCI1. FCI1 hosts the database tier of an SAP NetWeaver system. The application tier connects to FCI1 by using a virtual network name (VNN) of fci1.contoso.com. Name resolution is provided by an Azure Private DNS zone. On FCI1, you implement a distributed network name (DNN) of FCI1DNN and verify that you can connect to fci1dnn.contoso.com. You need to ensure that the application tier can use the DNN when connecting to FCI1. What should you do first?

Options

  • AFrom SQL Server Configuration Manager on FCI1, enable shared memory for the SQL Server
  • BFrom SQL Server Configuration Manager on FCI1, create an alias in the SQL Server Native
  • CIn the private DNS zone, create a CNAME record.
  • DIn the private DNS zone, create an A record.

How the community answered

(29 responses)
  • A
    10% (3)
  • B
    3% (1)
  • C
    7% (2)
  • D
    79% (23)

Explanation

Configure a DNN for failover cluster instance On Azure Virtual Machines, the distributed network name (DNN) routes traffic to the appropriate clustered resource. It provides an easier way to connect to the SQL Server failover cluster instance (FCI) than the virtual network name (VNN), without the need for an Azure Load The distributed network name (DNN) replaces the virtual network name (VNN) as the connection point when used with an Always On failover cluster instance on SQL Server VMs. This negates the need for an Azure Load Balancer routing traffic to the VNN, simplifying deployment, maintenance, and improving failover. With an FCI deployment, the VNN still exists, but the client connects to the DNN DNS name instead of the VNN name.

Topics

#SQL Server FCI#distributed network name#Azure Private DNS#DNN

Community Discussion

No community discussion yet for this question.

Full AZ-120 Practice