Product Specializations
This domain tests depth in the F5 product families you specify or administer: LTM traffic management, DNS/GTM global load balancing, ASM/Advanced WAF, APM access, NGINX, and Distributed Cloud services. Questions ask you to select the right module, profile, monitor, or persistence method for a stated application requirement.
Core rules
- LTM builds a virtual server that references a pool of members, a monitor, a persistence profile, and protocol profiles. Default load balancing is round robin; least connections suits long-lived, uneven sessions; observed and predictive use historical performance data.
- Monitors decide member availability. A member must pass its monitor before receiving traffic. Interval, timeout, and retries set failover speed, so a slow monitor delays removal of a dead server.
- Persistence choices include source IP (fragile behind NAT and proxies), cookie (insert, rewrite, or passive), SSL session ID, and hash. Cookie insert is usually best for HTTP applications because it survives client IP changes.
- DNS/GTM answers wide-IP queries from pools using methods such as global availability, round robin, ratio, topology, and QoS. Health checks and virtual-server dependencies remove dead sites from answers.
- ASM is a reverse-proxy WAF driven by a security policy. New policies typically begin in transparent or learning mode and must be tuned and then enforced. Advanced WAF adds bot defense, credential-stuffing protection, and API discovery.
- APM supplies access policies, SSO, MFA, and per-request policies. NGINX and NGINX Plus handle reverse proxy, load balancing, and Kubernetes Ingress, with NGINX App Protect providing WAF.
Worked example
An application team reports that users bounce between two data centers and lose shopping carts, and some users sit behind a corporate proxy. Source-IP persistence would pin every proxy user to one member and still break when the proxy egress address changes. Choose cookie persistence in insert mode so the BIG-IP sets its own cookie and consistently routes each browser. Add a source-IP fallback profile only if the application has non-HTTP flows. Verify the pool monitor checks the application health endpoint, not just TCP, so a hung app is removed.
Traps that cost marks
Confusing least connections with least sessions; assuming ASM blocks attacks out of the box when the policy is still transparent; forgetting APM is separately licensed; using DNS Express for zones it does not host; and attaching an LTM monitor where a GTM monitor is required.