This scenario requires unequal load distribution based on server capacity. The newer servers must receive more connections than the older ones, while still dynamically accounting for active connection counts.
According to BIG-IP Administration: Data Plane Configuration documentation:
Weighted Least Connections (member) combines:
Connection awareness (least connections)
Administrator-defined weights (ratios) to reflect server capacity
Pool members with higher weights receive proportionally more new connections than members with lower weights, even when using the same load balancing algorithm.
Why B is correct:
Allows assigning higher weights to newer servers and lower weights to older servers
Ensures smarter traffic distribution based on both capacity and real-time load
Why the other options are incorrect:
A. Global AvailabilityUsed for disaster recovery and site failover, not intra-pool load distribution.
C. Round RobinDistributes connections evenly without considering server capacity.
D. Least Connections (member)Balances only by current connection count and does not account for differences in server performance or capacity.
Correct Resolution:
Use Weighted Least Connections (member) and assign higher weights to newer servers so they receive more traffic while protecting older servers from overload.
