Free Practice Questions for the F5-CA F5CAB2 Exam (2026 Updated)

In BIG-IP LTM, health monitors are used to determine the availability of pool members and directly influence traffic flow decisions in the data plane.

Key characteristics of the default HTTP monitor according to BIG-IP Administration Data Plane Concepts:

Sends an HTTP request (typically GET /)

Expects an HTTP response code of 200 OK

Any response other than 200 is treated as a monitor failure

A failed monitor causes the pool member to be marked offline (down)

In this scenario:

Two pool members return 404 Not Found

A 404 response indicates that the requested object was not found

This does not meet the success criteria of the default HTTP monitor

These two members are therefore marked offline

One pool member returns 200 OK

This matches the expected response

The member is marked online

Resulting Pool Member Availability:

2 members: Offline

1 member: Online

Why the Other Options Are Incorrect:

B – 404 responses are not considered healthy by the default HTTP monitor

C – At least one member responds with the expected 200 OK

D – Members returning 404 responses fail the monitor and cannot be marked online

Key Data Plane Concept Reinforced:

BIG-IP health monitors make binary availability decisions based strictly on configured success criteria. For HTTP monitors, response codes matter— 404 is a failure , even if the service is technically reachable.

===========

In BIG-IP LTM, a pool member state directly affects how traffic is handled at the data plane level. When a pool member is manually disabled , BIG-IP changes the member’s availability state to disabled , which has specific and predictable traffic-handling consequences.

According to BIG-IP Administration Data Plane Concepts:

A disabled pool member :

Does not accept new connections

Continues to process existing non-persistent connections until they naturally close

Is removed from load-balancing decisions , including persistence lookups

Most importantly for this question:

Persistent connections (such as those created using source-address persistence, cookie persistence, or SSL persistence) are not honored for a disabled pool member

BIG-IP will not send new persistent traffic to a disabled member, even if persistence records exist

Therefore, when a pool member is manually disabled, it stops processing persistent connections , while allowing existing non-persistent flows to drain gracefully.

Why the Other Options Are Incorrect:

B – Persistent connections are not honored for a disabled pool member

C – Existing connections are not immediately terminated when a pool member is disabled

D – Only the disabled pool member stops accepting new connections, not all pool members

Key Data Plane Concept Reinforced:

Manually disabling a pool member is a graceful administrative action that prevents new and persistent traffic from reaching the member while allowing existing connections to complete, which is critical for maintenance and troubleshooting scenarios.

===========

In a BIG-IP device service cluster , configuration objects such as virtual servers, pools, profiles, and iRules are maintained through configuration synchronization (config-sync) .

Key BIG-IP concepts involved:

Device Service Cluster (DSC) A cluster is a group of BIG-IP devices that share configuration data. One device is typically used to make changes, which are then synchronized to the rest of the group.

Config-Sync Direction Matters

Changes are made on a local device

Those changes must be pushed to the group

The correct operation is “Sync Device to Group”

Why C is correct:

The virtual server was created only on device 1

Other devices in the cluster do not yet have this object

To propagate the new virtual server to all cluster members, the administrator must synchronize device 1 to the group

Why the other options are incorrect:

A. Synchronize the settings of the group to device 1 This would overwrite device 1’s configuration with the group’s existing configuration and may remove the newly created virtual server .

B. Create a new cluster on device 1 The cluster already exists. Creating a new cluster is unnecessary and disruptive.

D. Create a new virtual server on device 2 This defeats the purpose of centralized configuration management and risks configuration drift.

Conclusion:

After creating a new virtual server on a BIG-IP device that is part of a cluster, the administrator must synchronize the configuration from that device to the group so all devices share the same ADC application objects.

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.

The BIG-IP system uses a specific precedence algorithm to determine which virtual server (listener) should process an incoming packet when multiple virtual servers might match the criteria. Since BIG-IP version 11.3.0, the system evaluates three primary factors in a fixed order of importance:

Destination Address: The system first looks for the most specific destination match. A " Host " address (mask /32) is preferred over a " Network " address (mask /24, /16, etc.), which is preferred over a " Wildcard " (0.0.0.0/0).

Source Address: If multiple virtual servers have identical destination masks, the system then evaluates the source address criteria. Again, a specific source host match is preferred over a source network or a wildcard source.

Service Port: Finally, if both destination and source specifications are equal, the system checks the port. A specific port match (e.g., 80) is preferred over a wildcard port (e.g., or 0).

Following this logic, a virtual server configured with a specific destination host , a specific source host , and a specific service port represents the highest level of specificity and thus the highest preference.

The BIG-IP processing flow follows a specific sequence of events as a packet moves through the system.

