Exam AZ-104 topic 1 question 29 discussion

Answer is B. "None" FYI: Session persistence ensures that a client will remain connected to the same server throughout a session or period of time. Because load balancing may, by default, send users to unique servers each time they connect, this can mean that complicated or repeated requests are slowed down.

The load balancing rules configure how the load balancer routes traffic to the SQL Server instances. For this load balancer, you enable direct server return because only one of the two SQL Server instances owns the availability group listener resource at a time. Therefore Floating IP (direct server return) is Enabled. TCP 1433 is the standard SQL port. The availability group listener health probe port has to be different from the cluster core IP address health probe port.  The ports on a health probe are TCP59999 and TCP58888. https://docs.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/availability-group-load-balancer-portal-configure

I can see why session persistence seems to be a potential answer, but consider this guys: Session persistence can cause issues if the primary replica fails, as traffic might continue to be routed to an unavailable VM until the session timeout, rather than immediately failing over to the new primary. Microsoft recommends not using Client IP persistence for Always On listeners in Azure, as the availability group listener should dynamically route to the primary replica without sticky sessions. Session persistence can be useful but can also be harmful as shown above. Having a health probe, on the other hand, is an absolute requirement. it is used to determine the current primary replica.

It amazes me 40% vote on session persistence!! Really?

Answer is B. No Session persistence ensures that a client will remain connected to the same server throughout a session or period of time.

To configure an Azure internal load balancer (ILB) as a listener for a SQL Server Always On availability group, Session persistence must be set to Client IP. This ensures that the traffic from a specific client is directed consistently to the same backend server during the session. It is a critical requirement for SQL Server Always On listener configurations in Azure, as it helps maintain consistent connectivity for applications interacting with the SQL Server.

A is correct

The solution meets the goal. When you configure an Azure internal load balancer as a listener for a Microsoft SQL Server Always On availability group, you need to ensure that session persistence is configured correctly. Session persistence ensures that a client's connections are maintained with the same server during the session. In this case, setting the session persistence to Client IP is a valid solution as it ensures that a client's connection is maintained with the same server for the duration of the session based on the client's IP address. Therefore, the solution of setting session persistence to Client IP meets the goal. The answer is A (Yes).

asked to chatGPT, and the answer is: No, the solution does not meet the goal. For an Azure internal load balancer to properly work as a listener for an SQL Server Always On availability group, you need to set Session persistence to Client IP and protocol, not just Client IP. Setting the session persistence to "Client IP and protocol" ensures that the load balancer can route the traffic correctly based on both the client's IP address and the protocol, which is essential for the proper functioning of SQL Server Always On availability groups.

A. Yes. The solution mentioned in the scenario is correct. Setting session persistence to Client IP will ensure that all connections from a given client IP address are routed to the same SQL Server instance. This is important for ensuring that the client's session state is maintained, as SQL Server Always On availability groups do not provide session state sharing across multiple replicas. By using the Client IP session persistence mode, the Azure internal load balancer will route all client connections from a specific IP address to the same SQL Server instance. This ensures that the client's session state is maintained and provides a seamless failover experience. Therefore, the solution meets the goal of configuring an Azure internal load balancer as a listener for the SQL Server Always On availability group.

B is corerct

For configuring an Azure internal load balancer (ILB) as a listener for a SQL Server Always On availability group, setting the session persistence to "Client IP" is correct. This setting ensures that client connections from the same IP address are consistently routed to the same backend server. This is important for SQL Server Always On availability groups to ensure that the traffic is directed to the correct primary replica. Answer: A

Yes, session persistence can be configured in an internal load balancer (ILB) used as a listener for an Availability Group in Azure. This is useful in scenarios where you have a high-availability setup for SQL Server Always On Availability Groups and need to ensure that client connections are consistently routed to the same backend node for session consistency. https://learn.microsoft.com/en-us/azure/load-balancer/distribution-mode-concepts#session-persistence

Paste the question to CoPilot. and you will know.

No is right

Setting session persistence to "Client IP" on the Azure internal load balancer is a valid solution for configuring an Azure internal load balancer as a listener for a Microsoft SQL Server Always On availability group. This configuration ensures that client connections from the same source IP address are consistently directed to the same SQL Server instance within the availability group.

Ans. is NO, the key word is 'availability group' means we need redundancy of servers, servers must talk with each other which uses health probe not session persistence, this is use for communication between client and server. Correct me if im wrong.