Fortinet NSE 5 - FortiManager 7.2

When moving managed FortiGate devices from one ADOM to another, the shared policy package will not be moved to the new ADOM. You will need to import policy packages from the managed devices into the new ADOM.

When an administrator attempts to delete an address object that is currently referenced in a firewall policy on FortiManager with workspace mode enabled, two outcomes are expected. First, FortiManager will replace the deleted address object with the 'none' address object in the referenced firewall policy, effectively making the policy invalid or null. Second, FortiManager will not allow the deletion of a referenced address object unless the ADOM (Administrative Domain) is locked, as objects cannot be modified or deleted without locking the ADOM to ensure consistency and prevent conflicting changes.

Running the Policy Check feature in FortiManager ADOM will find and provide recommendations for optimizing policies in a policy package. This involves evaluating policies for potential issues like duplication, shadowing, overlap, and orphaning, and suggesting improvements based on these criteria.

Assigning an additional global policy package to the same ADOM results in FortiManager removing or replacing previously assigned policies to maintain consistency. Additionally, after assigning a global policy package to an ADOM, you can edit or delete all the global objects within the global ADOM.

When replacing a failed device in FortiManager, the administrator must use the device name of the failed device and the serial number of the new device. This ensures that FortiManager correctly updates its records to reflect the replacement. The command instructs FortiManager to associate the existing device entry with the new hardware by changing only the serial number part of the device's entry, preserving the original device name.