TCP Handshake: Before any application-layer data (like HTTP) can be processed, a TCP connection must be established.

The First Event: The very first event triggered when a client completes the 3-way handshake with the virtual server is CLIENT_ACCEPTED .

Profile Influence: Even if an HTTP profile is attached, the system must first " accept " the connection at the protocol level. HTTP_REQUEST only triggers after the client sends data that the BIG-IP recognizes as a valid HTTP request. If a client connects but never sends a request, CLIENT_ACCEPTED will have fired, but HTTP_REQUEST will not.

The behavior of a health monitor is determined by its Send String and Receive String .

Default HTTP Monitor: The pre-configured default HTTP monitor on a BIG-IP system has an empty Receive String .

Success Criteria: When the Receive String is blank, the BIG-IP system considers the health check successful if it receives any valid HTTP response from the server.

Status Code Interpretation: Because a 404 Not Found is a valid HTTP status code (it is a properly formatted response from a running web server process), the BIG-IP interprets this as the application being " alive " .

Result: All three members (including the two returning 404s and the one returning 200) will be marked as UP/Available (Green).

A Self IP is an IP address on the BIG-IP system that you associate with a specific VLAN .

VLAN Association: A Self IP cannot exist independently; it must be bound to a VLAN to define which network segment the BIG-IP can communicate with.

Layer 2 to Layer 3 Mapping: While a VLAN is associated with physical interfaces or trunks (Layer 2), the Self IP provides the Layer 3 identity for the BIG-IP on that VLAN.

Traffic Processing: Self IPs are used by the BIG-IP for health checking backend servers, acting as a default gateway for servers, and for HA heartbeat communication.

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.

The diagram illustrates a specific TCP handshake sequence where the BIG-IP system acts as a transparent forwarder rather than a full proxy. The key indicators that identify this as a Forwarding (IP) virtual server are as follows:

Initial Packet Processing : The diagram explicitly states that the LTM evaluates the packet looking only at the destination IP address . This is the fundamental characteristic of a Forwarding IP virtual server, which uses the system ' s routing table to make forwarding decisions instead of load balancing to a pool of members.

Handshake Sequence : Unlike a Standard virtual server, which completes the three-way handshake with the client (SYN, SYN-ACK, ACK) before initiating a separate connection to the server, the Forwarding IP virtual server passes the client ' s original SYN packet directly to the destination node.

Response Timing : The BIG-IP system waits for the SYN-ACK from the destination node before it sends a SYN-ACK back to the client. It essentially " passes through " the handshake signals while still maintaining a state entry in the connection table to track the flow.

Packet-by-Packet Logic : While it tracks the state, it does not perform address translation (unless SNAT is specifically configured) or deep packet inspection like a full proxy would.

Why other options are incorrect:

Standard virtual server : A Standard virtual server is a " full proxy. " It would finish the handshake with the client first and only then open a second, independent TCP connection to the backend server.

Stateless virtual server : A stateless virtual server does not track connections in the connection table. The diagram shows the system meticulously passing sequence numbers ($seq\_num$) and acknowledgment numbers ($ack\_num$) between the two sides, which requires stateful tracking of the TCP flow.

In a BIG-IP high availability (HA) configuration, Auto-Sync is a device trust feature that automatically synchronizes configuration changes from the Active device to the Standby device within a Sync-Failover device group.

Key principles from BIG-IP Administration Data Plane Concepts:

The Active device is always the authoritative source of configuration

Configuration changes are intended to be made only on the Active device

With Auto-Sync enabled , any time the Active device configuration changes, the system automatically pushes the configuration to all Standby members of the device group

Configuration changes made directly on a Standby device are not preserved

In this scenario:

The administrator modifies a Virtual Server on the Standby device

That change is local only and does not alter the device group’s synchronized configuration

When Auto-Sync next runs (triggered by a change on the Active device or an internal sync event), the Active device configuration overwrites the Standby configuration

As a result, the configuration change made on the Standby device is undone .

Why the Other Options Are Incorrect:

A – The change is not undone only when another change is made; it is undone during the next Auto-Sync operation

B – Changes made on the Standby device are never propagated to the Active device

D – Auto-Sync does not merge or promote Standby changes into the HA pair configuration

Best Practice Reinforced:

Always perform configuration changes on the Active BIG-IP device when Auto-Sync is enabled to ensure consistent and predictable HA behavior.

===========

To select the correct virtual server type, an administrator must balance the need for L7 intelligence versus raw throughput and hardware offloading:

