Which two conditions trigger FortiManager to create a new revision history? (Choose two.)
Which two conditions trigger FortiManager to create a new revision history? (Choose two.)
FortiManager creates a new revision history when it is auto-updated with configuration changes made directly on a managed device because it needs to record these external changes. Additionally, when FortiManager installs device-level changes on a managed device, it creates a new revision history to document the specific configuration that was applied during the installation process.
A & C are correct, FM 7.2 study guide pag 174, D is wrong because you revert to a previous revision AND... you must install the changes
AC are correct. In order for D to be correct, you must push the install. B is wrong because no install was pushed after an edit was made to the device database.
AC is the correct answer.
Really tricky one. Unless I am missing something, there are three correct answers: A. Correct. After every auto-update operation FortiManager stores the FortiGate configuration in the revision history. B. Wrong. The device-level database need to be installed for creating a new revision history. C. Correct. After every install operation FortiManager stores the FortiGate configuration in the revision history. D. Correct. Reverted changes must be installed, which creates a new revision entry.
that's right. Question or some answers is wrong. 3 correct answers - A C D -- all of that situations will create new revision on given device
AC is the correct answer
AC is correct.
Should be A and C