F5-301A case studies
F5-301A · Put your knowledge to work in context.
F5-301A - usually written as 301a - is the exam code associated with the F5 BIG-IP Administrator credential, a mid-level certification for people who run BIG-IP application delivery controllers day to day. It suits administrators, network engineers and operations staff who already touch BIG-IP configuration and want their practical skills validated, rather than architects or developers working purely with APIs and automation. The published blueprint is multiple choice and is organised around eight functional areas: setup and initial configuration; network configuration with VLANs, self IPs and routes; local traffic objects (nodes, pools and monitors); virtual servers and profiles; NAT and SNAT; SSL/TLS and certificate management; high availability and device service clustering; and monitoring, logging and troubleshooting. Because those areas map onto the order in which a device is actually built, preparation usually combines hands-on lab work on a real or virtual BIG-IP with revision of each object type and its dependencies. The F5-301A case studies are 5 cases and about 3,339 words.
1Two Divisions, One Subnet: Route Domain Design
Acme merges with two divisions that both use 10.20.0.0/24. The BIG-IP runs a single route domain 0.
689 words, about 3 min2SNAT Automap After a Planned Failover
A pair runs active/standby with one sync-failover device group and traffic-group-1. The client-facing VLAN has a floating self IP 203.0.113.10.
701 words, about 4 min3Mobile App Trust Failure and a Second Hostname
A public-facing virtual server 198.51.100.20:443 uses a client SSL profile with a certificate for portal.example.com issued by a public CA. Desktop browsers connect fine, but the iOS and Android versions of the company app report 'server certificate not trusted'.
665 words, about 3 min4A New VLAN That Does Not Follow the Virtual Server
An active/standby pair has device A active and device B standby. They run a sync-failover device group with traffic-group-1 floating.
634 words, about 3 min5The Pool Is Down but the Application Is Up
A pool of three nodes on port 8080 uses a custom HTTP monitor: send 'GET /health HTTP/1.0 ', receive '200 OK', interval 5, timeout 16. The application team deploys a new version that requires a Host header and redirects HTTP to HTTPS with a 301 for any request without Host.
650 words, about 3 min