F5CAB2 Exam Dumps : BIG-IP Administration Data Plane Concepts (F5CAB2) exam

In BIG-IP terminology, aTrunkis the object used to implement Link Aggregation (IEEE 802.3ad/802.1AX). When a network engineer refers to "interface binding" or "EtherChannel" with LACP, the BIG-IP equivalent is a Trunk.

LACP (Link Aggregation Control Protocol):This is a protocol that allows the BIG-IP system to communicate with the upstream switches to negotiate the bundling of multiple physical links into a single logical link.

Resilience and Redundancy:By creating a trunk that includes interfaces connected to two different switches (typically configured as a VPC, VSS, or MLAG cluster on the switch side), the administrator ensures that the BIG-IP remains reachable even if one physical interface or one switch fails.

Data Plane Logic:The BIG-IP treats the trunk as a single Layer 2 interface. VLANs are then associated with the trunk rather than individual physical ports.

Why the other options are incorrect:

Option B:Trunks aggregate physical interfaces. While VLANs are associated with trunks, the trunk configuration itself does not "list" MAC addresses of the switches; it uses LACP to negotiate the connection.

Options C & D:Virtual Servers are Layer 4-7 objects used for traffic processing and load balancing. They do not possess "LACP profiles," nor are physical interfaces or management IPs treated as pool members for the purpose of link aggregation.

WithLeast Connections (member), BIG-IP attempts to send new connections to the pool member with the fewest current connections. In a perfectly “stateless” scenario (no affinity), this often trends toward a fairly even distribution over time.

However,persistence overrides load balancing:

When apersistence profileis applied, BIG-IP will continue sending a client (or client group) to thesame pool memberbased on the persistence record (cookie / source address / SSL session ID, etc.).

This means even if another pool member has fewer connections, BIG-IP may still select the persisted member to honor session affinity.

The result can beuneven active connection counts, even though the configured load balancing method is Least Connections.

Why the other options are not the best cause:

A. Priority Group Activation is disabledPriority Group Activation only affects selection when priority groups are configured; disabling it does not inherently create uneven distribution under Least Connections.

B. SSL Profile Server is appliedA server-side SSL profile affects encryption to pool members, but it does not by itself cause skewed selection across pool members. (Skew could happen indirectly if members have different performance/latency, but that’s not the primary, expected exam answer.)

D. Incorrect load balancing methodLeast Connections is a valid method and does not itself explain unevenness unless something is overriding it (like persistence) or pool members are not all eligible.

Conclusion:

Apersistence profileis the most common and expected reason that active connections becomeunevenly distributed, because persistencetakes precedence overthe Least Connections load-balancing decision.

Managing the lifecycle of a pool member requires understanding the difference between "Disabled" and "Forced Offline" states, especially when persistence is involved.

Disabled (User-Disabled): This state allows existing connections and persistent sessions to continue until they naturally time out or are closed by the client/server. It only preventsnewsessions from being established.

Forced Offline: This state is more restrictive; it allows existing connections to complete butrejectsall new connections, including those with existing persistence records.

Immediate Removal: Neither "Disabled" nor "Forced Offline" will instantly kill currently active, established TCP connections. To meet the requirement of "immediately" removing all connections, the administrator must first set the member toForced Offline(to prevent persistence from bringing in new traffic) and then use the command line (e.g., tmsh delete sys connection ss-server-addr [IP]) to clear the current connection table entries.