In F5 BIG-IP architecture, a Trunk is a logical aggregation of physical interfaces designed to increase bandwidth and provide link redundancy through 802.3ad Link Aggregation Control Protocol (LACP).
When creating a Trunk object within the BIG-IP configuration, the administrator must assign physical Interfaces to it - these are the underlying hardware ports (e.g., 1.1, 1.2, 1.3) that will be bundled together to form the aggregated logical link.
It is critical to understand the layered object hierarchy on the BIG-IP platform:
* Interfaces # assigned to Trunks
* Trunks (or individual Interfaces) # assigned to VLANs (as tagged or untagged members)
* VLANs # assigned Self IP addresses
* Self IPs / Routes # configured at the network layer above
VLANs are not added to a Trunk; rather, a Trunk is added as a member of a VLAN. IP addresses and network routes are configured independently at a higher abstraction layer and have no direct association with Trunk creation.
This layered design ensures proper separation of concerns across the data plane. Misunderstanding this hierarchy is a common configuration error that can result in traffic forwarding failures.
Reference: BIG-IP Administration - Data Plane Configuration, Module: Network Objects - Interfaces, Trunks, and VLANs.

When a pool contains servers with heterogeneous hardware capabilities (differing CPU, RAM, or connection limits), a static load balancing method like Round Robin is ineffective because it distributes requests equally, regardless of the server's capacity. To optimize traffic distribution for newer, more powerful servers, a dynamic or weighted method is required.
Weighted Least Connections (member): This is the ideal method for this scenario. It combines two factors:
Least Connections: It first checks the current active connection count to ensure traffic goes to the least busy server.
Weight (Ratio): It allows the administrator to assign a "Ratio" value to each pool member. Newer servers can be assigned a higher ratio (e.g., 3) while older servers are assigned a lower ratio (e.g., 1). The BIG-IP system uses these weights to disproportionately favor the newer servers even when connection counts are similar.
Why other options are incorrect:
Global Availability: This is primarily a GSLB (Global Server Load Balancing) or specific LTM priority group concept where traffic is sent to the first available member in a list until it fails, then moves to the next. It does not load balance based on capacity.
Round Robin: This passes each new connection request to the next server in line, treating the old and new servers exactly the same.
Least Connections (member): While this sends traffic to the server with the fewest active connections, it assumes all servers are equal. If an old server and a new server both have 10 connections, they are treated as equally capable of taking the 11th, which is not true in this scenario.