An administrator runs 'show high-availability state' and sees that the local firewall is in 'passive' state, but the remote firewall shows 'active'. However, the HA1 link is up and the configuration is synchronized. What could cause the passive firewall to not take over after the active fails?
HA2 link is for session sync, not state.
Why this answer
If the HA2 link is down, the passive firewall cannot synchronize session state from the active firewall. In Palo Alto Networks HA implementations, the passive firewall requires a functional HA2 link to be considered fully operational and ready to take over; without it, the passive will not assume the active role even if the active fails. The HA1 link ensures heartbeats and configuration synchronization, but state synchronization over HA2 is critical for failover eligibility.
Exam trap
Candidates often assume that a functional HA1 link and synchronized configuration guarantee automatic failover, but they overlook the dependency on the HA2 link for state synchronization and failover readiness.
How to eliminate wrong answers
Option A is wrong because the question explicitly states that the configuration is synchronized, so this is not the cause. Option B is wrong because session synchronization is unrelated to the failover trigger; session sync ensures stateful failover but does not affect the passive firewall's ability to become active after a failure. Option C is wrong because the HA2 link (data link) is not required for failover detection; the HA1 link (control link) is used for keepalive messages and is reported as up, so the passive firewall should detect the active failure via HA1.