NSE4 System and Network Administration Practice Question
You are troubleshooting a FortiGate HA cluster that is not failing over correctly. The cluster has two units in active-passive mode. You check the HA status and see both units are in 'standalone' mode. Which THREE configurations could cause this? (Choose three.)
⚠ Common exam trap
The trap here is that candidates often overlook the HA password requirement or assume transparent mode disables HA, but FortiGate supports HA in all operational modes, and password mismatches are a common misconfiguration.
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 HA group ID is different on each unit
The HA group ID must match on all cluster members for them to recognize each other as part of the same cluster. If the group IDs differ, each unit will operate independently in standalone mode, as they cannot form a common HA session.
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 FortiGate is configured in transparent mode
Why it's wrong here
Transparent mode is a fully supported operating mode for FortiGate HA clusters; both NAT and transparent modes can form an HA pair as long as both units operate in the same mode. The failure symptom of standalone units is not caused by the operating mode itself, because transparent mode still allows heartbeat exchange and failover. A mode mismatch between the two units could prevent cluster formation, but that is not what this option states. Therefore, transparent mode alone is not a valid cause for a cluster that is not forming.
- ✓
The HA group ID is different on each unit
Why this is correct
The HA group ID is a mandatory matching parameter for cluster membership; each heartbeat packet carries the group ID, and a FortiGate only processes heartbeats from units with the same group ID. If the two units are configured with different group IDs, they will silently discard each other's heartbeat messages, so neither ever sees a peer and both remain in standalone mode. This is a classic misconfiguration when units are pre-staged separately or when a configuration template is not synchronized. Setting both units to the same group ID (0 through 255) is required before they can form an HA cluster.
- ✗
The firmware versions are different but both are 7.0.x
Why it's wrong here
FortiOS HA generally allows cluster formation when both units run the same major firmware version with minor differences; for example, 7.0.1 and 7.0.6 are considered compatible, albeit not recommended in production. A firmware version mismatch alone would not force a unit into standalone mode because the cluster can still be established, possibly with a compatibility warning. Only significant differences such as different major versions (e.g., 6.4 and 7.0) would prevent cluster formation. Since both units here run 7.0.x, the version difference is not the reason the cluster is not forming.
- ✓
The HA heartbeat interface is down on one unit
Why this is correct
The heartbeat interface is the dedicated control link that lets HA peers exchange state and keepalive messages; without this link, units cannot verify each other's health or negotiate roles. When the heartbeat interface is down or unreachable on one unit, that unit will not see the peer's heartbeats and will assume it is alone, causing it to operate in standalone mode or attempt to become primary. This remains true even if the data plane is connected. A physical cable failure, a disabled port, or a VLAN misconfiguration on the heartbeat link is a common root cause of a FortiGate HA cluster that splits into two standalone firewalls.
- ✓
The HA password is different on each unit
Why this is correct
The HA password is used to authenticate heartbeat packets and secure configuration synchronization between cluster members. Each FortiGate compares the received heartbeat's authentication payload against its own configured password; if they differ, the packets are dropped as invalid. As a result, the units do not recognize each other and remain in standalone mode with no failover or synchronization. This can happen after the password is changed on only one unit or when passwords are not included in a configuration restore, so it is essential to verify the password matches exactly, including case sensitivity, on all members.
Go deeper
Related to this question
About these practice questions
One of 773 original NSE4 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
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.