Key details for this exam, checked against the published exam outline
Each question shows the correct answer and an explanation of why it is right
What type of virtual server should be used to load balance UDP traffic without considering previous connections?
When handling high-volume UDP traffic where the BIG-IP does not need to maintain any session history or relationship between packets, a Stateless virtual server is the appropriate choice.
No Connection Tracking: A stateless virtual server does not create or maintain entries in the BIG-IP connection table. This means the system processes each packet as an individual event, without 'considering previous connections' or packets from the same source.
High Performance: Because the system bypasses the overhead of state management, stateless virtual servers provide the highest possible throughput for UDP and ICMP traffic.
Use Cases: This is ideal for services like DNS (stateless queries) or some types of syslog traffic where each packet is independent and doesn't require the persistence or protocol inspection typically provided by a full-proxy.
Why other options are incorrect:
Forwarding: While a Forwarding (IP) virtual server can handle UDP, it still maintains a state entry in the connection table to ensure return traffic is handled correctly.
Standard: This is a full-proxy virtual server. It is inherently stateful and requires a connection table entry for every flow it manages.
Reject: This is a special virtual server type that simply drops incoming traffic and, in the case of TCP, sends a reset (RST) or, for UDP, sends an ICMP unreachable message. It is not a load balancing type.
A development team needs to apply a software fix and troubleshoot one of its servers. The BIG-IP Administrator needs to immediately remove all connections from the BIG-IP system to the back-end server. The BIG-IP Administrator checks the Virtual Server configuration and finds that a persistence profile is assigned to it. What should the BIG-IP Administrator do to meet this requirement?
Managing the lifecycle of a pool member requires understanding the difference between 'Disabled' and 'Forced Offline' states, especially when persistence is involved.
Disabled (User-Disabled): This state allows existing connections and persistent sessions to continue until they naturally time out or are closed by the client/server. It only prevents new sessions from being established.
Forced Offline: This state is more restrictive; it allows existing connections to complete but rejects all new connections, including those with existing persistence records.
Immediate Removal: Neither 'Disabled' nor 'Forced Offline' will instantly kill currently active, established TCP connections. To meet the requirement of 'immediately' removing all connections, the administrator must first set the member to Forced Offline (to prevent persistence from bringing in new traffic) and then use the command line (e.g., tmsh delete sys connection ss-server-addr [IP]) to clear the current connection table entries.
Which of the following lists the order of preference from most preferred to least preferred when BIG-IP processes and selects a virtual server? (Choose one answer)
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.
A BIG-IP Administrator assigns the default http health monitor to a pool that has three members listening on port 80. When the administrator connects to each pool member via the CURL utility, two of the members respond with a status of 404 Not Found while the third responds with 200 OK. What will the pool show for member availability?
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 BIG-IP Administrator is making adjustments to an iRule and needs to identify which of the 235 Virtual Servers configured on the BIG-IP device will be affected. How should the administrator obtain this information in an efficient way?
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.
Which virtual server type is being configured in the screenshot? (Choose one answer.)
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).
Exam domains verified against: Official F5 Networks F5CAB2 exam guide, last checked September 2026.
Understand how trunk configurations enable multiple VLANs to share physical interfaces in BIG-IP deployments. Learn to assign VLANs to interfaces and trunks, identify which VLAN and egress route handles specific traffic patterns, and distinguish between tagged and untagged VLAN handling.
Grasp the core functions of application delivery controllers including intelligent load balancing algorithms and server selection mechanisms. Study the key features and business benefits that ADCs deliver for optimizing application performance and availability.
Sample question from this domain above: Q1
Predict how persistence profiles redirect existing connections and analyze packet processing order with wildcard virtual servers. Evaluate how status changes in virtual servers, pools, and pool members affect traffic flow and identify when connection or rate limits trigger.
Sample question from this domain above: Q6
Classify virtual servers into Standard, Forwarding IP, Stateless, Reject, Performance Layer 4, and Performance HTTP categories. Understand the distinct packet handling and use case for each type in data plane operations.
Sample question from this domain above: Q4
Learn the mechanisms that ensure HA integrity and maintain synchronized state across redundant systems. Examine the advantages of redundant deployments in preventing single points of failure and meeting service continuity requirements.
Sample question from this domain above: Q2
Common questions about the exam itself
