F5 101: What the Retired Application Delivery Fundamentals Exam Still Teaches

F5 exam 101, Application Delivery Fundamentals, was once the entry point to the F5 Certified Administrator, BIG-IP path. That changed on April 30, 2025, when F5 retired the exam and replaced the old two-exam administrator structure with five shorter BIG-IP administration exams. The historical F5 101 page therefore needs to be read as a legacy resource, not as a current scheduling target.

Retirement does not make the knowledge useless. The old 101 exam forced candidates to understand the networking, protocol, traffic-management, security, and application-delivery foundations that explain why BIG-IP behaves the way it does. Those fundamentals still matter in the current F5 program, but the certification structure now tests them in a more focused way.

The best use of 101 material today is to treat it as a conceptual foundation. If you are starting the current administrator path, use the old exam topics to strengthen weak networking knowledge, then align your preparation with F5CAB1 through F5CAB5. If you passed 101 while it was active and still have valid eligibility for 201, a different transition rule may apply.

Why F5 retired 101

F5 redesigned the Certified Administrator, BIG-IP credential after reviewing the existing 101 and 201 structure. Instead of two long exams, the current credential uses five 30-minute exams that separate installation and upgrade, data-plane concepts, data-plane configuration, control-plane administration, and troubleshooting. F5 has said the updated format was intended to make the assessment more relevant and focused while preserving the validity of the certification.

That change also removed much of the broad application-delivery-controller content from the administrator assessment. Under the old model, 101 spent significant attention on networking and ADC foundations because candidates needed a common base before moving to TMOS administration. Under the new model, those concepts are distributed more directly around what a BIG-IP administrator actually does.

This is why a current candidate should not prepare as though passing 101 is still the first step. The F5 certification path now points new administrator candidates to F5CAB1, F5CAB2, F5CAB3, F5CAB4, and F5CAB5, which may be taken in any order.

The old exam still exposes networking gaps quickly

Application delivery makes little sense without networking. A load balancer sits in the traffic path, makes decisions about destinations and connections, and often terminates or re-encrypts application traffic. If a candidate cannot reason about IP addressing, routing, ports, TCP state, DNS, or the OSI layers, BIG-IP configuration becomes a sequence of memorized screens rather than an understandable system.

Revisiting the OSI and TCP/IP models is therefore still useful. The goal is not to recite all seven OSI layers from memory; it is to trace what changes as traffic moves from a client toward an application. You should be able to separate a Layer 2 reachability problem from a routing problem, a transport problem, a TLS problem, and an application-layer problem.

The same is true for TCP and UDP. BIG-IP behavior depends heavily on connection-oriented and connectionless traffic characteristics, profile selection, persistence, timeouts, and how application flows are created. A candidate who understands TCP and UDP behavior can reason through scenarios instead of relying on product-specific vocabulary alone.

Application delivery is more than round-robin load balancing

One of the enduring lessons from 101 is that an application delivery controller is not merely a device that rotates requests among servers. It can make traffic decisions using health, connection state, persistence, protocol information, application awareness, SSL/TLS handling, profiles, and policy. It also sits at an operational boundary where network and application teams often meet.

A useful mental model is client → virtual service → traffic policy/profile decisions → pool → selected pool member. Around that path sit health monitoring, address translation, persistence, encryption, availability, and observability. Once that model is clear, many BIG-IP terms stop feeling independent.

The broader discussion of load balancers, DNS, and application traffic delivery is a good way to place BIG-IP in a modern architecture. Cloud services have changed where load balancing occurs, but the core questions remain: where does a client connect, how is a healthy destination selected, what state must persist, and how is failure handled?

Security fundamentals remain part of administration

Application delivery devices frequently handle TLS certificates, encrypted sessions, management interfaces, and sensitive traffic. The old fundamentals exam expected candidates to understand why encryption, authentication, and trust matter. Current BIG-IP exams continue that operational emphasis, especially around securing management access and applying appropriate profiles.

