You have a Microsoft SQL Server Always On availability group on Azure virtual machines.
You need to configure an Azure internal load balancer as a listener for the availability group.
What should you do?
Click on the arrows to vote for the correct answer
A. B. C. D.D
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/sql/virtual-machines-windows-portal-sql-alwayson-int-listenerTo configure an Azure internal load balancer as a listener for the Microsoft SQL Server Always On availability group, you need to perform the following steps:
Create an internal load balancer: First, you need to create an Azure internal load balancer in the same virtual network as the availability group. The internal load balancer must have a backend pool containing all the virtual machines that are part of the availability group. This can be done using Azure Portal or Azure CLI.
Create a load balancing rule: After creating the internal load balancer, you need to create a load balancing rule to route traffic to the virtual machines in the availability group. The load balancing rule should use port 1433, which is the default port for SQL Server. The load balancing rule should also use the backend pool that you created in step 1.
Configure health probes: Health probes are used to monitor the health of the virtual machines in the backend pool. For SQL Server availability groups, you should create a TCP health probe on port 59999. This port is used by the availability group listener to monitor the health of the replicas.
Set session persistence: Session persistence determines how traffic is distributed to the virtual machines in the backend pool. For SQL Server availability groups, you should set session persistence to "Client IP". This ensures that all traffic from a given client is sent to the same virtual machine in the backend pool.
Based on the above steps, the correct answer for the question would be option C: Set session persistence to Client IP and protocol. This is because session persistence must be set to "Client IP" for SQL Server availability groups, as mentioned in step 4. However, it is recommended to also set session persistence to "Protocol" to ensure that the same protocol (TCP) is used for all requests. Option A, which suggests creating an HTTP health probe on port 1433, is incorrect because HTTP is not used for SQL Server availability groups. Option B, which suggests setting session persistence to "Client IP" only, is incomplete because it does not address the need to also set session persistence for the protocol. Option D, which suggests enabling Floating IP, is not necessary for SQL Server availability groups and is not relevant to this configuration.