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

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.

Cookie Persistence is a Layer 7 persistence method that leverages an HTTP cookie to track a user session.

IP Independence: Unlike " Source Address Affinity " (which relies on the client ' s IP), Cookie persistence identifies the session base 16 d on a unique token provided by the BIG-IP system. This is crucial for environments where many users share a single gateway (NAT) or where a client ' s IP might change mid-session.

Encryption and Decryption: For the BIG-IP to insert or read a cookie, it must be able to see the HTTP header. If the traffic is encrypted end-to-end (SSL Pass-through), the BIG-IP cannot use cookie persistence. SSL must be terminated at the BIG-IP (Option B is false).

Security: By default, BIG-IP cookies are encoded, not clear text. Modern versions allow for easy encryption of these cookies to prevent information leakage (Option C is false).

Memory vs. Disk: The default behavior is " session-based " (In-memory). A cookie is only written to the client ' s file system (disk) if an Expiration is configured in the persistence profile (Option D is false).

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.

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.

In a large-scale BIG-IP environment with hundreds of virtual servers, the Network Map is the most effective tool for visualizing and auditing the relationships between various ADC objects.

The Network Map Functionality: The Network Map provides a hierarchical view of the local traffic objects. It allows an administrator to see the status and dependencies of Virtual Servers, Pools, Pool Members, and associated iRules all in one screen.

Search and Filter: By navigating to Local Traffic > Network Map , the administrator can use the Advanced Filter . This feature allows for searching specifically for an iRule name or a string within an iRule definition. Once the filter is applied, the system displays only the Virtual Servers that are associated with that specific iRule.

Efficiency: While the " Virtual Server List " (Option D) can be customized to show columns for iRules, it is often cumbersome to scroll through hundreds of entries. The " iRules List " (Option B) displays the scripts themselves but does not provide a reverse-lookup list of all associated virtual servers in a single view as efficiently as the Network Map.

Summary of Relationships: The Network Map is specifically designed to answer the question, " What is this object connected to? " making it the primary administrative interface for impact analysis during configuration changes.

The configuration shown matches a Performance Layer 4 virtual server because it is explicitly using a FastL4 profile:

The screenshot shows Protocol: TCP and Protocol Profile (Client): fastL4 . In BIG-IP data plane terms, FastL4 is the hallmark of a Performance (Layer 4) virtual server, designed to process connections at Layer 4 with minimal overhead (high throughput/low latency) compared to full proxy L7 processing.

The screenshot also shows HTTP Profile (Client): None (and HTTP server profile effectively not in use). A Standard virtual server commonly uses full-proxy features and frequently includes L7 profiles (like HTTP) when doing HTTP-aware load balancing, header manipulation, cookie persistence, etc. In contrast, a Performance L4 virtual server typically does not use an HTTP profile because it is not doing HTTP-aware (Layer 7) processing.

It is not a Forwarding IP virtual server: A Forwarding (IP) virtual server is used to route/forward packets (often without load balancing to pool members in the same way as Standard/Performance VS) and is selected by choosing a forwarding type. The presence of a TCP protocol with a FastL4 client profile aligns with a Layer 4 load-balancing style virtual server, not a packet-forwarding virtual server type.

Conclusion: Because the configuration is TCP-based and explicitly uses fastL4 with no HTTP profile, the expected BIG-IP virtual server type is Performance Layer 4 (Option C) .

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.

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.

===========