NSE5_FMG-7.2 Questions and Answers

FortiManager updated the object ALL using FortiGate’s value in its database

FortiManager updated the object ALL using FortiManager’s value in its database

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

managed FortiGate.

FortiManager installed the object ALL with the updated value.

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.

Managed gateways are devices managed by FortiManager in the same ADOM

External gateways are third-party VPN gateway devices only

Protected subnets are the subnets behind the device that you don’t want to allow access to over the IPsec

VPN

Managed devices in other ADOMs must be treated as external gateways

Manually promote one of the working secondary devices to the primary role, and reboot the old primary device to remove the peer IP of the failed device.

Reboot the failed device to remove its IP from the primary device.

Reconfigure the primary device lo remove the peer IP of the failed device.

The FortiManager HAfailover is transparent to administrators and does not require any reconfiguration.

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

It allows FortiManager to respond to requests for FortiGuard services from FortiGate devices.

It allows FortiManager to determine the connection status of managed devices.

It allows administrative access to FortiManager.

It allows third-party applications to gain read/write access to FortiManager.

The FortiManager replaces the address object to none.

0.0.0.0/0.

192.168.1.0/24.

10.0.5.0/24.

The administrator must use the Policy & Objects section to create a policy first.

The administrator must use the FortiManager script.

The administrator must disable the FortiManager offline mode first.

The administrator must change the ADOM mode to Advanced to bring the FortiManager online.

The FortiManager administrator must add the authorized device to the Training ADOM using the Add Device wizard only.

The authorized FortiGate will be automatically added to the Training ADOM.

The authorized FortiGate will appear in the root ADOM.

The authorized FortiGate can be added to the Training ADOM using FortiGate Fabric Connectors.

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.

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

VIP and IP Pools

Firewall policies

Security profiles

Routing

Make sure FortiManager Access is enabled in the administrator profile

Make sure Offline Mode is disabled

Make sure the administrator IP address is part of the trusted hosts.

Make sure ADOMs are enabled and the administrator has access to the Global ADOM

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

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

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

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

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

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

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.

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.

Device-level database

Revision history database

ADOM-level database

Configuration-level database

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.