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.
Hot Area:
Answer: 
Needs to bet set to Multiple hosts + single
The Single option specifies that NLB should direct multiple requests from the same client IP address to the same cluster host. This is the default setting for affinity. You can optionally modify the NLB client affinity to direct all client requests from a TCP/IP Class C address range (instead of a single IP address) to a single cluster host by enabling the Network option instead of the Single option. This feature ensures that clients that use multiple proxy servers to access the cluster can have their TCP connections directed to the same cluster host.
The Network option specifies that NLB direct multiple requests from the same TCP/IP Class C address range to the same cluster host. Enabling Network affinity instead of Single affinity ensures that clients that use multiple proxy servers to access the cluster have their TCP connections directed to the same cluster host.
https://technet.microsoft.com/en-us/library/cc771709(v=ws.11)
I’m not entirely sure that it needs to be single and not none, because the data is stored in a DB rather than beeing session based, BUT nonetheless this is indeed the node that needs be set.
“You discover that all of the users from a subnet named Subnet1 always connect to the same NLB node” meant that the current Affinity setting is “Network”.
Affinity defines what node a client connects to after establishing a first connection with the server.
For instance, if no affinity is used, each time the same client connects to the NLB cluster it may receive a response from different nodes. This is fine for
applications that do not maintain a session state on the node.
If the application maintains a session state, this could be an issue.
For example, imagine that a client connects to a node and the node saves the client name to the application state. Then, when the client connects to a different node later, that node will not have the state information for the client.
Requirements:
The session state information of App1 is stored in a Microsoft SQL Server 2012 database.
You need to ensure that all of the users from each of the subnets connect equally across all of the nodes in Cluster1.
Possible Solution: Affinity setting: “Single” because session state matters in this context