F5-CA F5CAB2 Updated Exam

12

In the BIG-IP system, pool selection must occur on the client-side of the connection, before the system attempts to connect to a pool 3 member. The events listed 4 are the primary entry points for making these decisions:

CLIENT_ACCEPTED (E): This is a Layer 4 event triggered when the BIG-IP accepts a TCP connection. It is the earliest point where a pool can be assigned based on the client ' s source IP address or the destination port.

CLIENT_DATA (A): This event is triggered when the system receives a " chunk " of data on the client-side. It is often used for non-HTTP protocols (like custom TCP protocols) to inspect the payload and select a pool based on its contents.

HTTP_REQUEST (C): This is a Layer 7 event. It occurs once the BIG-IP has fully parsed the HTTP headers. This is the most common event for pool selection, allowing the administrator to route traffic based on the URI, Host header, or cookies.

Events like SERVER_SELECTED or SERVER_CONNECTED occur after the load balancing decision has already been made, and HTTP_RESPONSE or SERVER_DATA occur after the server has already started communicating back, making them too late for initial pool selection.

When establishing a redundant pair, each device must know where to send its health heartbeats and sync data.

The Peer IP: The Failover Peer IP is the IP address belonging to the other BIG-IP device in the HA pair. This is typically a 34 Self-IP on a dedicated " HA " or " Internal " VLAN, or the Management IP.

Purpose: It identifies the destination for the " Heartbeat " (the " Are you alive? " check).

Setup Context: During the initial setup, you tell Device A to look for Device B at its " Failover Peer IP, " and you tell Device B to look for Device A at its respective " Failover Peer IP. "

4647

Virtual Servers have a setting called VLAN and Tunnel Traffic which defines where the BIG-IP " listens " for new connections. 4849

Ingress Logic: A virtual server is an entry point. It must be enab 50 led on the VLAN where the Client resides. If a client is on the " 51 Internal " VLAN, the Virtual Server must be enabled there to receive the traffic.

Egress Logic: The BIG-IP system uses the TMM Routing Table and Self-IPs to reach pool members. It does not need the Virtual Server to be " enabled " on the destination VLAN (External) to send traffic there.

Default Behavior: By default, Virtual Servers are enabled on " All VLANs. " However, if restricted for security, the administrator must ensure the Virtual Server is active on the client-facing (ingress) VLAN.

In BIG-IP architecture, link aggregation and redundancy at Layer 2 are implemented using Trunks , not virtual servers or pools.

According to BIG-IP Administration Data Plane Concepts:

Interfaces are the physical network ports on the BIG-IP device

A Trunk is a logical grouping of multiple interfaces

Trunks can be configured to use LACP (Link Aggregation Control Protocol) to:

Provide link redundancy

Increase aggregate bandwidth

Allow automatic detection of link failures

VLANs are then assigned to the trunk , not directly to individual interfaces, once aggregation is in place

Correct Design for the Scenario:

To connect BIG-IP to two upstream switches with LACP:

One physical interface from BIG-IP connects to Switch A

Another physical interface from BIG-IP connects to Switch B

Both interfaces are placed into the same trunk

LACP is enabled on the trunk and on the switches

This configuration allows:

Traffic to continue flowing if one interface or switch fails

Proper LACP negotiation between BIG-IP and the upstream switches

Clean separation of responsibilities (Layer 2 handled by trunking, Layer 4–7 by virtual servers)

Why Option D Is Correct:

A Trunk containing an interface connected to each switch is exactly how BIG-IP implements LACP-based interface binding

The trunk handles link state, load distribution, and failover at the data plane

Why the Other Options Are Incorrect:

A & B – Virtual servers operate at Layers 4–7 and have nothing to do with physical link aggregation or LACP

C – VLAN IDs and MAC addresses are not configured inside a trunk definition; trunks aggregate interfaces, and VLANs are applied to trunks

Key Data Plane Concept Reinforced:

On BIG-IP systems, LACP is always configured on a Trunk , which aggregates physical interfaces to provide Layer 2 resiliency and bandwidth aggregation . Virtual servers and pools are not involved in physical interface binding.

===========