The F5CAB5 exam validates your ability to support and troubleshoot BIG-IP systems in production environments. Designed for network administrators and F5 professionals, this certification demonstrates competency in diagnosing performance issues, resolving configuration problems, and maintaining optimal load balancing operations. This page outlines the exam syllabus, question formats, and practical study strategies to help you prepare efficiently for the F5 Certified Administrator, BIG-IP Certification path offered by F5 Networks.
Use this topic map to guide your study for F5 Networks F5CAB5 (BIG-IP Administration Support and Troubleshooting) within the F5 Certified Administrator, BIG-IP Certification path.
The F5CAB5 exam combines knowledge-based and scenario-driven questions to assess both your understanding of BIG-IP concepts and your ability to apply them to real-world troubleshooting situations.
Questions progress in difficulty, starting with foundational concepts and advancing to complex multi-step troubleshooting that mirrors production support responsibilities.
Structure your study around the seven core topics, dedicating focused time to hands-on practice and scenario analysis. A systematic approach helps you build both conceptual understanding and practical troubleshooting skills needed for the exam and real-world work.
Explore other F5 Networks certifications: view all F5 Networks exams.
Strengthen your preparation with up-to-date resources from validexamdumps.com. These materials align to F5CAB5 and cover practical scenarios with clear explanations.
Visit the exam page to download the PDF, Online Practice Test, or get a bundle discount for both formats: BIG-IP Administration Support and Troubleshooting.
Virtual server and pool troubleshooting typically account for a significant portion of the exam, as these are core to daily BIG-IP administration. Network performance identification and statistics interpretation also appear frequently because they directly support real-world support scenarios. Allocate study time proportionally to these high-impact areas.
High resource utilization often manifests as network performance degradation. When CPU or memory reaches capacity, BIG-IP may drop connections, increase latency, or fail to process requests efficiently. Understanding this relationship helps you diagnose whether a performance issue stems from infrastructure limits or configuration problems.
Practical experience with virtual server configuration, pool management, and basic troubleshooting is valuable but not mandatory if you study the exam topics systematically. Prioritize labs that let you review statistics, interpret logs, and navigate the BIG-IP interface. Even simulated environments help you build the diagnostic mindset needed for the exam.
Candidates often confuse virtual server and pool configuration issues, overlook the role of health checks in pool problems, or misinterpret statistics without considering context. Another frequent error is assuming a single root cause when troubleshooting complex scenarios. Always review the full system state before selecting your answer.
Shift from learning new content to drilling weak areas identified in practice tests. Take at least two full-length timed mocks and review every incorrect answer. Spend 15-20 minutes daily reviewing scenario-based questions to sharpen your diagnostic reasoning. Avoid cramming new topics; instead, consolidate what you already know.
A BIG-IP Administrator needs to collect HTTP status code and HTTP method for traffic flowing through a virtual server.
Which default profile provides this information? (Choose one answer)
To collect application-layer details such asHTTP status codes(200, 404, 500, etc.) andHTTP methods(GET, POST, PUT, DELETE), the BIG-IP system must use a profile designed for traffic visibility and reporting rather than basic traffic handling. TheAnalytics profile (Option C)is the correct choice because it is specifically designed to collect, store, and present detailed statistics about HTTP and TCP traffic passing through a virtual server.
When an Analytics profile is attached to a virtual server, BIG-IP can record metrics such as HTTP response codes, request methods, URI paths, latency, throughput, and client-side/server-side performance data. These statistics are then accessible through the BIG-IP GUI underStatistics Analytics, allowing administrators to validate application behavior and troubleshoot performance or functional issues.
TheHTTP profile (Option B)enables HTTP protocol awareness and features like header insertion and compression, but it does not provide historical or statistical reporting of HTTP methods and response codes.Request Adapt (Option A)is used for ICAP-based content adaptation, not visibility.Statistics (Option D)is not a standalone profile and does not provide HTTP-level insight.
Therefore, the Analytics profile is the only default profile that fulfills this requirement.
Due to a change in application requirements, a BIG-IP Administrator needs to modify the configuration of a Virtual Server to include a Fallback Persistence Profile. Which persistence profile type should the BIG-IP Administrator use for this purpose?
Comprehensive and Detailed Explanation From BIG-IP Administration S73upport and Troubleshooting documents: Persistence is critical for ensuring that a client's session remains with the same pool member throughout its duration. If primary persistence (like Cookie Persistence) fails---for instance, because the client has disabled cookies---load balancing will not work as expected, and the session may be broken. A 'Fallback Persistence Profile' provides a backup method75. The most common and reliable fallback method is 'Source Address Affinity'76. This method tracks the client's IP address in the BIG-IP's persistence table and ensures that any subsequent requests from that IP are routed to the same pool member, even if the primary persistence token is missing. Troubleshooting session drops often involves checking if a fallback method is configured to handle scenarios where the primary method is unsupported by the client's browser or environment. Without a fallback, the BIG-IP would revert to standard load balancing, potentially sending the client to a different server that lacks their session data.
A BIG-IP Administrator is receiving intermittent reports from users that SSL connections to the BIG-IP device are failing. Upon checking the log files, the administrator notices: SSL transaction (TPS) rate limit reached. Reviewing stats shows a max of 1200 client-side SSL TPS and 800 server-side SSL TPS. What is the minimum SSL license limit capacity required to handle this peak?
Troubleshooting SSL connection resets often involves verifying license limits against actual resource utilization. F5 devices use a 'Transactions Per Second' (TPS) license to control the amount of SSL processing the device can handle. The log entry SSL transaction (TPS) rate limit reached is a clear indicator that the traffic volume has exceeded the licensed capacity. When determining the necessary license level, it is important to know that F5 primarily licenses and limits the 'Client-side' SSL TPS---which represents the encrypted connections between the users and the virtual servers. In this specific scenario, the peak demand reached 1200 client-side transactions per second. Although there were also 800 server-side transactions (re-encryption from the BIG-IP to the pool), these typically do not count against the primary TPS license limit in the same manner. Therefore, to ensure that the virtual server works as expected during peak load, the administrator must upgrade the license to at least 1200 TPS. This troubleshooting process links system log errors to license-enforced resource constraints.
Which two methods should the BIG-IP Administrator troubleshoot a Pool-member that's been marked "DOWN" by its Health Monitor? (Pick the 2 correct responses below)
When a health monitor marks a member 'Down,' the goal is to determine if the issue is at the network level or the application level.
Monitor Logging (Option A): In the Pool Member configuration, an administrator can enable 'Monitor Logging'. This generates a detailed text file in /var/log/monitors/ that shows the exact 'Send' string sent by the BIG-IP and the exact 'Receive' string (or lack thereof) returned by the server.
TCPdump (Option C): This is the most definitive way to see if the monitor traffic is even leaving the BIG-IP and if the server is responding with a TCP RST (reset) or an ICMP unreachable message. A command such as tcpdump -ni <vlan> host <member_ip> and port <member_port> is standard for this task.
Why not others? While the routing table (Option B) is useful for general connectivity, if other members in the same subnet are 'Up,' the routing is likely fine. Statistics (Option D) show that it is down but rarely why it is down at a protocol level.
A custom HTTP monitor is failing to a pool member 10.10.3.75:8080 that serves up www.example.com. A ping works to the pool member address. The SEND string is: GET / HTTP/1.1 \r\nHost: www.example.com\r\nConnection: Close\r\n\r\n. Which CLI tool syntax will show whether the web server returns the correct HTTP response?
To manually verify a health monitor's 'Send String' from the BIG-IP command line, the curl utility is the preferred tool because it allows for custom header insertion.
Matching the Monitor String: The monitor string requires an HTTP/1.1 request which must include a 'Host' header. Option A correctly uses the --header (or -H) flag to pass Host: www.example.com to the specific IP and port of the pool member.
Troubleshooting Logic: If curl --header 'Host: www.example.com' 'http://10.10.3.75:8080/' returns a '200 OK' but the BIG-IP monitor still shows 'Down,' the administrator should check if the Receive String in the monitor configuration matches the output provided by curl.
Invalid Syntax: Option D is incorrect because it tries to append the hostname to the URI path, which the web server will likely reject with a '404 Not Found'. tracepath (Options B and C) is a path discovery tool similar to traceroute and cannot validate HTTP response content.
