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

The policy package reports inconsistencies and conflicts during a Policy 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.

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

The administrator profile does not have full access privileges like the Super_User profile.

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

To create System Checkpoints for the FortiManager configuration.

To save the current state of the whole ADOM.

To save the current state of all policy packages and objects for an ADOM.

To revert individual policy packages and device-level settings for a managed FortiGate by reverting to a specific ADOM revision

The administrator profile does not have full access privileges like the Super_User profile

The administrator workflow is enabled on the ADOM.

FortiAnalyzer features are not enabled on FortiManager

The admin session requires approval before administrator can see the FortiAnalyzer feature panes.

The administrator must turn off the Use Legacy Device login and add the FortiAnalyzer device to the same network as Forti-Manager

The administrator must select the Forti-Manager administrative access checkbox on the FortiAnalyzer management interface

The administrator must use the Add Model Device section and discover the FortiAnalyzer device

The administrator must use the correct user name and password of the FortiAnalyzer device

You must manually move the header and footer policies after the policy assignment.

After you assign the global policy package to an ADOM, the policy package is hidden from the ADOM and cannot be viewed.

If you assign an additional global policy package to the same ADOM, FortiManaqer removes previously assigned policies.

You can edit or delete all the global objects in the global ADOM.

File system

ADOM1

ADOM2 object database

ADOM2

The FortiManager ADOM workspace mode is set to Normal.

An administrator can also lock the Local-FortiGate-1 policy package.

The FortiManager ADOM is locked by the administrator.

FortiManager is in workflow mode.

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

FortiManager is unable to determine the policy package status.

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

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

Policy ID 1 is configured from the interface any to port6. FortiManager rejects the request to import this policy because the any interface does not exist on FortiManager.

The address object used in policy ID 1 already exists in the ADOM database with any as the interface association, and conflicts with the address object interface association locally on FortiGate.

Policy ID 1 does not have the ADOM Interface mapping configured on FortiManager.

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

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

Configuration changes have been installed on FortiGate. which means the FortiGate configuration has been changed

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

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

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

It provides recommendations for optimizing policies in a policy package.

It provides recommendations to combine similar policy packages within an ADOM into one single policy package.

It compares the policy packages with the revision history, and updates policy packages in the ADOM database.

It merges and creates dynamic mappings for duplicate objects used in a policy package.

Any pending device settings will be installed automatically

Any unused objects from a previous ADOM are moved to the new ADOM automatically

The shared policy package will not be moved to the new ADOM

Policy packages will be imported into the new ADOM automaticallyD

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.

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

When FortiManager installs device-level changes to a managed device

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

When changes to device-level database is made on FortiManager

From the list of configured override servers with ability to fall back to public FDN servers

From the configured override server list only

From the default server fdsl.fortinet.com

From public FDNI server with highest index number only

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 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

VIP and IP Pools

Firewall policies

Security profiles

Routing

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

FortiGate uptime

FortiGate license information

FortiGate IPS version

FortiGate configuration checksum

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 will install configuration changes to managed device automatically

It will tag the device settings status as Auto-Update

It will generate a new version ID and remove all other revision history versions

It will modify the device-level database

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.

You must install these changes using the Install Wizard to a managed device

The successful execution of a script on the Device Database will create a new revision history

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

The Device Settings Status will be tagged as Modified