F5CAB5 BIG-IP Administration Support and Troubleshooting (F5CAB5) exam Questions and Answers

When a BIG-IP device group shows aChanges Pendingstatus, it indicates that one or more devices in the group have configuration changes that have not yet been synchronized to the other members. To identifywhich device has the most recent (authoritative) configuration, the administrator must view the detailed synchronization status at thedevice group level.

The correct location isDevice Management > Device Groups (Option D). Within this menu, the BIG-IP Configuration Utility displays each device group along with its synchronization status and provides details about which device has pending changes. From this view, the administrator can clearly see which device is marked as havingchanges pending, making it the source device that should be used to initiate aSync to Groupoperation.

The other options do not provide the required level of detail:

Device Management > Overview (Option A)shows general HA status but not configuration ownership.

Device Management > Devices (Option B)lists devices but does not clearly identify which one holds unsynchronized changes.

System > High Availability (Option C)focuses on failover and traffic groups, not configuration sync state.

This workflow aligns with BIG-IP best practices for configuration synchronization and ensures changes are propagated correctly without overwriting newer configurations.

Comprehensive and Detailed 150 to 250 Words Explanation From BIG-IP Administration, Support, and Troubleshooting Documents:

AQKViewfile is the primary diagnostic support bundle used by F5 Support to troubleshoot BIG-IP system issues. It contains comprehensive system information, including running configuration, licensing details, module provisioning, hardware status, software versions, log files, statistics, and the output of numerous diagnostic commands. Generating a QKView is a standard and recommended first step when investigating performance problems, configuration issues, or when opening a support case with F5.

In the BIG-IP Configuration Utility (GUI), the correct and supported location to generate a QKView isSystem > Support. This menu is specifically designed for support and troubleshooting operations. From this section, administrators can generate a QKView file, monitor its creation progress, download it locally, or upload it directly to F5 iHealth for automated analysis. This workflow is clearly documented in BIG-IP Administration and Support guides and aligns with F5 best practices.

The other menu options are not appropriate:

System > Configurationis used for system-wide settings such as DNS, NTP, and device identity.

System > Archiveis used to create UCS backup files, which are configuration backups, not diagnostic bundles.

System > Logsis used only for viewing system logs, not generating support files.

Therefore,System > Supportis the correct and only valid answer.

In the BIG-IP Configuration Utility, the status icon (shape and color) provides immediate feedback on why a virtual server is not working as expected81. A "Red Diamond" indicates that the object is "Offline" and unavailable to process traffic82. For a virtual server, this specific status typically means it has inherited an offline state from its mandatory backend resources8383. If all pool members associated with the virtual server have failed their health monitors, the virtual server will transition to a red diamond status because it has no healthy destination for incoming requests. This is distinct from a "Black Circle," which would indicate the virtual server has been manually "Disabled" by an administrator85858585. To troubleshoot a red diamond, the administrator must examine the associated pool and its members to determine why the health monitors are failing (e.g., server crashes, network path failures, or incorrect monitor strings). Resolving the health check failures on the pool members will return the virtual server to an "Available" (Green) status.

These log messages indicate that the BIG-IP system is under significant resource pressure and has activated its Adaptive Connection Management.

Global Eviction Policy: The message Aggressive mode ... activated (global memory) confirms that the system has reached a memory utilization threshold that triggers the eviction policy. This happens because TMM (the data plane) is running low on available memory pages.

Sweeper/Reaping: Once in "Aggressive mode," the BIG-IP "sweeper" starts reaping (terminating) connections to free up memory. The log Connections killed confirms this is occurring.

Impact: The system does not drop all connections; it targets connections based on the eviction policy (e.g., oldest connections or those exceeding limits) to bring memory usage back to safe levels. Thus, some connections will be dropped (Option A), and the cause is TMM memory exhaustion (Option C).

F5 BIG-IP provides two distinct ways to throttle traffic on a Virtual Server: total capacity and velocity.

Connection Rate Limit: This setting specifically controls the number of new connection attempts per second. It is the correct tool for managing traffic spikes and protecting backend resources from being overwhelmed by a high frequency of new requests.

Comparison (Connection Limit): A standard Connection Limit (Option C) restricts the total concurrent connections allowed at any one time, regardless of how fast they arrive.

Other Profiles: OneConnect (Option A) is used for connection pooling and reuse to reduce server-side load, and HTTP Compression (Option B) reduces bandwidth usage but does not limit connection counts or rates.

To successfully performSSL offload and re-encryptionon a BIG-IP system, the virtual server must be configured withboth a Client SSL profile and a Server SSL profile. The Client SSL profile enables BIG-IP to decrypt inbound HTTPS traffic from clients, while the Server SSL profile is required tore-encrypt traffic before forwarding it to the pool members.

From the exhibit, the virtual server has aClient SSL profile configured, which allows BIG-IP to accept HTTPS connections from clients. However, there isno Server SSL profile attached, meaning BIG-IP attempts to sendunencrypted HTTP trafficto pool members listening on HTTPS (port 443). This protocol mismatch causes the server-side SSL handshake to fail, resulting in users being unable to connect to the application.

This behavior is well documented in BIG-IP SSL troubleshooting guides: when backend servers expect HTTPS, a Server SSL profile is mandatory to establish a secure connection from BIG-IP to the pool members.

The other options are incorrect:

Removing the Client SSL profile (Option A) would break client-side HTTPS.

The server-side TCP profile (Option B) is unrelated to SSL encryption.

Forward Proxy (Option C) is only used for outbound SSL inspection scenarios.

Therefore, configuring anSSL Profile (Server)is the correct and required solution.

The Local Traffic Manager (LTM) log file is the primary repository for all events related to load balancing objects, including virtual servers, pools, and nodes.

