An administrator wants the FGCP cluster to fail over automatically if the WAN-facing interface on the primary unit loses its link, but is unsure how to make the cluster react to that specific port. Which configuration achieves this?
- AEnable session pickup so the cluster tracks the WAN interface state and migrates sessions when the link drops.
- BRaise the device priority on the WAN interface so the cluster favours whichever unit has that link up.
- CConfigure a second heartbeat interface on the WAN port so heartbeat loss there forces the cluster to switch units.
- DAdd the WAN interface to the HA monitored interfaces list so a link failure on it lowers the unit's score and triggers failover. Correct
Why A is wrong: Tempting because session pickup is an HA feature, but it only synchronises session tables for smoother failover; it does not monitor interface link state or trigger a failover when a port goes down.
Why B is wrong: Plausible because priority influences primary selection, but device priority is a static administrative preference and is not evaluated per interface link state, so it does not cause an automatic failover on link loss.
Why C is wrong: This confuses heartbeat with port monitoring; heartbeat interfaces detect peer reachability between cluster members, not the up or down state of a data interface like the WAN port.
Why D is correct: Interface monitoring (port monitoring) adds the chosen interface to the HA health calculation, so a link-down event on the monitored WAN port reduces that unit's cluster score and causes the cluster to fail over to the healthy unit.