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

FortiGuard database

Global database

Logs

All devices

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

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

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

During discovery FortiManager sets trie FortiManager NATed IP address on FortiGate

During discovery FortiManager sets both tie FortiManager NATed IP address and NAT device IP address on FortiGate

During discovery FortiManager sets the NATed device IP address on FortiGate

During discovery FortiManager uses only the FortiGate serial number to establish the connection

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

It installs all the changes in the device database first and the administrator must reinstall the changes on the FodiGate device

It provides the option to preview only the policy package changes before installing them

It install provisioning template changes on the FortiGate device

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.

When you configure MEA, you must open TCP or UDP port 540.

You must open the ports to the Fortinet registry

You must create a MEA special policy on FortiManager using the super user profile

The administrator must have the super user profile.

Once initiated, the install process cannot be canceled and changes will be installed on the managed device

Will not create new revision in the revision history

Installs device-level changes to FortiGate without launching the Install Wizard

Provides the option to preview configuration changes prior to installing them

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

10.0.1.0/24

It will create firewall address group on Local-FortiGate with 192.168.0.1/24 and 10.0.1.0/24 object values

192.168.0.1/24

Local-FortiGate will automatically choose an IP Network based on its network interface settings.

Username is admin

Password is fortinet

FortiAnalyzer features are disabled

Reports and Event Monitor panes are enabled

port1 interface IP address is 192.168.1.99/24

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.

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

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.

FortiGate is discovered by FortiManager through the FortiGate NATed IP address.

FortiGate can announce itself to FortiManager only if the FortiManager IP address is configured on

FortiGate under central management.

During discovery, the FortiManager NATed IP address is not set by default on FortiGate.

If the FCFM tunnel is torn down, FortiManager will try to re-establish the FGFM tunnel.

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

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.