FCP_FMG_AD-7.6 · Question #23
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…
The correct answer is D. Limit ADOM revisions before upgrading. Limiting ADOM revisions reduces the number of stored historical configurations, which helps avoid performance degradation and slow ADOM upgrades caused by a large volume of revisions.
Question
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?
Options
- ACheck and repair the global configuration database before upgrading.
- BExport firewall policies to Excel, delete them on the ADOM. then reimport them after upgrading
- CFind unused firmware templates, then delete them before upgrading.
- DLimit ADOM revisions before upgrading.
How the community answered
(55 responses)- A9% (5)
- B5% (3)
- C2% (1)
- D84% (46)
Explanation
Limiting ADOM revisions reduces the number of stored historical configurations, which helps avoid performance degradation and slow ADOM upgrades caused by a large volume of revisions.
Topics
Community Discussion
No community discussion yet for this question.