Configuration synchronization is natively built into FGCP-based clusters (both active-passive and active-active); any change made on the primary node is automatically replicated to every secondary node.

Since FortiOS 6.4, FGSP also provides an optional “configuration-synchronization” mode that continuously copies the full running-config between the two standalone peers, giving them the same behaviour as an HA pair while still using FGSP’s session-sharing model.

VRRP and standalone deployments have no mechanism to copy the full configuration database, so they do not meet the stated requirement.

C. VRRP – Only the virtual IP is shared; each firewall keeps an independent configuration with no automatic sync capability.

E. Stand-alone appliance – A single unit; nothing exists to synchronise with, so configuration replication is impossible.

1. Fortinet. “FortiOS 7.4 Administration Guide – High Availability: How FGCP synchronises configuration”, pp. 548-549.

2. Fortinet. “FortiOS 7.4 Administration Guide – Active-active HA operation”, p. 556.

3. Fortinet. “FortiOS 7.4 Administration Guide – FortiGate Session Life Support Protocol (FGSP) with configuration synchronisation”, pp. 607-610.

4. Fortinet. “FortiOS 7.4 Administration Guide – Virtual Router Redundancy Protocol (VRRP)”, p. 640 (states ‘no configuration-sync’).