Fortinet FCP_FMG_AD-7.6 Exam Dumps

The correct answer is B. The FortiManager 7.6 Administrator Study Guide gives the exact extract: ''Performing a revert operation followed by an installation only reverts device-level changes and does not revert policy packages. To achieve full synchronization, you must run the Import Configuration tool on FortiManager to synchronize the policy package.''

The guide also states: ''After every retrieve, auto-update, or revert operation, you must use Import Configuration to ensure the policy information is synchronized.''

In the exhibit, the missing unset comment for policy ID 1 is a policy package issue, not just a device-level revert issue. Reinstalling the existing policy package does not automatically rebuild it from the reverted revision. The administrator must import the firewall policies again so the policy package reflects the reverted policy state. That is why the comment was not removed.

=========

Using the Install Wizard is the recommended method to reinstall the central policy package on the BR1-FGT-1 firewall, ensuring all settings, installation targets, and dependencies are correctly processed during installation.

Right after moving the ISFW device to a new ADOM, the status typically shows the policy package as never-installed, indicating that the device has been assigned to the new ADOM but no policy package has yet been installed in that ADOM.

The FortiManager 7.6 Administrator Study Guide states under Copying System Templates Between ADOMs: ''The first step is to export the system template from the original ADOM with the execute fmprofile export-profile command'' and shows the output file being written to /tmp/Training, described as ''File copied in FortiManager tmp folder.''

The key point is that the command exports the system template profile from the original ADOM, while /tmp/Backup_File is only the destination path on FortiManager where the exported file is stored. The same study guide also defines system templates as a ''subset of model device configuration---system-level settings'', which means they belong to the device-level side of the ADOM, not the policy database.

So the export source is the ADOM device database, and the file is saved afterward in the FortiManager /tmp folder.

The import report clearly shows: 'firewall profile-protocol-options', SKIPPED, '(name=default, oid=3491, DUPLICATE)'. In FortiManager import reporting, SKIPPED means the object was not imported or updated, and DUPLICATE means an object with that identity already exists in the ADOM database. So FortiManager did not update its database with the imported value for the object default, which makes C correct.

The lab guide reinforces this behavior in the conflict-handling workflow. It explains that during import, FortiManager checks for duplicate names and conflicts, and for conflicting objects the administrator may need to choose whether to keep the value from FortiGate or FortiManager. For the default Firewall Profile-Protocol-Options object, the guide specifically discusses keeping the existing FortiManager value to avoid unnecessary changes.

=========