What is a common feature of FortiGate's HA setup?

In a FortiGate high availability (HA) setup, one of the primary features is automatic failover between units. This ensures that if the primary unit fails or becomes unreachable, the secondary unit can seamlessly take over the role of protecting network resources without manual intervention. This characteristic is crucial for maintaining service continuity and minimizing downtime in a networked environment.

Automatic failover typically involves monitoring the health of the primary unit and quickly rerouting all traffic to the backup unit if an issue is detected. This process is executed through HA protocols that allow for real-time synchronization of session states and configurations between the units, enabling users to maintain an uninterrupted experience even in the event of hardware or software failures.

In contrast, while load balancing, session persistence, and centralized logging may also play roles in a FortiGate environment, they do not specifically define the core purpose of HA, which is to provide reliability and availability through automatic failover. Load balancing is about distributing traffic to multiple active units, session persistence relates to maintaining sessions over a cluster, and centralized logging concerns the aggregation of logs from all units, rather than their failover capabilities.