F5 201 Exam Overview:
| Certification Vendor: | F5 Networks |
| Exam Name: | TMOS Administration (201) |
| Exam Number: | 201 |
| Exam Duration: | 90 minutes |
| Certificate Validity Period: | 2 years |
| Exam Price: | USD 180 |
| Passing Score: | 245 / 350 (scaled, approx 70%) |
| Related Certifications: | F5 Certified Technical Professional F5 Certified Technical Specialist F5 Certified Security Solutions Expert |
| Available Languages: | English |
| Real Exam Qty: | 80 (70 scored, 10 unscored) |
| Exam Format: | Multiple choice, Scenario-based |
| Recommended Training: | F5 Certified Study Guide Administering BIG-IP Official Training |
| Exam Registration: | Pearson VUE Registration Certiverse Registration F5 Education Exam Page |
| Sample Questions: | F5 201 Sample Questions |
| Exam Way: | Online proctored or in-person at Pearson VUE / Certiverse test centers |
| Pre Condition: | Valid only for candidates who passed Exam 101 (Application Delivery Fundamentals) before May 1, 2025 and retain active eligibility; retired for new candidates after that date |
| Official Syllabus URL: | https://education.f5.com/exams/tmos-administration-201 |
F5 201 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
| Topic 6 |
|
| Topic 7 |
|
| Topic 8 |
|
Reference: https://support.education.f5.com/hc/en-us/articles/4403999362715-TMOS-Administration-201
Introduction to F5-201: TMOS Administration Exam
The qualified candidate is capable of performing day-to-day operations of TMOS-based devices which have already been installed. They are also capable of basic troubleshooting of a TMOS-based device in order to provide full, accurate, and appropriate information to senior engineers and/or F5 Support.
They can do any of the following without assistance:
- Be familiar with HTTP, ClientSSL, ServerSSL, TCP, UDP, and persistence profiles
- Perform software management functions on the platform (for example, capable of performing upgrades and licensing).
- Perform administrative tasks using the GUI
- Able to access and manage the BIG-IP through multiple paths (management IP, Self IP)
- Open a support case and utilize online resources such as AskF5, F5 iHealth, and DevCentral
- Understand the relationship and differentiation between virtual servers, virtual server types, virtual addresses, pools, pool members, nodes, profiles, iRules, and address translation (NAT/SNAT)
Understanding of functional and technical aspects of Opening a support ticket with F5
The following will be discussed in this section:
- Use the dashboard to gauge the current running status of the system
- Review log files and identify possible events
- Identify severity levels and the associated response times
- Use iApps Analytics to gauge the current running status of application services
- Given an issue, determine the appropriate severity according to F5 guidelines
- Explain what virtual servers, pools, nodes and pool members are
- Explain the purpose of iApps Analytics
- Distinguish between qualitative/quantitative statements in order to assemble an accurate problem description
- Given a situation, predict the appropriate dashboard statistics
- Provide quantitative and relevant information appropriate for a given issue
- Identify the necessary components for all support cases (Qkview uploaded to iHealth/ or attached to case, serial number of device, problem description, other supporting data)
- Given a current running status, recognize significant statistics
- Describe how to capture application statistics
- Identify the appropriate supporting components and severity levels for an F5 support ticket
- Given log file snippets, identify critical events
- Explain the status icons of objects on the map
- Distinguish between relevant/irrelevant information in order to assemble an accurate problem description
- Review the Network Map in order to determine the status of objects
- Interpret each of the statistic types displayed by the dashboard
- Given log file snippets, describe an event sequence
Understanding of functional and technical aspects of Troubleshooting basic performance issues
The following will be discussed in this section:
- Recognize when a packet capture is needed within the context of a performance issue
- Differentiate between performance issue types (i.e. Latency, Congestion, broken content)
- Use BIG-IP tools in order to identify potential performance issues
- Establish the frequency of a given issue (random, continuous, isolated, intermittent, repetitive intervals)
- Understand how to get performance statistics in addition to the those shown in the dashboard (Overview - Performance)

We're so confident of our products that we provide no hassle product exchange.


By Audrey


