Courseiva
System and Network AdministrationeasyMultiple ChoiceObjective-mapped

How Active-Passive HA Failover Works in FortiGate

An administrator has configured two FortiGate units in an active-passive HA cluster. The primary unit fails. How does the secondary unit become active?

Quick Answer

The answer is that the secondary unit detects loss of heartbeat from the primary and takes over. This occurs because in an active-passive HA failover mechanism, the secondary unit continuously monitors the primary unit’s health through dedicated heartbeat interfaces; when the primary fails and stops sending these heartbeat messages, the secondary interprets the absence as a failure and automatically transitions to the active role. On the Fortinet NSE 4 Network Security Professional NSE4 exam, this concept tests your understanding of FortiGate’s default HA behavior, where no manual intervention or additional conditions like link monitoring are required for the failover to trigger. A common trap is assuming the secondary must detect a link failure or wait for a timer to expire, but the core trigger is simply the loss of heartbeat. Memory tip: “No heartbeat, no hesitation—secondary takes the station.”

⚠ Common exam trap

A common mix-up: candidates think the secondary unit requires the heartbeat link to be down or manual intervention to become active, but FortiGate HA automatically promotes the secondary unit upon detecting the primary's failure via heartbeat loss.

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

The secondary unit detects loss of heartbeat from the primary and takes over

In an active-passive HA cluster, the secondary unit monitors the primary unit's health via heartbeat messages. When the primary fails and stops sending heartbeats, the secondary unit detects the loss of heartbeat and initiates a failover, transitioning to the active role. This is the default behavior in FortiGate HA, where the secondary unit does not require manual intervention or additional conditions to become active.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • The secondary unit detects loss of heartbeat from the primary and takes over

    Why this is correct

    Heartbeat monitoring triggers failover when primary is unreachable.

  • The administrator must manually reboot the secondary unit

    Why it's wrong here

    Failover is automatic; manual reboot is not required.

  • The secondary unit becomes active only if the heartbeat link is also down

    Why it's wrong here

    Heartbeat link failure is one of the conditions, but the primary unit failure is the trigger.

  • The secondary unit waits for a configuration change before becoming active

    Why it's wrong here

    No configuration change is needed.

About these practice questions

Courseiva writes every NSE4 question from scratch — 282 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 →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 more way this is tested on NSE4

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. An administrator configures a FortiGate HA cluster with two units in active-passive mode. After setup, the secondary unit shows 'standby' status but traffic is not failing over when the primary is shut down. What is the most likely cause?

hard
  • A.The HA heartbeat interface is not configured on the same subnet.
  • B.The cluster is in active-active mode.
  • C.The session failover feature is disabled.
  • D.The primary unit's configuration changes were not synchronized to the secondary.

Why D: In an active-passive HA cluster, the secondary unit must have a synchronized copy of the primary's configuration to take over traffic. If configuration synchronization is not enabled or fails, the secondary remains in standby but lacks the necessary policies and settings to handle traffic, so failover does not occur even though HA status appears normal.

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This NSE4 practice question is part of Courseiva's free Fortinet 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 NSE4 exam.