A network administrator is planning to add a trunk to a single BIG-IP system.

In the F5 BIG-IP ecosystem, a trunk is a logical grouping of two or more physical interfaces that the system treats as a single data path. This configuration is based on the Link Aggregation Control Protocol (LACP) or static link aggregation.

Trunks provide two primary benefits to the data plane:

Increased Bandwidth: By aggregating multiple physical interfaces (e.g., combining two 10Gbps interfaces), the aggregate throughput of the logical connection is increased. This allows the BIG-IP to handle higher traffic volumes than a single interface could support.

Link Redundancy: Trunks provide high availability at the physical layer. If one physical interface within the trunk fails or the cable is disconnected, the BIG-IP system automatically redistributes traffic across the remaining active interfaces in the trunk. This prevents a single cable or port failure from causing a network outage.

Why the other options are incorrect:

Option C: While VLAN tags are often used on trunks, the ability to use tagged VLANs is a property of the VLAN configuration and 802.1Q tagging, not the trunk itself. A single interface can support tagged VLANs without being part of a trunk.

Option D: Trunks are agnostic to the type of application traffic (such as VoIP) passing through them. They operate at Layer 2 to provide a reliable pipe for any Layer 3+ traffic.