F5-CSE case studies
F5-CSE · Put your knowledge to work in context.
F5-CSE is a certification for administrators and engineers who design, deploy, and support application delivery environments built on F5 BIG-IP. It suits candidates who already handle day-to-day traffic management and want to demonstrate that they can reason about the whole stack - how a request is processed internally, how virtual servers and pools are structured, how profiles and persistence shape behaviour, how TLS is terminated and managed, and how security and high-availability controls fit together. The F5-CSE case studies are 5 cases and about 4,796 words.
1Branch users authenticate but stall on any response larger than 1.3 KB
A web portal is published on a BIG-IP running TMOS 16.1 at 203.0.113.10:443, using a standard virtual server, a client SSL profile, and a pool of three members on the internal VLAN. Head-office users work normally.
889 words, about 4 min2Least Connections (member) stops distributing load after two small nodes join the pool
vs-shop at 10.0.0.10:443 fronts app pool with four members. Members .21 and .22 are 16-vCPU hosts; .23 and .24 are 4-vCPU hosts added last quarter.
883 words, about 4 min3Source IP persistence collapses onto two members behind forward proxies
vs-portal at 10.0.0.20:443 uses portal pool with six members and Source IP persistence with a 1800-second timeout. Users arrive through one of two forward proxies, 10.50.0.5 and 10.50.0.6, which PAT all branch traffic; roughly 70% of sessions come from .5.
988 words, about 5 min4One virtual server, five hostnames, one wildcard certificate
A SaaS provider publishes vs-saas at 198.51.100.20:443 as a standard virtual server with one client SSL profile, clientssl-default, holding a wildcard certificate for .saas.example.com (RSA 2048) that expires in 12 days. The certificate object contains only the leaf; the issuing intermediate is not included in the file.
1,022 words, about 5 min5A failover exposed six weeks of configuration that never reached the standby
A BIG-IP pair runs active/standby with a device group dg-ha containing traffic-group-1. Device A is active and holds the floating self IP; device B is standby.
1,014 words, about 5 min