Monitoring and Troubleshooting (17%) - Monitor BIG-IP system performance and health, troubleshoot common issues and system errors, analyze and interpret system logs and data, identify and resolve security threats,

Local Traffic Management (16%) - Configure and manage BIG-IP LTM features, implement and manage virtual servers and services, monitor and analyze traffic and session statistics,

BIG-IP System Administration (16%) - Configure and manage BIG-IP system settings, implement and manage BIG-IP user authentication and authorization, manage BIG-IP log and security settings,

BIG-IP Scalability and High Availability (11%) - Implement and manage BIG-IP high availability, configure and manage BIG-IP scalability features, monitor and analyze system performance and health,

BIG-IP Advanced Topics (16%) - Implement and manage BIG-IP iRules, configure and manage BIG-IP system security settings, implement and manage BIG-IP advanced traffic management features,

Option B: iRules

Option C: Traffic Management Shell (tmsh)

Option D: Route Domains

Option E: MAC Masquerading

Option F: Always-On Management (AOM)

Correct Answer: Option B

Explanation for Option A: Incorrect. SNAT is used to map original client IP addresses to a translated IP address, not for custom programmatic traffic manipulation,

Explanation for Option B: Correct. iRules is a customized, TCL-based scripting language built into the BIG-IP system that allows administrators to directly inspect, intercept, and manipulate traffic payloads and headers in real-time,

Explanation for Option C: Incorrect. tmsh is the command-line interface used for administrative configuration of the BIG-IP system, not a mechanism for real-time traffic manipulation,

Explanation for Option D: Incorrect. Route Domains provide network isolation within the BIG-IP system, allowing overlapping IP spaces, rather than inspecting application layer logic,

Explanation for Option E: Incorrect. MAC Masquerading is a high availability feature that allows a floating MAC address to be shared between devices, accelerating failover convergence,

Explanation for Option F: Incorrect. AOM provides out-of-band management access to the hardware appliance, entirely unrelated to application traffic processing,

Option B: Network Failover

Option C: HA Groups

Option D: Fail-Safe

Option E: Split Brain Avoidance

Option F: Connection Mirroring

Correct Answer: Option E

Explanation for Option A: Incorrect. Configuration Sync ensures identical configurations across the device group, but does not dictate active/standby traffic processing logic during an outage,

Explanation for Option B: Incorrect. Network Failover is the mechanism for passing heartbeat packets to detect peer status, but it does not inherently solve the simultaneous processing issue,

Explanation for Option C: Incorrect. HA Groups calculate scores based on trunk, pool, or cluster status to determine the active device, not specifically preventing dual-active scenarios,

Explanation for Option D: Incorrect. Fail-Safe monitors specific services or VLAN traffic to trigger a failover if traffic stops, rather than preventing partition issues,

Explanation for Option E: Correct. Split Brain Avoidance (often utilizing gateway failsafe or network failover combined with management port heartbeats) prevents the active-active "split brain" scenario where both devices assume the active role during a partition,

Explanation for Option F: Incorrect. Connection Mirroring duplicates stateful session data to the standby device so connections survive a failover, but does not stop both from going active,

Option B: The node configuration has been manually disabled

Option C: The application health monitor assigned to the pool is failing

Option D: The BIG-IP system has exhausted its memory resources

Option E: The client SSL profile is configured with an expired certificate

Option F: A packet filter rule is dropping outbound traffic

Correct Answer: Option C

Explanation for Option A: Incorrect. If the virtual server IP was wrong, clients would fail to connect, but it would not cause the BIG-IP to mark a specific backend pool member offline,

Explanation for Option B: Incorrect. If manually disabled, the status would show as disabled (black circle) rather than offline (red diamond),

Explanation for Option C: Correct. A ping only verifies Layer 3 connectivity. If a Layer 7 application health monitor (like an HTTP monitor looking for a 200 OK response) fails to receive the expected string, it will mark the member offline regardless of ICMP reachability,

Explanation for Option D: Incorrect. Memory exhaustion would typically cause system-wide instability or aggressive connection reaping, not specifically target one pool member with an offline status,

Explanation for Option E: Incorrect. An expired client SSL profile affects the client-to-F5 connection, not the health status of the backend pool member,

Explanation for Option F: Incorrect. While a packet filter could theoretically block monitor traffic, application monitor failure is the direct configuration cause of the offline status,

You can retake the exams as many times as you want,

This is a huge original question bank,

You get support from instructors if you have questions,

Each question has a detailed explanation,

Mobile-compatible with the Udemy app,