NSE5_FMG-7.0 Sample Questions Answers

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

Device-level database

Revision history database

ADOM-level database

Configuration-level database

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.

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.

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

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

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

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.

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

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

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.

FortiManager will not allow the administrator to delete a referenced address object

FortiManager will disable the status of the referenced firewall policy

FortiManager will replace the deleted address object with the none address object in the referenced

firewall policy

FortiManager will replace the deleted address object with all address object in the referenced firewall policy

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

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

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.

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.

By a dollar symbol ($) at the end of the device name

By an at symbol (@) at the end of the device name

By a QUESTION NO: mark(?) at the end of the device name

By an Asterisk (*) at the end of the device name

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.

port1 on FortiGate and WAN on FortiManager

port1 on both FortiGate and FortiManager

WAN zone on FortiGate and WAN zone on FortiManager

WAN zone on FortiGate and WAN interface on FortiManager

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