An ADOM revision in FortiManager creates a versioned snapshot of the central management components within a specific Administrative Domain (ADOM). Its primary purpose is to save the current state of all policy packages and their associated objects. This allows administrators to create a restore point before making significant changes. If a new configuration causes issues, the administrator can revert the ADOM's policy and object database to this previously saved, known-good state.

A. This is incorrect because an ADOM revision specifically saves the policy and object database, not the entire state of the ADOM, which would include device inventory and other settings.

C. This describes an action (reverting) that can be performed using a revision, not the purpose of creating one. Also, device-level settings have their own separate revision history.

D. This is incorrect. System Checkpoints are used to save the entire FortiManager system configuration, not the configuration of a specific ADOM.

1. FortiManager Administration Guide 7.4.0

Chapter: Administrative Domains (ADOMs)

Section: Revisions

Page 131.

The guide states

"You can create a revision of an ADOM. An ADOM revision saves the policy packages and objects for that ADOM. You can revert the ADOM to a previous revision if necessary." This directly supports option B.

2. FortiManager Administration Guide 7.4.0

Chapter: System Settings

Section: Creating system checkpoints

Page 53.

This section describes System Checkpoints as a way to "back up the entire FortiManager configuration

" distinguishing it from ADOM-specific revisions and confirming that option D is incorrect.