NSE5_FMG-7.2 Practice Exam Questions with Answers Fortinet NSE 5 - FortiManager 7.2 Certification

You must install these changes using theInstall Wizardto a managed device

The successful execution of a script on theDevice Databasewill create a new revision history

The script history will show successful installation of the script on the remote FortiGate

TheDevice Settings Statuswill be tagged asModified

FortiGate devices in HA cluster devices are counted as a single device.

FortiGate in transparent mode configurations are not counted toward the device count on FortiManager.

FortiGate devices in an HA cluster that has five VDOMs are counted as five separate devices.

The maximum number of managed devices for each ADOM is 500.

Allows FortiManager to download IPS packages

Allows FortiManager to respond to request for FortiGuard services from FortiGate devices

Allows FortiManager to run real-time debugs on the managed devices

Allows FortiManager to automatically configure a default route

The policy package reports inconsistencies and conflicts during aPolicy Consistency Check.

The policy package does not have a FortiGate as the installation target.

The policy package configuration has been changed on both FortiManager and the managed device

independently.

The policy configuration has never been imported after a device was registered on FortiManager.

FortiManager updated the object ALL using the FortiGate value in its database.

FortiManager installed the object ALL with the updated value.

FortiManager created the object ALL as a unique entity in its database, which can be only used by this

managed FortiGate.

FortiManager updated the object ALL using the FortiManager value in its database.

The latest revision history for the managed FortiGate does match with the FortiGate running configuration

Configuration changes have been installed to FortiGate and represents FortiGate configuration has been changed

The latest history for the managed FortiGate does not match with the device-level database

Configuration changes directly made on the FortiGate have been automatically updated to device-level

database

The unused objects that are not tied to the firewall policies will be installed on FortiGate

The unused objects that are not tied to the firewall policies will remain as read-only locally on FortiGate

The unused objects that are not tied to the firewall policies locally on FortiGate will be deleted

The unused objects that are not tied to the firewall policies in policy package will be deleted from the

FortiManager database

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.

The same administrator can lock more than one ADOM at the same time

Ungraceful closed sessions will keep the ADOM in a locked state until the administrator session times out

Unlocking an ADOM will submit configuration changes automatically to the approval administrator

Unlocking an ADOM will install configuration automatically on managed devices

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.

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

Enable SD-WAN central management in theTrainingADOM

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

The address object used in policy ID 2 already exist in ADON database with any as interface association and conflicts with address object interface association locally on the FortiGate

Policy ID 2 is configured from interface any to port6 FortiManager rejects to import this policy because any interface does not exist on FortiManager

Policy ID 2 does not have ADOM Interface mapping configured on FortiManager

Policy ID 2 for this managed FortiGate already exists on FortiManager in policy package named Remote-FortiGate.

FortiGate uptime

FortiGate license information

FortiGate IPS version

FortiGate configuration checksum

FortiManager is unable to determine the policy package status

The policy package was never imported after a device was registered on FortiManager

The Policy configuration has been changed on a managed device and changes have not yet been imported into FortiManager

The Policy package configuration has been changed on FortiManager and changes have not yet been installed on the managed device.

Backs up all devices and the FortiGuard database.

Does not back up firmware images saved on FortiManager

Supports FTP, SCP, and SFTP

Can be configured from the CLI and GUI

It allows FortiManager to manage all FortiGate devices

It allows FortiManager to fun reports based on FortiAnalyzer

It allows FortiManager to store all managed FortiGate device logs

It allows FortiManager to act as a collector and FortiAnalyzer device

The device name of the new device and serial number of the failed device

The device name and serial number of the failed device

The device name of the failed device and serial number of the new device

The device name and serial number of the new device

By a dollar symbol ($) at the end of the device name

By an at symbol (@) at the end of the device name

By a QUESTION NO: mark(?) at the end of the device name

By an Asterisk (*) at the end of the device name

From the list of configured override servers or public FDN servers

From the default server fds1.fortinet.com

From the configured override server IP address 10.0.1.50 only

From public FDNI server IP address with the fourth highest octet only

VPN Manager must be enabled on a per ADOM basis.

VPN Manager automatically adds newly-registered devices to a VPN community.

VPN Manager can install common IPsec VPN settings on multiple FortiGate devices at the same time.

Common IPsec settings need to be configured only once in a VPN Community for all managed gateways.

VPN Manager automatically creates all the necessary firewall policies for traffic to be tunneled by IPsec.

When you configure MEA, you must open TCP or UDP port 540.

You must open the ports to the Fortinet registry

You must create a MEA special policy on FortiManager using the super user profile

The administrator must have the super user profile.