You deployed a FortiGate active-active with ELB/ILB solution using the template from Azure Marketplace. What is the purpose of the inbound NAT rules configured in the external load balancer in this…

The correct answer is D. To allow administrative access to the FortiGate VMs. In an active-active FortiGate ELB/ILB deployment, the inbound NAT rules configured on the external load balancer are used to allow administrative access (e.g., HTTPS, SSH) to the individual FortiGate VMs. Since the public IP is associated with the load balancer, NAT rules are…

Deploying FortiGate-VM on Azure

Question

You deployed a FortiGate active-active with ELB/ILB solution using the template from Azure Marketplace. What is the purpose of the inbound NAT rules configured in the external load balancer in this deployment?

Options

ATo load balance the incoming traffic between both FortiGate VMs
BTo filter inbound traffic before it reaches the FortiGate instances
CTo forward the health probes to both FortiGate VMs
DTo allow administrative access to the FortiGate VMs

How the community answered

(40 responses)

A
3% (1)
B
10% (4)
C
8% (3)
D
80% (32)

Explanation

In an active-active FortiGate ELB/ILB deployment, the inbound NAT rules configured on the external load balancer are used to allow administrative access (e.g., HTTPS, SSH) to the individual FortiGate VMs. Since the public IP is associated with the load balancer, NAT rules are required to map specific ports to backend FortiGate instances for management access.

Topics

#external load balancer#inbound NAT rules#FortiGate HA#active-active

Community Discussion

No community discussion yet for this question.

Full FCP_ZCS_AD-7.4 Practice