You have an on-premises line-of-business (LOB) application that uses a Microsoft SQL Server instance as the backend. You plan to migrate the on-premises SQL Server instance to Azure virtual machines.

Question

Options

• Aan Always On availability group that has premium storage disks and a virtual network name
• Ban Always On Failover Cluster Instance that has a virtual network name (VNN) and a standard file
• Can Always On availability group that has premium storage disks and a distributed network name
• Dan Always On Failover Cluster Instance that has a virtual network name (VNN) and a premium file

• A
  9% (3)
• B
  31% (10)
• C
  47% (15)
• D
  13% (4)

Explanation

Always On availability groups on Azure Virtual Machines are similar to Always On availability groups on-premises, and rely on the underlying Windows Server Failover Cluster. If you deploy your SQL Server VMs to a single subnet, you can configure a virtual network name (VNN) and an Azure Load Balancer, or a distributed network name (DNN) to route traffic to your availability group listener. There are some behavior differences between the functionality of the VNN listener and DNN listener that are important to note: * Failover time: Failover time is faster when using a DNN listener since there is no need to wait for the network load balancer to detect the failure event and change its routing. Not B, not D: Migrate to an Always On availability group, not an Always on Failover cluster https://docs.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/availability-group-

No community discussion yet for this question.