For study purposes, make sure you can distinguish encryption from authentication and understand where TLS is terminated. A client-side SSL profile and a server-side SSL profile solve different parts of the communication path. If BIG-IP decrypts traffic from the client and then creates a separate encrypted session to a pool member, it participates in two TLS relationships, each with its own certificates and trust requirements.

That is why a clear grasp of SSL and TLS remains useful even though 101 itself is retired. F5 product knowledge becomes easier when the underlying security protocol is understood first.

Map legacy 101 knowledge to the current five-exam administrator series

The current F5 Certified Administrator, BIG-IP path is a much better organizing structure for preparation. F5CAB1 focuses on installation, initial configuration, security, licensing, software images, and provisioning. F5CAB2 focuses on data-plane concepts such as interfaces, VLANs, self IPs, routes, ADC objects, traffic behavior, virtual server types, and high availability.

F5CAB3 moves into data-plane configuration of virtual servers and pools. F5CAB4 covers control-plane administration including HA state, device status, logs, UCS archives, authentication, system services, configuration synchronization, and upgrade decisions. F5CAB5 focuses on support and troubleshooting.

That mapping makes old 101 material useful without confusing it with the current exam path. Networking theory that once sat inside a broad fundamentals exam now supports several more focused exams. The study strategy should follow the current blueprint while using 101 as background where needed.

Historical candidates and new candidates should make different decisions

If you never passed 101, there is no reason to chase the retired exam. Start with the current administrator series. If you passed 101 before retirement and have active eligibility for 201, F5 still allows eligible candidates to complete the legacy route. That exception exists because F5 did not want candidates who had already passed the first exam to lose their progress immediately.

Do not assume eligibility simply because you once studied 101. The 201 route is limited to candidates with active eligibility generated by a valid 101 passing result. Everyone else should use the five-exam structure.

There is also a lesson here about certification maintenance. F5 now has a dedicated F5CABR recertification exam for people who have previously achieved the administrator credential. Recertification no longer depends on repeating the old 201 exam.

Study the fundamentals as operating knowledge, not historical trivia

The strongest reason to revisit F5 101 is practical. BIG-IP administrators still need to troubleshoot real traffic. They still need to understand how a client reaches a virtual server, how the system selects a pool member, why a route or VLAN matters, what a TCP profile changes, where TLS is terminated, and how health monitors influence availability.

Build a small set of diagrams and explain them without product documentation. Trace a successful flow and then break one component at a time: wrong route, down interface, unhealthy pool member, certificate mismatch, incorrect service port, persistence sending traffic somewhere unexpected. This converts networking theory into diagnostic reasoning.

F5 101 has retired, but its best material remains valuable because application delivery still rests on the same foundational layers. Use the page as a bridge into current BIG-IP administration rather than as a current exam target, and your preparation will stay both historically accurate and technically useful.

One practical way to use legacy 101 material is to build a prerequisite checklist before touching the current exam blueprints. Can you subnet comfortably? Can you explain the difference between a routed path and a switched segment? Can you describe what happens in a TCP handshake, what a DNS lookup returns, and why a TLS certificate is trusted? Can you trace a request through a load balancer without relying on vendor terminology? If any of those answers are weak, fix the fundamentals first.

This prevents an expensive study mistake: trying to memorize BIG-IP object names while the underlying network model remains fuzzy. Current F5 exams assume candidates can apply concepts, so a weak foundation appears later as confusion about VLANs, self IPs, routes, virtual servers, pool members, persistence, and profiles. The old 101 material is valuable precisely because it exposes those gaps early.

Keep the historical boundary clear in your notes. Label 101 as retired, label the five F5CAB exams as the current administrator route, and date any scheduling or pricing information you record. That small discipline prevents older study guides, videos, or forum posts from quietly steering you toward an exam path that no longer exists for new candidates.

That distinction also helps when reading older community advice: preserve the technical insight, but verify the exam path against current F5 sources before acting on it.

The fundamentals remain useful because modern BIG-IP administration still depends on understanding the traffic path beneath the interface.