F5 Networks F5CAB2 Dumps - Pass BIG-IP Administration Data Plane Concepts Exam in 2026

To meet the requirement of fault tolerance when one interface goes down, BIG-IP must use link aggregation so that loss of a single physical link does not isolate the VLAN(s).

How the objects relate (data plane view)

Interfaces = physical links.

Trunk (LACP) = bundles multiple interfaces into one logical link that provides redundancy (and possibly bandwidth aggregation).

VLANs are assigned to interfaces or trunks. If you need multiple VLANs on the same trunk, they must use 802.1Q tagging (because you can only have one untagged VLAN per interface/trunk).

Self IPs are then placed on the VLANs to provide BIG-IP presence and routing/ARP functions, but self IPs are not what provides link resiliency---the trunk does.

Why Option D is correct

You have two physical interfaces and you want resiliency if one fails put both interfaces into one trunk with LACP enabled.

You need both external and internal VLANs on those same two links both VLANs should be configured as tagged on that trunk, so they can coexist on the same aggregated link.

If either physical interface fails, the trunk remains up via the remaining interface, keeping both VLANs operational.

Why the other options are incorrect

A: Two VLANs cannot both be untagged on the same trunk/interface. Only one untagged VLAN is possible; additional VLANs must be tagged.

B: Two trunks ''each with one VLAN'' would typically mean splitting VLANs across separate trunks. With only two interfaces total, that becomes one interface per trunk---if one interface goes down, the VLAN on that interface is down (no redundancy for that VLAN).

C: Same redundancy problem as B, and disabling LACP removes the negotiated aggregation behavior expected when the switch engineer specifically requested LACP.

===========

This scenario combines session continuity, multiple protocols (HTTP and FTP), and HA failover behavior, which directly implicates persistence handling across devices and services.

Key Requirements Breakdown

Same pool member for entire session

Session must survive failover

Session must span multiple services (HTTP and FTP)

Why Persistence Mirroring + Match Across Services Is Required

Persistence Mirroring

Ensures persistence records are synchronized from the active BIG-IP to the standby BIG-IP.

Without mirroring:

After failover, the standby device has no persistence table

Clients are load-balanced again

Sessions break, forcing users to restart

Persistence mirroring is essential for session continuity during failover

Match Across Services

Allows a single persistence record to be shared across multiple virtual servers / protocols

Required when:

HTTP and FTP must use the same pool member

Multiple services are part of a single application session

Together, these settings ensure:

Persistence survives device failover

Persistence is honored across HTTP and FTP

Why the Other Options Are Incorrect

A . Cookie persistence and session timeout

Cookie persistence only applies to HTTP and does not address FTP or failover synchronization.

B . Stateful failover and Network Failover detection

Stateful failover applies to connection state, not persistence records, and does not link HTTP and FTP sessions.

D . SYN-cookie insertion threshold and connection low-water mark

These are DoS / SYN flood protection settings, unrelated to persistence or HA behavior.

According to F5 BIG-IP documentation regarding High Availability and MAC Masquerade behavior, the system allows for more granular control over Layer 2 addresses during failover events.

Standard MAC Masquerade: By default, when a traffic group is assigned a MAC masquerade address (like 02:12:34:56:00:00), the BIG-IP system uses that exact MAC address for all traffic associated with that traffic group across all VLANs. This ensures that upstream switches do not need to relearn ARP entries for the Virtual IP, but it can cause issues in environments where multiple VLANs share the same physical infrastructure or monitoring tools that flag identical MACs across segments.

Per-VLAN MAC Masquerade: When the system database variable tm.macmasqaddr_per_vlan is set to true, the BIG-IP system calculates a unique MAC address for each VLAN. It does this by taking the base MAC masquerade address configured in the traffic group and adding the VLAN ID (tag) to it.

Calculation Logic:

Base MAC: 02:12:34:56:00:00

VLAN ID: 1501

To find the suffix, the VLAN ID is converted from decimal to hexadecimal:

$1501$ in decimal = 05DD in hex.

The system then applies this offset to the last two octets of the base MAC address.

00:00 + 05:DD = 05:DD.

Result: The final MAC address for VLAN 1501 becomes 02:12:34:56:05:dd.

This ensures that every VLAN has a unique Layer 2 identity while still reaping the benefits of 'gratuitous ARP-less' failover provided by MAC masquerading.

When managing a large environment with hundreds of Virtual Servers, the most efficient way to identify the relationship between an iRule and the objects it manages is to view the properties of the iRule itself.

iRule Properties: Within the BIG-IP Configuration Utility, navigating to Local Traffic > iRules and selecting a specific iRule provides a 'Statistics' or 'Usage' tab (depending on the version). This view explicitly lists all Virtual Servers currently associated with that specific iRule.

Centralized Management: Instead of manually checking 235 individual Virtual Servers under the 'Virtual Servers' menu, the iRules menu acts as a central point of reference for that specific logic.

Data Plane Impact: Because iRules can modify traffic flow, headers, and load balancing decisions, seeing the full list of affected Virtual Servers is critical before making adjustments to avoid unintended side effects across the application portfolio.