Configure Session Persistence
Question
You have five Azure virtual machines that run Windows Server 2016. The virtual machines are configured as web servers.
You have an Azure load balancer named LB1 that provides load balancing services for the virtual machines.
You need to ensure that visitors are serviced by the same web server for each request.
What should you configure?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.D
With Sticky Sessions when a client starts a session on one of your web servers, session stays on that specific server. To configure An Azure Load-Balancer For
Sticky Sessions set Session persistence to Client IP or to Client IP and protocol.
On the following image you can see sticky session configuration:
Note:
-> Client IP and protocol specifies that successive requests from the same client IP address and protocol combination will be handled by the same virtual machine.
-> Client IP specifies that successive requests from the same client IP address will be handled by the same virtual machine.
https://cloudopszone.com/configure-azure-load-balancer-for-sticky-sessions/The correct answer is D. Session persistence to Client IP.
Explanation: When a client sends a request to the load balancer, it directs the request to one of the virtual machines based on a defined load-balancing algorithm. However, if the client sends subsequent requests to the load balancer, it may direct the request to a different virtual machine. This can cause issues such as loss of session data or inconsistent behavior on the website.
To avoid this, session persistence can be enabled on the load balancer. Session persistence ensures that a client's subsequent requests are directed to the same virtual machine that serviced their initial request. There are different methods of implementing session persistence, including source IP affinity (Client IP), protocol, session, and cookie-based affinity.
Source IP affinity (Client IP) is the best method for web applications that require session persistence. When enabled, the load balancer tracks the client's IP address and ensures that subsequent requests from that IP address are directed to the same virtual machine. This ensures that the client's session data is maintained across multiple requests.
Option A, Floating IP (direct server return) to Disabled, is not relevant to this scenario. Direct server return (DSR) is a method of load balancing that allows the response to be sent directly from the virtual machine to the client without passing through the load balancer. This can improve performance but is not related to session persistence.
Option B, Session persistence to None, would not provide session persistence. This means that subsequent requests from a client could be directed to a different virtual machine, potentially causing issues with session data.
Option C, Protocol to UDP, is not relevant to this scenario. The protocol used by the load balancer would depend on the requirements of the web application and the services it provides. UDP (User Datagram Protocol) is a connectionless protocol that is used for applications that require low latency but do not require reliability, such as video streaming or online gaming.
