Pass the Fortinet Network Security Expert FCP_FMG_AD-7.6 Questions and answers with ValidTests

The administrator set the flag to 0 to prevent configuration overrides.

The administrator reinstalled the policy package.

The administrator needs to retrieve the device to correctly detect the FortiGate firmware version.

The administrator installed only the device-level configuration.

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

Manually promote one of the working secondary devices to the primary role: and reboot the original primary device to remove the peer IP address of the failed device.

Reconfigure the primary device to remove the peer IP address of the failed device from its configuration.

Check the integrity database of the primary device to force a secondary device to become the new primary with all active interfaces.

The administrator must use a user local meta field to assign FortiToken.

The administrator must use a valid FortiToken that exists on HQ-NGFW-1.

The administrator must use a metadata variable to assign the same FortiToken to multiple users in FortiManager.

The administrator must use per-device mapping to assign the FortiToken to HQ-NGFW-1.

The administrator must select Per Platform for all interfaces to correctly detect all interfaces from HQ-NGFW-1.

The administrator must manually create the port4 interface on the ADOM layer to avoid import policy errors.

FortiManager will create LAN, port4, and port6 as normalized interfaces at the ADOM layer.

FortiGate may not work as expected when the administrator does not import all objects.

FortiGate must enable rating for the FortiManager IP address, 192.168.1.120, in server list 1.

FortiManager and FortiGate have different IPS database versions.

The administrator must enable IPv6 connections for FortiGuard services on FortiManager.

The administrator must enable the fortiguard-anycast option to correctly download all signatures from the local FDS.

The administrator will be able to select the option to assign the global policy package to the new policy package.

FortiManager will automatically assign the global policy package to the new policy package.

FortiManager will automatically install policies on the policy package in ADOM1.

The administrator will have to assign the global policy package from the global ADOM.

The FortiGate-HQ must be managed under the FortiManager ADOM—root to allow moving its VDOMs to different ADOMs.

The administrator must have full access in the device layer of FortiGate-HQ VDOM-root before they can VDOMs to different ADOMs.

FortiManager must be in ADOM normal mode, which does not allow VDOMs to be managed separately.

The administrator must delete the FortiGate-HQ device from FortiManager and add it again using the Add Device wizard before moving the VDOM.

Check and repair the global configuration database before upgrading.

Export firewall policies to Excel, delete them on the ADOM. then reimport them after upgradingthe ADOM.

Find unused firmware templates, then delete them before upgrading.

Limit ADOM revisions before upgrading.

You can add them to objects as custom attributes.

You can export them to be used in other ADOMs.

You can use them as variables in scripts.

You can invoke them using the $ character.

Enable the prompt asking the administrator to accept firewall policies changes before saving.

Enable the workspace (for all ADOMs) to control all changes made by any administrator.

Enable device lock and the advanced mode feature in the ADOM.

Enable workflow mode and the ADOM lock feature.