F5CABR (BIG-IP Recert) case studies
F5CABR (BIG-IP Recert) · Put your knowledge to work in context.
The F5 BIG-IP Recertification exam (F5CABR) is a recertification assessment for IT professionals who already hold an active F5 Certified BIG-IP Administrator or higher-level BIG-IP certification. Rather than testing every topic from scratch, it verifies that your knowledge of the BIG-IP platform remains current across local traffic management, high availability, security, and troubleshooting. The F5CABR (BIG-IP Recert) case studies are 5 cases and about 4,295 words.
1Checkout Pool: Round Robin on Wildly Unequal Hardware, No Persistence
Checkout runs on one virtual server with a single pool of four members: web-01 (32 vCPU), web-02 (32 vCPU), legacy-01 (8 vCPU, which also runs the licensed tax daemon) and legacy-02 (8 vCPU, identical to legacy-01). Round Robin is the only load balancing setting; all four members sit in one priority group with Priority Group Activation set to 'Less than 2 available'.
861 words, about 4 min2Source Address Persistence Behind Carrier NAT
A consumer portal is published on one virtual server (Client SSL and HTTP profiles, OneConnect enabled) with four pool members listening on port 8080. The only persistence profile attached is the built-in Source Address profile with a 180-second idle timeout.
765 words, about 4 min3Three Hostnames, One VIP: Chains, Protocols and Re-Encryption
One virtual server at 203.0.113.10:443 terminates TLS for three hostnames using SNI: www.example.com and shop.example.com (both covered by a wildcard .example.com certificate) and api.partner.example (a separate certificate from a public CA). The client SSL profile carries the wildcard as its default certificate; the partner certificate is selected by an SNI-based Client SSL profile on a matching Server Name.
865 words, about 4 min4Failsafe on the Heartbeat VLAN Moves Both Traffic Groups
An active/standby pair (BIG-IP A and B) runs two traffic groups: tg-portal (self IP 10.20.1.100) and tg-partner (self IP 10.20.1.101). tg-portal was active on A; tg-partner was configured to be active on B and had served traffic there for two years, so the pair effectively runs active/active for different applications.
913 words, about 5 min5ASM False Positives and an AFM Blacklist Behind a Partner Proxy
A public API is protected by a single virtual server carrying APM (an access policy plus a per-request policy), ASM in Blocking enforcement, and an AFM DoS profile. The ASM policy was built in staging against a hand-written XML sample.
891 words, about 4 min