FCP_FMG_AD-7.6: FCP - FortiManager 7.6 Administrator Adom Practice Questions

Company policy dictates that any time a change is made to a policy package on FortiManager an ADOM revision is created before the change installed, and that revision is held for a minimum of 90 days. Over the past three months, each installed change has resulted in several unused policies and duplicate objects. The FortiManager administrator plans to upgrade the FortiGate devices and then upgrade the FortiManager ADOM from version 7.4 to 7.6. Which action can the administrator take to avoid slow ADOM upgrades?

• AA. Check and repair the global configuration database before upgrading.
• BB. Export firewall policies to Excel, delete them on the ADOM. then reimport them after upgradingthe ADOM.
• CC. Find unused firmware templates, then delete them before upgrading.
• DD. Limit ADOM revisions before upgrading.

Refer to the exhibit. An administrator added a FortiGate device to FortiManager with the default object settings at the ADOM layer. What can you conclude from the import policy package process of the HQ-NGFW- 1 device?

• AA. The administrator must select Per Platform for all interfaces to correctly detect all interfaces from HQ- NGFW-1.
• BB. The administrator must manually create the port4 interface on the ADOM layer to avoid import policy errors.
• CC. FortiManager will create LAN, port4, and port6 as normalized interfaces at the ADOM layer.
• DD. FortiGate may not work as expected when the administrator does not import all objects.

What is the purpose of ADOM revisions?

• AA. ADOM revisions find unused, duplicate, and unnecessary firewall policies and objects.
• BB. ADOM revisions show specific changes in a policy package when it is installed.
• CC. ADOM revisions compare previous snapshots of the Policy Package and ADOM-level objects with the device-level database.
• DD. ADOM revisions save the current state of all policy packages and objects for an ADOM.