NSE5_FMG-7.2 Fortinet NSE 5 - FortiManager 7.2 Question and Answers

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.

VIP and IP Pools

Firewall policies

Security profiles

Routing

When creating a new policy package, the administrator can select the option to assign the global policy

package to the new policy package

When a new policy package is created, the administrator needs to reapply the global policy package to

ADOM1.

When a new policy package is created, the administrator must assign the global policy package from the global ADOM.

When the new policy package is created, FortiManager automatically assigns the global policy package to the new policy package.

Trainer is not a part of workflow approval group

Trainer does not have full rights over this ADOM

Trainer must close Student’s workflow session before approving the request

Student, who submitted the workflow session, must first self-approve the request

It downloads the latest configuration from the specified FortiGate and performs a reload operation on the device database.

It installs the latest configuration on the specified FortiGate and update the revision history database.

It compares and provides differences in configuration on FortiManager with the current running

configuration of the specified FortiGate.

It installs the provisioning template configuration on the specified FortiGate.

The Install On column value represents successful installation on the managed devices

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

Policy seq#3 will be installed on the Trainer[NAT] VDOM only

Policy seq#3 will be not installed on any managed device

Restore the configuration from a previous backup.

Log in asSuper_Userin order to unlock the ADOM.

Log in using the same administrator account to unlock the ADOM.

Delete the previous admin session manually through the FortiManager GUI or CLI.

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.

It allows FortiGate to unset central management settings.

It allows FortiGate to reboot and recover the previous configuration from its configuration file.

It allows the FortiManager to revert and install a previous configuration revision on the managed FortiGate.

It allows FortiGate to reboot and restore a previously working firmware image.

The administrator logged in using the unsecure protocol HTTP, so the view is restricted.

The administrator profile does not have full access privileges like theSuper_Userprofile.

The administrator IP address is not a part of the trusted hosts configured on FortiManager interfaces.

FortiAnalyzer features are not enabled on FortiManager.

It supports the FortiManager script feature

It allows making configuration changes for managed devices on FortiManager panes

FortiManager automatically installs the configuration difference in revisions on the managed FortiGate

You cannot assign the same ADOM to multiple administrators

FortiGuard database

Global database

Logs

All devices

Device-level database

Revision history database

ADOM-level database

Configuration-level database

When a new policy package is created, it automatically assigns the global policies to the new package.

When a new policy package is created, you need to assign the global policy package from the global

ADOM.

When a new policy package is created, you need to reapply the global policy package to the ADOM.

When a new policy package is created, you can select the option to assign the global policies to the new package.

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

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 # 3 will be installed on all managed devices and VDOMs that are listed under Installation Targets

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

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

It installs device-level changes on the FortiGate device without launching the Install Wizard

It installs all the changes in the device database first and the administrator must reinstall the changes on the FodiGate device

It provides the option to preview only the policy package changes before installing them

It install provisioning template changes on the FortiGate device

Internally upgrades existing ADOMs to the same ADON version in order to clean up and correct the ADOM

syntax

Verifies and corrects unregistered, registered, and deleted device states

Verifies and corrects database schemas in all object tables

Verifies and corrects duplicate VDOM entries

Once initiated, the install process cannot be canceled and changes will be installed on the managed device

Will not create new revision in the revision history

Installs device-level changes to FortiGate without launching theInstall Wizard

Provides the option to preview configuration changes prior to installing them

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.

Authorize the new AP using AP Manager and wait until the change is updated on the FortiAP. Changes to the AP's state do not require installation.

Changes to the AP's state must be performed directly on the managed FortiGate.

Authorize the new AP using AP Manager and install the policy package changes on the managed FortiGate.

Authorize the new AP using AP Manager and install the device level settings on the managed FortiGate.

File system

ADOM1

ADOM2 object database

ADOM2

When FortiManager is auto-updated with configuration changes made directly on a managed device

When changes to the device-level database are made on FortiManager

When FortiManager installs device-level changes on a managed device

When a configuration revision is reverted to a previous revision in the revision history