By default, BIG-IP load balancing algorithms (such as Round Robin) distribute connections evenly across all available pool members. However, persistence profiles override normal load balancing decisions by forcing subsequent connections from a client to be sent to the same pool member.
According to the BIG-IP Administration: Data Plane Configuration documentation:
Persistence creates a client-to-server mapping that is honored before load balancing algorithms are applied.
When persistence is enabled, BIG-IP may repeatedly select the same pool member even if others are available.
This directly alters load balancing behavior.
Why the other options are incorrect:
A). Adding a OneConnect profileOneConnect optimizes server-side TCP connections but does not change which pool member is selected.
B). Enabling SNAT automapSNAT affects source address translation, not pool member selection.
C). Enabling a fallback host in the HTTP profileA fallback host is only used when no pool members are available.
Correct Resolution:
Adding a persistence profile alters load balancing behavior by maintaining client affinity to a specific pool member.

Least Connections (node) balances connections across the physical server regardless of how many services or pool members exist on that node.

This question addresses the critical architectural distinction between "member-based" and "node-based" load balancing in environments where servers are multi-homed or host multiple virtualized services. On a BIG-IP, a node represents the underlying IP address of a physical or virtual server, while a pool member represents a specific combination of that IP and a service port (e.g., 10.1.1.10:80).
When multiple pools reference the same IP address across different ports or Virtual Servers, using Least Connections (member) (Option D) only balances connections relative to that specific pool. For example, if Pool_A and Pool_B both use Server_X, and Pool_A has 100 connections while Pool_B has only 5, a member- based algorithm for Pool_B only sees the 5 connections and may continue to send traffic there even if Server_X is CPU-saturated by Pool_A.
The Least Connections (node) algorithm (Option B) solves this by tracking the aggregate total of all active connections directed to that specific node (IP address) across every pool on the system. By selecting the node with the absolute lowest total connection count, the BIG-IP ensures a more equitable distribution of work at the hardware resource level. Predictive methods (Options A and C) use a ranking system based on the trend of connection counts over time, but for the specific requirement of maintaining an equal number of current connections on multi-service servers, the direct Least Connections (node) calculation is the standard and most effective procedural choice.

In this scenario, each backend node (server) hosts multiple services and is referenced by multiple pools and virtual servers. The goal is to ensure an equal number of total connections per backend server, regardless of how many pool members (services/ports) exist on that server.
According to the BIG-IP Administration: Data Plane Configuration documentation:
Least Connections (node) tracks the total number of active connections to a node across all pool members and services.
This algorithm ensures load distribution is balanced at the server level, not just at the individual service (member) level.
It is specifically recommended when:
Multiple pool members exist on the same backend server
Multiple virtual servers reference the same backend servers
Why the other options are incorrect:
B . Predictive (member)
Predictive algorithms are advanced and traffic-pattern based, but they operate at the member level and do not guarantee equal connections per server.
C . Least Connections (member)
This balances connections per pool member, which can overload a server hosting multiple members while still appearing "balanced" per member.
D . Predictive (node)
Although node-aware, predictive algorithms are less deterministic and not the best choice when strict equality of connections is required.
Correct Resolution:
Using Least Connections (node) ensures that each backend server carries an equal connection load across all services and pools.

When a single IP address (Virtual Server) must host multiple hostnames (e.g., site1.com, site2.com) over HTTPS, the BIG-IP must be able to present the correct SSL certificate for each site during the initial handshake. This requirement is handled by a technology called Server Name Indication (SNI).
To implement this on the BIG-IP, the administrator must use a Client SSL profile because the encryption is occurring between the user (Client) and the Virtual Server. Within the Client SSL profile settings, there is a field called Server Name. By creating multiple Client SSL profiles-each with a different "Server Name" (the hostname) and its corresponding certificate-and attaching them all to the same Virtual Server, the BIG-IP can inspect the SNI extension in the client's "Client Hello" packet. It then selects the specific profile that matches the requested hostname.
Option A is incorrect because "Client Name" is not the standard field name used for SNI hostname matching in the profile. Options B and C refer to Server SSL profiles, which manage the connection between the BIG- IP and the backend servers. While Server SSL profiles also have a "Server Name" field (used to send SNI to a backend server), the requirement here is to provide encrypted communication for "users" accessing the virtual server, which definitively requires a Client-side SSL configuration.