Monitor Logging: When a health monitor marks a pool member as "UP" or "DOWN," the system generates a log entry in /var/log/ltm.

Diagnosing Flaps: To troubleshoot "flapping" (frequent state changes), an administrator would look for messages like 01010028:3: Pool /Common/http_pool member /Common/10.10.1.1:80 monitor status down followed quickly by an "up" status. This log provides the timestamp and the specific monitor that triggered the state change.

Comprehensive and Detailed Explanation From BIG-IP A41dministration Support and Troubleshooting documents:To confirm functionality across a complex environment, the "Network Map" is the most efficient troubleshooting tool in the Configuration Utility43. It provides a hierarchical, visual representation of the traffic management objects44. A single glance allows the administrator to see the status of a Virtual Server (Green/Red/Yellow), the status of its associated pool, the health of individual pool members, and which iRules are currently attached45. This view is superior to the standard "Virtual Server List" for troubleshooting because it maps the dependencies between objects46. For example, if a Virtual Server is "Red," the Network Map will show if that status is inherited from a failed pool or a specific monitor failing on a pool member. Reviewing these basic stats in the Network Map helps the administrator quickly isolate whether a failure is at the service level (Virtual Server), the logic level (iRule), or the hardware level (Pool Member).

Identifying network-level performance issues often starts with investigating hardware-level alerts78. In F5 terminology, a "Link" like "1.0" or "1.1" refers to a physical interface on the appliance79. When an SNMP trap reports that a link is "DOWN," it indicates a loss of signal or an administrative shutdown of the physical port80. To verify this, the administrator must navigate to Network > Interfaces > Interface List81. This screen provides real-time status, showing whether the interface is "up," "down," or "uninitialized," as well as any media speed or duplex mismatches that could be causing performance degradation82. Troubleshooting this is the first step in resolving "pool member down" or "VLAN failsafe" issues, as a down interface will take down any VLANs associated with it, immediately halting all traffic flow for the services relying on that physical path.

The issue is caused by the Source Address restriction configured on the virtual server.

Source Filter: The configuration contains the line source 192.168.0.0/16. This acts as an implicit Access Control List (ACL). The virtual server will only accept and process TCP connections if the client's source IP address falls within the 192.168.x.x range.

Why Ping Works: ICMP (Ping) is handled by the Virtual Address object, not the Virtual Server object. Unless ICMP is specifically disabled on the Virtual Address, it will respond to pings from any subnet, even if the Virtual Server itself is restricted by a source filter or is even disabled.

Evaluation of Other Options:

Disabled (Option A): If the VS were disabled, the configuration would typically show disabled or state down, and the symptoms would be similar, but the source filter is a more specific "misconfiguration" in this context.

Port 80 (Option C): The configuration destination 10.99.20.50:http explicitly confirms it is listening on port 80.

Unallowed Subnet: If a client from a different network (e.g., 10.10.1.5) tries to connect, the BIG-IP will silently drop the connection or send a reset because it does not match the defined source criteria.

Comprehensive and Detailed Explanation From BIG-IP Administration Supp13ort and Troubleshooting documents: When troubleshooting a Virtual Server that is not working as expected, it is critical to ensure that the applied profiles match the type of traffic being processed. SSH (Secure Shell) is a non-HTTP protocol that operates over TCP. The exhibit indicates that an HTTP profile is applied to the Virtual Server14. An HTTP profile instructs the BIG-IP system to parse traffic as HTTP; however, since SSH traffic does not follow HTTP specifications, the BIG-IP's parser will fail to understand the data stream, typically resulting in dropped packets or reset connections15. To fix this, the administrator must set the HTTP profile to "None"16. This allows the Virtual Server to act as a "Standard" or "FastL4" listener that passes the encrypted SSH data transparently to the backend pool members without attempting application-layer inspection. This highlights a common troubleshooting step: verifying that L7 profiles are not inadvertently applied to L4 traffic, which disrupts the expected traffic flow between the client and the server.

The BIG-IP architecture is divided into two distinct planes: the Control Plane (Management) and the Data Plane (Traffic Management Microkernel - TMM).

Data Plane (TMM): This plane is responsible for the actual processing of application traffic, including load balancing, SSL offloading, and session management for modules like APM (Access Policy Manager). If data plane resources (CPU/Memory allocated to TMM) are exhausted, active user sessions and traffic throughput are directly degraded.

APM Sessions: Because APM sessions are managed within the TMM process to ensure high-speed access control and tunneling, they are a primary "Data Plane" function.

Control Plane Functions: Options A, B, and D (MCPD, Configuration Utility/GUI, and iControl) all reside in the Control Plane (running on the Linux host OS). While a total system hang affects both, a specific "data plane resource issue" is designed to isolate and impact the traffic-handling services like APM while the management GUI might remain responsive.

The failure of the Forwarding (IP) virtual server is caused by an incorrect Network Mask configuration for a wildcard destination.

Wildcard Destination: The administrator intends to create a "Wildcard" Virtual Server that listens for any destination IP address (0.0.0.0).

The Mask Conflict: A mask of 255.255.255.255 (or /32) tells the BIG-IP to look for a specific, single host address. When combined with 0.0.0.0, the system is literally looking for traffic destined for the IP 0.0.0.0, which is not a valid routable destination for standard traffic.

Correct Configuration: To allow the virtual server to catch traffic for any IP address, the mask must be changed to 0.0.0.0 (or /0). This signifies that the system should ignore all bits of the destination address and match everything.

Forwarding Logic: The rest of the configuration—including ip-forward (Forwarding IP type), translate-address disabled, and translate-port disabled—is correct for a BIG-IP acting as a router/gateway.