NSE5_FMG-7.0 Questions and Answers

NSX-T Service Template

Security profiles

SNMP

Routing

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.

That the virtual IP address and correct ports are set on the NAT device

That the NAT device IP address and correct ports are configured on FortiManager

That the external IP address on the NAT device is set to DHCP and configured with the virtual IP

That the override server IP address is set on FortiManager and the NAT device

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

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.

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.

FortiGate uptime

FortiGate license information

FortiGate IPS version

FortiGate configuration checksum

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

Specify a gateway address when you create a default SD-WAN static route

Enable SD-WAN central management in the Training ADOM

Configure and install the SD-WAN firewall policy and SD-WAN static route before installing the SD-WAN

template settings

Remove all the interface references such as routes or policies that will be a part of SD-WAN member

interfaces

VIP and IP Pools

Firewall policies

Security profiles

Routing

When configuration revision is reverted to previous revision in the revision history

When FortiManager installs device-level changes to a managed device

When FortiManager is auto-updated with configuration changes made directly on a managed device

When changes to device-level database is made on FortiManager

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

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

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

FortiGuard database

Global database

Logs

All devices

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