Refer to the exhibit. An administrator deployed an HA active-active load balance sandwich in Microsoft Azure. The setup requires configuration synchronization between devices. What are two outcomes…

Question

Exhibit

Options

• AFortiGate-VM instances are scaled out automatically according to predefined workload levels.
• BFortiGate A and FortiGate B are two independent devices.
• CBy default, FortiGate uses FGCP
• DIt does not synchronize the FortiGate hostname

• A
  14% (5)
• B
  81% (29)
• C
  6% (2)

Explanation

FortiGate A and FortiGate B are two independent devices. This means that they are not part of a cluster or a high availability group, and they do not share the same configuration or state information. They are configured as standalone FortiGates with standalone configuration synchronization enabled. This feature allows them to synchronize most of their configuration settings with each other, except for some settings that identify the FortiGate to the network, such as the hostname. It does not synchronize the FortiGate hostname. This is one of the settings that are excluded from the standalone configuration synchronization, as mentioned above. The hostname is a unique identifier for each FortiGate device, and it should not be changed by the synchronization process.

No community discussion yet for this question.