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

Question

Options

• AWhen FortiManager installs device-level changes on a managed device
• BWhen changes to the device-level database are made on FortiManager
• CWhen FortiManager is auto-updated with configuration changes made directly on a managed
• DWhen a provisioning template is assigned to a managed device on the device-level database

• A
  71% (44)
• B
  8% (5)
• D
  21% (13)

Explanation

Conditions for Revision History and Troubleshooting FortiManager creates a revision history when: 1- FortiGate is added to FortiManager 2- Device changes are installed 3- FortiGate configuration is retrieved from FortiManager 4- A local change on FortiGate causes an automatic update Scripts run directly on remote devices also cause automatic updates and create a revision history 5- You revert to a previous revision and install the changes How to check managed FortiGate configuration issues: 1- View and download FortiGate configuration revision Compare differences between revisions 2- View who made the changes 3- View what has been installed on the managed device

No community discussion yet for this question.