Pass the Fortinet NSE 5 Network Security Analyst NSE5_FMG-7.2 Questions and answers with ExamsMirror

FortiManager will reboot

FortiManager will send the logging configuration to the managed devices so the managed devices will start sending logs to FortiManager

FortiManager will enable ADOMs automatically to collect logs from non-FortiGate devices

FortiManager can be used only as a logging device.

The FortiGate will be added automatically to the default ADOM named FortiGate.

The FortiGate will be automatically added to the Training ADOM.

By default, the unregistered FortiGate will appear in the root ADOM.

The FortiManager administrator must add the unregistered device manually to the unregistered device

manually to the Training ADOM using the Add Device wizard

Specify a gateway address when you create a default SD-WAN static route

Enable SD-WAN central management in the Training ADOM

Configure and install the SD-WAN firewall policy and SD-WAN static route before installing the SD-WAN

template settings

Remove all the interface references such as routes or policies that will be a part of SD-WAN member

interfaces

To find and provide recommendation to combine multiple separate policy packages into one common

policy package

To find and merge duplicate policies in the policy package

To find and provide recommendation for optimizing policies in a policy package

To find and delete disabled firewall policies in the policy package

SD-WAN must be enabled on per-ADOM basis

You can create multiple SD-WAN interfaces per VDOM

When you configure an SD-WAN, you must specify at least two member interfaces.

The first step in creating an SD-WAN using FortiManager is to create two SD-WAN firewall policies.

Set to workflow and use the ADOM locking feature

Set to read/write and use the policy locking feature

Set to normal and use the policy locking feature

Set to disable and use the policy locking feature

Secondary device with highest priority will automatically be promoted to the primary role, and manually

reconfigure all other secondary devices to point to the new primary device

Reboot one of the secondary devices to promote it automatically to the primary role, and reconfigure all other secondary devices to point to the new primary device.

Manually promote one of the secondary devices to the primary role, and reconfigure all other secondary devices to point to the new primary device.

FortiManager HA state transition is transparent to administrators and does not require any reconfiguration.

Policy ID 2 is installed without a source address

Policy ID 2 will not be installed

Policy ID 2 is installed in disabled state

Policy ID 2 is installed without a source device

FortiGate is discovered by FortiManager through the FortiGate NATed IP address.

FortiGate can announce itself to FortiManager only if the FortiManager IP address is configured on

FortiGate under central management.

During discovery, the FortiManager NATed IP address is not set by default on FortiGate.

If the FCFM tunnel is torn down, FortiManager will try to re-establish the FGFM tunnel.

Policy 3 will be installed on all FortiGate devices and vdom belongs to the ADOM.

Policy seq.# 3 will be skipped because no installation targets are specified.

Policy seq.# 3 will be installed on all managed devices and VDOMs that are listed under Installation Targets.

Policy seq.# 2 will not be installed on the Local-FortiGate root VDOM because there is no root VDOM in the Installation Target.

Policy seq # 1 will be installed on the Remote-FortiGate root[NAT] and Student[NAT] VDOMs only.