HOTSPOT
Your network contains an Active Directory domain named contoso.com. The domain contains a
Network Load Balancing (NLB) cluster named Cluster1 that contains four nodes. Cluster1 hosts a web
application named App1. The session state information of App1 is stored in a Microsoft SQL Server
2012 database.
The network contains four subnets.
You discover that all of the users from a subnet named Subnet1 always connect to the same NLB
node.
You need to ensure that all of the users from each of the subnets connect equally across all of the
nodes in Cluster1.
What should you modify from the port settings?
To answer, select the appropriate setting in the answer area.
What should you modify from the port settings?
HOTSPOT
Your network contains an Active Directory domain named contoso.com. The domain contains a
Network Load Balancing (NLB) cluster named Cluster1 that contains four nodes. Cluster1 hosts a web
application named App1. The session state information of App1 is stored in a Microsoft SQL Server
2012 database.
The network contains four subnets.
You discover that all of the users from a subnet named Subnet1 always connect to the same NLB
node.
You need to ensure that all of the users from each of the subnets connect equally across all of the
nodes in Cluster1.
What should you modify from the port settings?
To answer, select the appropriate setting in the answer area.
I guess you should change affinity to ‘None’?
You are right, till app is maintaining session state itself, affinity is not demanded.
None – With No affinity, NLB does not associate clients with a particular member. Every client request can be load balanced to any member. This affinity provides the best performance but might disrupt clients with established sessions, because subsequent requests might be load balanced to other members where the session information does not exist.
Single – In Single affinity, NLB associates clients with particular members by using the client’s IP address. Thus, requests coming from the same client IP address always reach the same member. This affinity provides the best support for clients that use sessions on an intranet. These clients cannot use No affinity because their sessions could be disrupted. Additionally, these clients cannot use Class C affinity because intranet clients typically have IP addresses within a narrow range. It is likely that this range is so narrow that all clients on an intranet have the same Class C address, which means that one member might process all of the requests while other members remain idle.
Class C – With Class C affinity, NLB associates clients with particular members by using the Class C portion of the client’s IP address. Thus, clients coming from the same Class C address range always access the same member. This affinity provides the best performance for clusters serving the Internet.
https://technet.microsoft.com/en-us/library/bb687542.aspx