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? (Choose one answer)

A. Check and repair the global configuration database before upgrading.
B. Export firewall policies to Excel, delete them on the ADOM, then reimport them after upgrading the ADOM.
C. Find unused firmware templates, then delete them before upgrading.
D. Limit ADOM revisions before upgrading.

Correct Answer: D

Brave-Dump Clients Votes

D 100%

Comments

Saeed Abd El Halim Hamada 2025-07-16 22:39:04

Selected Answers: D

Correct Answer Is D
Explanation:
When an ADOM is upgraded in FortiManager, the system processes all data associated with that ADOM — including:

Policy packages
Objects
Device settings
ADOM revisions

Why Too Many Revisions Cause Problems:

Each ADOM revision is a snapshot of all policies and objects at a point in time.
Over time, dozens or hundreds of revisions can accumulate, especially in high-change environments.
During an ADOM upgrade, FortiManager processes and verifies all revisions, which can slow down or even fail the upgrade if the system is overloaded or revisions are corrupt.

Why the other options are incorrect:

A. Global configuration database issues are not related to ADOM upgrade speed.
B. Exporting/deleting/reimporting firewall policies manually is risky, error-prone, and not needed.
C. Firmware templates are not stored inside the ADOM, and have no impact on ADOM upgrade performance.