Search for F5 Certified Administrator BIG-IP exam questions and answers and you'll mostly find dump sites promising the real paper. Skip them — F5 rotates its pools, the certification agreement forbids it, and memorised answers to retired questions are worse than useless because false recognition makes you answer fast and wrong.
What actually helps is knowing the shapes of questions F5 asks. There are about seven recurring ones. Learn to recognise them and the exam gets substantially more predictable.
First, the logistics.
The certification path
F5 Certified Administrator, BIG-IP historically required two exams: 101 Application Delivery Fundamentals and 201 TMOS Administration. Note a real change — under the current program, passing 201 is no longer required for the recertification path, so verify the current requirements on F5's certification site before you plan your spend. Programs shift and blog posts age badly.
Exam 201 essentials:
- Duration: 90 minutes
- Format: multiple choice
- Passing score: scaled 245 (roughly 69%)
- Cost: about $100 USD online-proctored via Certiverse, around $130 at a test centre
- Partial credit: none — questions score whole
Scaled scoring at 245 means you can't compute your standing from raw counts, so don't try to game it during the exam. Answer everything; there's no penalty for a guess.
Diagnostic questions: free practice tests.
The seven question types
1. "Traffic arrives — trace the path"
The most common shape on the exam. A packet hits a virtual server; you're asked what happens next, or where it went wrong.
You must own the order of operations: virtual server matching (most specific match wins), then iRules, then the pool, then the load balancing method, then the persistence check, then SNAT, then the node. Know which order persistence and load balancing evaluate in — persistence is checked first, and if an existing persistence record matches, the load balancing method is bypassed entirely. That single fact resolves a surprising number of questions.
2. "Why is the pool member down?"
Health monitor questions, and they're everywhere. Know monitor types (ICMP, TCP, HTTP, HTTPS, and application-specific), the meaning of interval and timeout and the standard 3n+1 relationship, the difference between send and receive strings, and what a receive-disable string does.
Then know the state vocabulary precisely, because F5 distinguishes them and the exam tests the distinction: available (green), offline (red), unknown (blue — no monitor assigned), disabled (black), and forced offline. "Blue means no monitor" is a free point that people miss.
3. "Which persistence profile?"
Source address affinity, cookie persistence (and its variants — HTTP cookie insert, rewrite, passive), SSL session ID, universal, destination address. Scenario tells you the constraint — clients behind a shared NAT, or an application that can't tolerate cookies, or SSL passthrough — and you pick accordingly.
Classic trap: source address persistence with clients behind a large corporate NAT, which collapses everyone onto one pool member. If the scenario mentions a proxy or NAT, source address is usually the wrong answer.
4. "Where does SNAT apply, and what breaks?"
SNAT questions test whether you understand return-path routing. Know Automap versus a SNAT pool versus no SNAT, and — most importantly — the consequence: with SNAT, the pool member sees the BIG-IP's address as the client, so the original client IP is lost unless you insert X-Forwarded-For.
The question is often phrased as "the application logs show all requests coming from one IP; why?" That's SNAT, and the fix is an HTTP profile with X-Forwarded-For enabled.
5. "Which profile does this?"
Profiles are BIG-IP's configuration model and the exam expects fluency. TCP, HTTP, Client SSL versus Server SSL, OneConnect, compression, persistence profiles.
Understand profile inheritance — child profiles inherit from parents, and changing a parent propagates to children that haven't overridden the value. And understand the Client SSL / Server SSL split: Client SSL terminates the client's connection, Server SSL re-encrypts to the pool member. SSL bridging needs both; SSL offload needs only Client SSL.
OneConnect appears regularly too: it multiplexes client connections onto fewer server-side connections, and it needs an HTTP profile to work properly on HTTP traffic.
6. "How do you back up / upgrade / recover this?"
Operational questions. Know what a UCS archive contains (full system configuration including certificates and keys) versus an SCF (single configuration file, portable text). Know where config lives — bigip.conf, bigip_base.conf. Know boot locations and how volumes work in an upgrade, and how to roll back.
Also basic CLI: tmsh navigation, save sys config, load sys config, and the bigstart commands for service state.
7. "Read this log / diagnose this symptom"
You'll get a symptom — intermittent failures, an SSL handshake error, a virtual server that doesn't respond — and pick the most likely cause. This rewards having actually operated a BIG-IP. Know tcpdump on the F5, know what /var/log/ltm gives you, and know the difference between a virtual server that's unavailable versus one whose pool has no available members.
How to prepare without dumps
Get hands on the box. F5 offers trial and lab options, and BIG-IP Virtual Edition can be run in a lab environment. Build one virtual server, one pool, two nodes, one monitor. Then break each piece deliberately — remove the monitor, misconfigure the receive string, disable a member — and watch the status change. Two evenings of this beats two weeks of reading.
Read the official study guides. F5 publishes blueprint-aligned study guides for 101 and 201 free of charge. They are dry and they are exactly what's tested. Read the blueprint objectives and check off each one honestly.
Drill the vocabulary. F5 has strong opinions about terminology — node versus pool member versus pool, virtual server versus virtual address. Questions exploit imprecision. If you use these terms loosely at work, tighten them for the exam.
Post-mortem every wrong answer. For each miss, write down the specific distinction you failed to make. After thirty of those, your errors will cluster into two or three concept pairs, and you drill those instead of grinding random questions. Question banks that explain their reasoning make this loop much faster — ai.examcert.app explains each option, which is genuinely useful on the trace-the-path questions where three answers look plausible.
Is it worth it?
If you administer F5 gear or work somewhere that does, yes — it's one of the more respected vendor credentials in networking, and roles that want it specifically want it. It's also a gateway to the specialist tracks (LTM, GTM/DNS, ASM/Advanced WAF), where the real market value sits.
If you're a generalist network engineer with no F5 in your environment, the ROI is thin. Learn the concepts, skip the badge.
Two or three weeks with lab access is a realistic timeline for 201 if you already work with load balancers. Six to eight weeks if you're starting from application-delivery fundamentals.
Full breakdown and practice questions: F5 Certified Administrator BIG-IP exam guide.
Top comments (0)