A. The script history shows successful installation of the script on the remote FortiGate device.

B. You must install these changes on a managed device using the Install Wizard.

C. The successful execution of a script on the Device Database creates a new revision history.

D. The device Config Status is tagged as Modified.

A. To ensure database consistency, you must upgrade an ADOM before you upgrade the devices in it.

B. ADOMs using global objects can be upgraded before or after upgrading the global database ADOM.

C. You cannot import policies from a device until its FortiOS version matches the ADOM version.

D. Upgrading the FortiManager version upgrades all existing ADOMs automatically.

A. FortiManager is in workflow mode.

B. An administrator can also lock the Local-FortiGate_root policy package.

C. The FortiManager ADOM workspace mode is set to Normal

D. The FortiManager ADOM is locked by the administrator.

A. The policy configuration has been changed on FortiManager and changes have not yet been installed on the managed device.

B. FortiManager is unable to determine the policy package status.

C. The policy package was never imported after a device was registered on FortiManager.

D. The policy configuration has been changed on a managed device and changes have not yet been imported into FortiManager.

A. SNMP

B. NSX-T Service Template

C. Routing

D. Security profiles

A. To save the current state of all policy packages and objects for an ADOM

B. To revert individual policy packages and device-level settings for a managed FortiGate

C. To save the FortiManager configuration in the System Checkpoints

D. To save the current state of the whole ADOM

A. Check whether FortiManager is part of a high availability (HA) cluster.

B. Determine whether the VDOMs of the same FortiGate will be assigned to different ADOMs.

C. Ensure that FortiAnalyzer features are installed in advance.

D. Confirm that FortiManager has enough storage capacity for the expected logs.