Performance (Layer 4) Virtual Server: This type is designed for maximum speed. It uses the fastL4 profile, which allows the BIG-IP system to leverage the ePVA (Embedded Packet Velocity Accelerator) hardware chip. When a Performance (L4) virtual server is used, the system processes packets at the network layer (L4) without looking into the application payload (L7). This fulfills the requirement for hardware acceleration and avoids the overhead of HTTP optimization features, which are not needed in this scenario.

Performance (HTTP) Virtual Server: While fast, this type uses the fasthttp profile to provide some L7 awareness and optimization (like header insertion or small-scale multiplexing). Since the requirement specifically states HTTP optimization is not required, the L4 variant is more efficient.

Standard Virtual Server: This is a full-proxy type. While it offers the most features (SSL offload, iRules, Compression), it processes traffic primarily in the TMOS software layer (or via high-level hardware assistance), which is " slower " than the pure hardware switching path of the Performance (L4) type.

Stateless Virtual Server: This is typically used for specific UDP/ICMP traffic where the system does not need to maintain a connection table. It is not appropriate for standard HTTP (TCP) applications requiring persistent sessions or stateful load balancing.

By choosing Performance (Layer 4) with the fastL4 profile, the organization ensures that the traffic is handled by the hardware acceleration chips, providing the lowest latency and highest throughput possible for their HTTP application.

The BIG-IP system supports various remote authentication methods like LDAP, Active Directory, and RADIUS.

Fallback to Local: This is a specific security and availability feature within the System > Users > Authentication configuration.

Redundancy: When " Fallback to Local " is enabled, the BIG-IP will first attempt to authenticate a user against the configured remote server. If that remote server is unreachable or fails to respond, the system will then check its internal Local User database for credentials.

Administrative Access: This is standard practice for the " admin " or emergency accounts to ensure the system remains accessible even if the corporate directory service (e.g., AD) is offline.

On BIG-IP systems, physical interface bandwidth is fixed by the link speed (for example, 1GbE or 10GbE). When traffic demand exceeds the capacity of a single interface, BIG-IP provides link aggregation through trunks .

Key concepts involved:

Interfaces A single physical interface (such as 1.1) is limited to its negotiated link speed. You cannot exceed this capacity through software tuning alone.

Trunks (Link Aggregation) A trunk combines multiple physical interfaces into a single logical interface.

BIG-IP supports LACP and static trunks.

Traffic is distributed across member interfaces, increasing aggregate bandwidth and providing redundancy .

VLANs are then assigned to the trunk , not directly to individual interfaces.

Why option B is correct:

Creating a trunk with two interfaces allows BIG-IP to use both physical links simultaneously.

This increases total available bandwidth (for example, two 10Gb interfaces → up to 20Gb aggregate capacity).

This is the documented and supported method for scaling bandwidth on BIG-IP.

Why the other options are incorrect:

A. Increase the MTU MTU changes affect packet size and efficiency, not total bandwidth capacity .

C. Assign two interfaces to the VLAN BIG-IP does not support assigning a VLAN to multiple interfaces directly. VLANs must be associated with one interface or one trunk .

D. Set the media speed manually Media speed can only be set up to the physical capability of the interface and connected switch port. It cannot exceed the hardware limit.

Conclusion:

To increase total available bandwidth on BIG-IP when a single interface is insufficient, the administrator must create a trunk object with multiple interfaces and move the VLAN onto the trunk. This aligns directly with BIG-IP data plane design and best practices.

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.

Redundant BIG-IP systems (HA pairs) must maintain constant communication to monitor the health of the peer and synchr 15 onize states. 16

Heartbeats: By default, even with a serial cable, th 17 e BIG-IP systems exchange " heartbeat " packets over the network to determine if the peer is still alive.

Network Failover: This involves the exchange of UDP packets (typically on port 1026) at regular intervals.

Device Service Clustering (DSC): Modern BIG-IP versions use the Central Management (cm) infrastructure to communicate configuration status and sync status constantly.

Clarification on others: Port lockdown does affect HA communication if misconfigured (A is false). Mirroring uses separate channels (B is false). Mirroring is never sent over the serial cable because it requires high bandwidth (D is false).

Configuring networking objects in BIG-IP requires using the correct TMSH module path and verb .

Module Path: Trunks are networking objects, so they reside under the /net module, not /sys.

Verb: Since the trunk already exists, the modify verb must be used to update its properties rather than create.

Syntax: The correct syntax to append physical interfaces to an existing trunk is tmsh modify /net trunk [name] interfaces add { [port list] }.

Data Plane Impact: Adding interfaces to a trunk (Link Aggregation) increases the total aggregate bandwidth available to the system and provides additional hardware redundancy.