PCNSA Device Management and Services Practice Question
A company has two PA-220 firewalls in active/passive HA. They want to ensure that if the active firewall loses internet connectivity but its management interface remains up, a failover occurs. Which monitoring method should be configured?
⚠ Common exam trap
A common mix-up: candidates confuse 'link monitoring' (which only checks local interface status) with 'path monitoring' (which checks end-to-end connectivity to a remote target), leading them to select link monitoring when the question explicitly requires detection of internet connectivity loss beyond the first hop.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Path monitoring.
Path monitoring is the correct method because it monitors the dataplane connectivity to specific destination IP addresses (e.g., the internet gateway) and triggers a failover when those paths become unreachable, even if the management interface remains up. This ensures that the active firewall fails over based on actual data traffic path health, not just link or management status.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Path monitoring.
Why this is correct
Path monitoring sends ICMP pings to defined destination IP addresses, so loss of upstream reachability triggers failover even while the management interface stays up. This satisfies the stem's constraint that internet connectivity loss, not interface state, must drive the active/passive PA-220 failover.
- ✗
Heartbeat backup.
Why it's wrong here
Heartbeat backup sends heartbeat packets over the HA backup path, providing redundancy for the heartbeat link itself rather than monitoring internet reachability. It is tempting as a resilience feature, but it would be correct when the HA backup channel needs protection, not when path monitoring must trigger failover.
- ✗
Session replication.
Why it's wrong here
Session replication synchronises session tables between HA peers so established flows survive failover; it does not detect loss of internet connectivity. It is tempting because it is a genuine HA feature, but it would be the right choice when session continuity across failover matters, not for triggering failover on a path failure.
- ✗
Link monitoring on all interfaces.
Why it's wrong here
Link monitoring on all interfaces tracks physical link state, so a firewall whose management interface stays up while internet connectivity fails would not trigger failover. It is tempting because link monitoring is a real HA trigger, but it would be correct when physical link loss must cause failover, not logical path failure.
Go deeper
Related to this question
About these practice questions
Courseiva writes every PCNSA question from scratch — 385 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PCNSA practice question is part of Courseiva's free Palo Alto Networks certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PCNSA exam.