Correct answers are B & D:
FortiManager 7.2 Study Guide page 160
"conf: in sync" means FortiGate configuration is in sync with the latest running revision history.
"db: modified" and "cond: pending" means that changes have been made to the device-level settings and need to be installed.
The example on this slide shows that the FortiGate configuration is in sync with the latest running revision history. However, changes have been made to the device-level settings. That is why the CLI output is showing db:modified and the cond is showing as pending. After you install the changes on FortiGate, it will show db: not modified and cond:OK.
db:modified = Config changes made on FMG
cond:in sync = Latest revision history in sync with FGT running-config
cond:pending = Config changes needed to be installed
Reference [Page 160] - https://ebin.pub/fortinet-fortimanager-study-guide-for-fortimanager-72.html
B. The output indicates "STATUS: dev-0: modified," suggesting that there have been modifications to the FortiGate configuration. This implies that the latest revision history for the managed FortiGate does match the FortiGate running configuration.
D. The output includes information about the status and synchronization, and it mentions "cont: 0 sync: second: pending: dr: received: com:." This suggests that there might be differences or pending changes between the FortiGate and the device-level database, indicating that the latest revision history for the managed FortiGate does not match the device-level database.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
DatBroNZ
3 months, 3 weeks agoDaniSerb
3 months, 3 weeks agoSatekhi
12 months agoGeniusA
12 months ago