F5 certification now uses a modular BIG-IP administrator pathway
F5 certifications are intended for engineers who operate and secure application-delivery infrastructure, including BIG-IP traffic management, availability, DNS services and access controls. Understanding the credential structure matters because F5 changed a foundational part of its program. Since May 1, 2025, new candidates pursuing F5 Certified Administrator, BIG-IP no longer follow the familiar two-exam sequence of 101 Application Delivery Fundamentals followed by 201 TMOS Administration. Instead, the current administrator route is organized into five smaller, topic-specific exams.
The 101 exam retired on April 30, 2025. Examination 201 remains available only to qualifying candidates who passed 101 previously and are still within the permitted eligibility window. New entrants should not plan to register for 101 or assume that a fresh 101-plus-201 path is available. F5’s revised series is F5CAB1 through F5CAB5, covering installation and upgrade, data-plane concepts, data-plane configuration, control-plane administration, and support and troubleshooting. Existing holders and transitional candidates should consult F5 directly about their specific eligibility and renewal provisions.
Why application delivery knowledge is valuable
Application delivery controllers sit between clients and backend applications, making decisions about routing traffic, availability, encryption and sometimes access policy. An engineer needs to understand the relationship among virtual servers, pools, pool members, monitors, persistence, network address translation and client/server protocols. Misconfiguring one of those elements can cause intermittent failures that are harder to diagnose than a complete outage, especially when a service appears healthy from one location and inaccessible from another.
F5 skills matter most when the engineer can explain the full request path. A client connects to an address and port, the system selects a virtual server and applies relevant profiles and policies, chooses a backend pool member, and maintains the session according to the persistence configuration. Logging and packet traces can then be used to diagnose where the failure occurred. Candidates who understand this flow can reason about load balancing and security controls rather than relying on memorized console screens. That knowledge supports operations in finance, healthcare, ecommerce and other application-dependent environments.
F5CAB1: installation, initial configuration and upgrades
F5CAB1 addresses bringing a BIG-IP system into a manageable state. An administrator must understand management connectivity, initial network interfaces, licensing prerequisites, fundamental system configuration and safe upgrade planning. A change that looks routine can have a significant service impact if it alters the management path, breaks synchronization or introduces a version compatibility problem in a high-availability pair.
Preparation should include a controlled maintenance scenario. Record the existing software version and relevant configuration, identify expected service behavior during the change, verify that backups can be restored and confirm the health checks needed afterward. Running an upgrade without a rollback path leaves the engineer unable to respond when traffic behavior differs from the plan. F5CAB1 learning is useful because reliable application delivery begins with disciplined platform lifecycle management, not just successful initial installation.
F5CAB2: understanding the BIG-IP data plane
The data plane processes the traffic flowing through a BIG-IP device. Candidates should be comfortable distinguishing virtual addresses and virtual servers, backend pool members, nodes, traffic profiles and the translation mechanisms that let clients reach application services. A protocol-aware load balancer can inspect and manage more than a simple network forwarding device, which means configuration details such as HTTP profile behavior, SSL termination and connection reuse can change how an application behaves.
Consider a web application whose backend hosts pass a health monitor but users still receive incomplete responses. The administrator must evaluate whether the problem is caused by an inappropriate monitor, a persistence decision, a protocol profile or a backend behavior invisible to a basic port check. Understanding each traffic-processing stage makes troubleshooting more systematic. The purpose of F5CAB2 is to connect those data-plane elements into a coherent model before making higher-risk changes in production.
F5CAB3: configuring traffic processing
F5CAB3 turns that conceptual model into working application delivery. Engineers create virtual servers and pools, select health monitors, apply protocol and SSL profiles, and decide when session persistence is needed. A well-designed configuration should reflect application requirements rather than assume that the same load-balancing method is appropriate for every workload. Transactional applications may require particular session behavior, while stateless services can tolerate a different distribution policy.
In a lab, build a simple two-node backend service and observe how a virtual server chooses healthy members. Intentionally fail one member and verify that the expected traffic shift occurs. Then change an SSL or persistence setting and inspect the application impact. The exercise should end with a short record of the desired behavior, the configuration responsible for it and the signals that demonstrate success. F5CAB3 skills are valuable because they make application availability predictable and explainable.
F5CAB4: control-plane administration and secure operations
F5CAB4 concerns the system’s management, configuration and administrative behavior. Privileged access, role assignment, interface reachability, configuration backup, system logging and high-availability synchronization all affect whether a BIG-IP platform can be safely operated. An engineer should know which management operations can change live traffic and which actions require a maintenance window or peer coordination. Least-privilege accounts and auditable changes reduce the risk that normal troubleshooting becomes an uncontrolled production event.
A useful scenario is a configuration change performed in an active/standby device pair. The administrator needs to understand how changes synchronize, what happens if the peers become inconsistent and how to verify that failover will not introduce different application behavior. Backups and change records should be checked before the modification, not constructed after an outage. F5CAB4 preparation therefore belongs in the same operational discipline as patching and disaster recovery, because reliable administration must survive individual operator mistakes and device failures.
F5CAB5: support and troubleshooting
F5CAB5 addresses the engineer’s ability to diagnose a failing system and communicate findings accurately. Troubleshooting begins by narrowing the fault: client connection, virtual-server listener, protocol processing, monitor status, pool selection, backend reachability or application response. A packet trace can reveal whether a connection is reset or translated differently than expected; device logs may expose SSL, configuration or resource problems. A successful investigator correlates these signals with the time and scope of the reported failure.
Practice should deliberately create distinguishable symptoms. Disable a pool member, configure an overly strict health check, introduce an SSL mismatch and simulate a failed node. For each scenario, record what users observe, which BIG-IP objects need inspection and which evidence confirms the root cause. Restore the expected configuration and verify end-to-end service behavior rather than declaring success after a single green dashboard indicator. These exercises develop the practical competence that a modular certification is meant to demonstrate.
Specialist tracks build on application-delivery expertise
After foundational BIG-IP administration, F5 offers more specialized credentials and learning paths in traffic management, DNS, access policy and application security. The exact prerequisites depend on the current program and should be verified rather than copied from an old certification map. Engineers working with local traffic management need strong knowledge of application behavior, persistence, SSL and advanced troubleshooting. DNS-related work requires understanding of authoritative DNS, service availability and geographically distributed responses. Security and access tracks introduce different policy, identity and threat-management concerns.
The job role should guide specialization. Someone supporting a load-balanced internal application estate may benefit more from LTM troubleshooting than from an advanced security track unrelated to their duties. A security engineer responsible for protecting public web applications needs to connect traffic handling with web application policy and incident-response processes. Selecting a credential on the basis of actual platform responsibilities reduces the risk of studying a collection of features that cannot be applied or demonstrated at work.
Building a realistic F5 study environment
A useful lab does not need to reproduce an entire enterprise network, but it must expose the fundamental traffic path. Prepare a simple application with two backend instances, one F5 BIG-IP system or appropriately licensed lab equivalent, and test clients on different networks. Establish a baseline response, add a monitored pool and virtual server, then examine what happens when a member becomes unhealthy or a persistence rule changes. Use authorized test systems and avoid touching real customer traffic without an approved maintenance process.
Document the configuration as if another engineer would inherit it. Include interface and virtual-server diagrams, the reason for each monitor, an explanation of protocol profiles and the recovery steps for common failure cases. Test both successful and failed client requests. This portfolio of practical decisions is more informative than a list of screens and can guide preparation across F5CAB2, F5CAB3 and F5CAB5 while reinforcing the safety principles of the other modules.
Choosing the right current F5 credential
Start by checking F5’s current learning-path and certification pages. For a new BIG-IP administrator candidate, the five-exam F5CAB structure is the relevant route; exams can be taken in any order according to F5’s program rules. Individuals with prior 101 results or an existing administrator credential should confirm whether transitional 201 eligibility or recertification options apply to them. The current internal exam inventory includes F5CAB1 , F5CAB3 , F5CAB4 , and F5CAB5 ; unavailable inventory destinations must not be invented for other modules.
The purpose of certification is to validate applied skill in preserving service availability and security. Keep training aligned to real platform versions, approved maintenance procedures and the application risks your role actually owns. By treating the retired 101/201 structure as historical and using the current modular exam requirements, a candidate can invest in knowledge that is both test-relevant and useful during real incidents and changes.
