F5CAB2 practice question 2 of 10

What should a BIG-IP Administrator configure to minimize impact during a failover? (Choose one answer)

Full set: 67 questions
Answer options
A: External monitors
B: Clone pool
C: OneConnect profile
D: MAC masquerading Correct answer
Correct Answer:
D. MAC masquerading
Explanation

MAC masquerading is a feature specifically designed to minimize traffic disruption during a BIG-IP device failover. It assigns a unique, non-device-specific MAC address to a traffic group. When a failover occurs, the newly active unit takes over this same MAC address along with the floating IP addresses. This prevents upstream network devices, such as switches and routers, from needing to update their Address Resolution Protocol (ARP) caches with a new MAC address. By keeping the MAC address consistent, network convergence time is significantly reduced, resulting in a faster and more seamless failover.

Why Incorrect

A. External monitors are used to verify the health and availability of pool members (backend servers), not to manage the network impact of a BIG-IP system failover.
B. A clone pool is used to copy traffic to another interface or device, typically for monitoring or intrusion detection, and has no role in the failover process.
C. A OneConnect profile optimizes server-side TCP connections for performance and efficiency but does not address the Layer 2 network transition that occurs during a device failover.

References

1. F5 Networks, BIG-IP Device Service Clustering: Administration, Version 16.1, Chapter: Configuring High Availability.

Section: MAC masquerade address: "When a device fails over, the new active device begins processing traffic for the traffic group, using the MAC masquerade address. Because the MAC address has not changed, the upstream router and other network devices do not need to update their Address Resolution Protocol (ARP) caches. This prevents a disruption in traffic."

2. F5 Networks, BIG-IP Local Traffic Manager: Concepts, Version 16.1, Chapter: Monitors.

Section: About Monitors: "A monitor is a component of the BIG-IP system that you use to check the status of any network device, such as a pool member or node." This confirms monitors are for checking backend resources, not for managing failover impact.

3. F5 Networks, BIG-IP Local Traffic Manager: Concepts, Version 16.1, Chapter: Profiles.

Section: Understanding the OneConnect profile: "The OneConnect™ profile causes the BIG-IP system to minimize the number of server-side TCP connections by re-using existing connections for subsequent requests." This clarifies its purpose as connection optimization, not failover management.

Scroll to Top