Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Microsoft Certified: Azure Administrator Associate · Microsoft
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
Session persistence should be none.
For configuring a SQL Server Always On Availability Group Listener behind an Azure Internal Load Balancer (ILB), the required load balancer setting is: Session persistence = None if you set yes Only the primary replica should receive traffic When failover occurs, the ILB must route traffic to the new primary Sticky sessions (Client IP persistence) break failover routing This leads to: Clients being stuck to the old server Connection failures after failover Incorrect listener behavior Therefore, setting persistence to Client IP does NOT meet the goal.
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.