Which two conditions trigger FortiManager to create a new revision history? (Choose two.)

FortiManager automatically tracks device-level configuration changes by creating new entries in the Revision History table under specific operational triggers. First, whenever FortiManager successfully performs an installation operation that pushes device-level configuration changes to a managed FortiGate, a new revision entry is logged to represent the installed baseline. Second, when configuration modifications are performed directly on the FortiGate CLI or GUI, FortiManager detects the out-of-sync status and automatically retrieves or auto-updates its configuration from the managed device, creating a corresponding revision history entry. Both of these actions ensure complete auditability of deployed device configurations across FortiManager and managed FortiGate units.

Option B: Modifying the device-level database in FortiManager only alters the staging database and does not generate a revision entry until an install or retrieve occurs.

Option D: Assigning a provisioning template modifies FortiManager's database settings, but a revision history entry is created only when those template settings are installed.

- Fortinet

FortiManager 7.4.0 Administration Guide

"Creating revision histories" section.

- Fortinet Training Institute

FortiManager 7.2 Study Guide

"Device Manager - Revision History Triggers" chapter

pp. 82-85.