NSE5_FMG-7.2 Sample Questions Answers

The FortiManaqer HA state transition is transparent to administrators and does not require any reconfiguration.

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.

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

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

The API command has enabled both central NAT and interface policy on the policy tab.

The API command has requested the policy tab permissions information only.

The API command has failed when requesting policy tab permissions information.

The API command has applied to customer with ID: 200.

The FortiManager replaces the address object to none.

0.0.0.0/0.

192.168.1.0/24.

10.0.5.0/24.

First create an SD-WAN firewall policy, add member interfaces to the SD-WAN template and create a static route

You must specify a gateway address when you create a default static route

Remove all the interface references such as routes or policies

Enable SD-WAN central management in the ADOM, add member interfaces, create a static route and SDWAN firewall policies.

VIP and IP Pools

Firewall policies

Security profiles

Routing

Two or more administrators can make configuration changes at the same time, in the same ADOM.

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

Concurrent read-write access to an ADOM is disabled. Most Voted

You can validate administrator login attempts through external servers.

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.

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

The DNS addresses in the default system settings are the same as the Training system template

The Training system template has other default settings

The ADOM is locked by another administrator

The Training system template does not have assigned devices

The setting allows automatic updates to the policy package configuration for a managed device

The setting enables the ADOMs feature on FortiManager

This setting allows you to assign different VDOMs from the same FortiGate to different ADOMs.

The setting disables concurrent ADOM access and adds ADOM locking

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

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.

It does not back up firmware images saved on FortiManager.

It can be configured using the CLI and GUI.

It backs up all devices and the FortiGuard database.

It supports FTP, SCP, and SFTP.

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

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

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

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 allows two or more administrators to make configuration changes at the same time, in the same ADOM.

It disables concurrent read-write access to an ADOM.

It allows the same administrator to lock more than one ADOM at the same time.

It is used to validate administrator login attempts through external servers.

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

Restore the configuration from a previous backup.

Log in as Super_User in 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.

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.

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.

Device-level database

Revision history database

ADOM-level database

Configuration-level database

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

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.