nerdexam
Fortinet

NSE4 · Question #274

In a High Availability configuration operating in Active-Active mode, which of the following correctly describes the path taken by a load-balanced HTTP session?

The correct answer is A. Request: Internal Host -> Master FG -> Slave FG -> Internet -> Web Server. In an Active-Active FortiGate HA configuration, a load-balanced HTTP session typically involves the Master FortiGate initially processing or distributing the session, which is then handled by a Slave FortiGate for egress traffic to the internet.

Submitted by yousef_jo· Apr 18, 2026FortiGate Deployment and System Configuration

Question

In a High Availability configuration operating in Active-Active mode, which of the following correctly describes the path taken by a load-balanced HTTP session?

Options

  • ARequest: Internal Host -> Master FG -> Slave FG -> Internet -> Web Server
  • BRequest: Internal Host -> Master FG -> Slave FG -> Master FG -> Internet -> Web Server
  • CRequest: Internal Host -> Slave FG -> Internet -> Web Server
  • DRequest: Internal Host -> Slave FG -> Master FG -> Internet -> Web Server

How the community answered

(21 responses)
  • A
    90% (19)
  • C
    5% (1)
  • D
    5% (1)

Why each option

In an Active-Active FortiGate HA configuration, a load-balanced HTTP session typically involves the Master FortiGate initially processing or distributing the session, which is then handled by a Slave FortiGate for egress traffic to the internet.

ARequest: Internal Host -> Master FG -> Slave FG -> Internet -> Web ServerCorrect

In FortiGate's Active-Active HA mode, session processing is distributed among cluster members. The Master FortiGate often receives the initial request, performs necessary checks or session assignments, and then load-balances or forwards the session to a Slave FortiGate for the actual processing and egress to the Internet to reach the web server, ensuring traffic distribution.

BRequest: Internal Host -> Master FG -> Slave FG -> Master FG -> Internet -> Web Server

A single HTTP session would not typically traverse Master -> Slave -> Master again; once a session is assigned to a unit for processing, it usually flows through that unit.

CRequest: Internal Host -> Slave FG -> Internet -> Web Server

While a Slave FG processes traffic, in a load-balanced scenario coordinated by the master, the path often involves the master's initial role in session distribution, rather than the internal host always directly sending to the slave for initial connection.

DRequest: Internal Host -> Slave FG -> Master FG -> Internet -> Web Server

Routing through Slave -> Master -> Internet for a single session is not the standard flow in a FortiGate Active-Active load-balanced scenario, as the master typically distributes, or the session is directly handled by one unit.

Concept tested: FortiGate Active-Active HA traffic flow

Source: https://docs.fortinet.com/document/fortigate/7.4.0/fortios-handbook/357672/load-balancing-traffic-with-active-active-ha

Topics

#High Availability (HA)#Active-Active Mode#Session Flow#FortiGate HA

Community Discussion

No community discussion yet for this question.

Full NSE4 Practice