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

Device name and serial number of the original device.

Device name and serial number of the replacement device.

Device name of the replacement device and serial number of the original device.

Device name of the original device and serial number of the replacement device.

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.

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.

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

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 administrator had restored the FortiManager configuration file

The administrator must refresh both devices to restore connectivity

FortiManager test internet connectivity therefore, both devices appear to be down

The administrator can reclaim the FGFM tunnel to get both devices online

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

FortiManager ignored the firewall service category General but created a new service category in its database.

FortiManager ignored the firewall service category general and deleted the duplicate value In Its database

FortiManager ignored the firewall service category General and updated the FortiGate duplicate value in the FortiGate database.

FortiManager ignored the firewall service category General and did not update Its database with the value

Admin A can access VDOM2 and VDOM3 with the super user profile.

The FortiManager policies and objects database can be shared between the Financial and HR ADOMs.

The administrator must set the FortiManager ADOM mode to Advanced.

The administrator must configure FortiManager in workspace mode.

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.

The administrative domain is disabled.

The Port1 interface IP address is 192.168.1.99/24.

Management Extension applications are enabled.

The FortiManager setup wizard is disabled.

FortiAnalvzer features are disabled.

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

This setting will enable the ADOMs feature on FortiManager.

This setting is applied globally to all ADOMs.

This setting will allow assigning different VDOMs from the same FortiGate to different ADOMs.

This setting will allow automatic updates to the policy package configuration for a managed device.

ADOM revisions can significantly increase the size of the configuration backups.

ADOM revisions can save the current size of the whole ADOM

ADOM revisions can create System Checkpoints for the FortiManager configuration

ADOM revisions can save the current state of all policy packages and objects for an ADOM

FortiGate uptime

FortiGate license information

FortiGate IPS version

FortiGate configuration checksum

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.

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.

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

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

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

It will not create a new revision in the revision history

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

It cannot be canceled once initiated and changes will be installed on the managed device

It provides the option to preview configuration changes prior to installing them

You must install these changes using Install Wizard

FortiGate will auto-update the FortiManager’s device-level database.

FortiManager will create a new revision history.

FortiManager provides a preview of CLI commands before executing this script on a managed FortiGate.

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.

Device-level database

Revision history database

ADOM-level database

Configuration-level database

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