FCP_FMG_AD-7.6 Exam Dumps - FortiManager 7.6 Administrator

ADOM revisions find unused, duplicate, and unnecessary firewall policies and objects.

ADOM revisions show specific changes in a policy package when it is installed.

ADOM revisions compare previous snapshots of the Policy Package and ADOM-level objects with the device-level database.

ADOM revisions save the current state of all policy packages and objects for an ADOM.

FortiManager does not support per-device mapping for firewall addresses.

The administrator will see a new policy package named Remote-FortiGate_root in the FortiManager ADOM database.

FortiManager will change the configuration of REMOTE_SUBNET to match the interface mapping coming in from Remote-FortiGate.

As a result of this policy import process, FortiManager will create a new firewall address called REMOTE_SUBNET in the ADOM database.

FortiManager sets both the 100.65.0.120 IP address and 10.0.13.120 IP address on FortiGate.

FortiManager sets both the 100.65.0.120 IP address and 100.65.0.101 IP address on FortiGate.

FortiManager sets the 100.65.0.101 IP address on FortiGate.

FortiManager sets the 100.65.0.120 IP address on FortiGate.

Configure an TCL script to run locally on FortiManager for each FortiGate.

Restrict administrators with an administration profile from viewing the revision history to limit who can make changes.

Enable the change note to require administrators to add a note whenever they change object configurations.

Enable a workflow requiring approval before installing policy packages on any FortiGate.

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.