What are two expected results when both FortiManager and FortiGate are behind network address translation NAT devices? Choose two answers

When both FortiManager and FortiGate reside behind Network Address Translation (NAT) devices, communication and discovery rely on translated IP addresses. During the discovery process initiated from FortiManager, FortiManager targets and discovers the FortiGate using the FortiGate's public NATed IP address. However, because FortiManager is also behind a NAT gateway, it is unaware of its own external public NATed address by default. Consequently, during discovery, FortiManager pushes its internal non-NATed IP address to the FortiGate's central management configuration instead of its NATed IP address. Administrators must manually update the central management IP address on the FortiGate to ensure proper long-term FGFM management connection re-establishment across NAT gateways.

Option C: FortiGate requires the external NATed IP address of FortiManager configured under central management to successfully initiate connections.

Option D: FortiManager cannot initiate FGFM connections to a FortiGate behind NAT; re-establishment must be initiated by the FortiGate.

- Fortinet FortiManager 7.0.0 Administration Guide

Section: "Device Manager"

Subsection: "Discovery and NAT configurations".

- Fortinet FortiManager 7.2 Study Guide

Chapter: "FGFM Protocol and Device Discovery"

Page 95–102.