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.To 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: Create an Azure internal load balancer and configure it to use an IP address from a subnet that's different from the subnets used by the availability group.
Create a health probe: Create an Azure health probe to monitor the availability of the SQL Server instances. In this scenario, the health probe should be created on port 1433, which is the default port for SQL Server. This health probe will monitor the availability of each SQL Server instance.
Create a backend pool: Create a backend pool and add the IP addresses of the SQL Server instances that are part of the availability group. The backend pool is responsible for distributing traffic to the SQL Server instances.
Create a load balancing rule: Create a load balancing rule to distribute traffic to the backend pool based on the health of the SQL Server instances. For the load balancing rule, you should set session persistence to Client IP. This setting ensures that a client's requests are always routed to the same SQL Server instance. If the session persistence is set to Client IP and protocol, the load balancer would balance traffic based on both the client IP and the protocol.
Therefore, the correct answer is option C, "Set session persistence to Client IP and protocol." However, option A is incorrect because creating an HTTP health probe on port 1433 is not a valid configuration for SQL Server Always On availability groups. Option B is incorrect because setting session persistence to Client IP alone is not sufficient to ensure that a client's requests are always routed to the same SQL Server instance.