Fortinet Exam NSE5_FMG-7.0 Topic 3 Question 11 Discussion

STATUS: dev-db: modified; conf: in sync; cond: pending; dm: retrieved; conn: up -- dev-db: modified -- This is the device setting status which indicates that configuration changes were made on FortiManager. -- conf: in sync -- This is the sync status which shows that the latest revision history is in sync with Fortigate's configuration. -- cond: pending -- This is the configuration status which says that configuration changes need to be installed.

Most probably a retrieve was done in the past (dm: retrieved) updating the revision history DB (conf: in sync) and FortiManager device level DB, now there is a new modification on FortiManager device level DB (dev-db: modified) which wasn't installed to FortiGate (cond: pending), hence; revision history DB is not aware of that modification and doesn't match device DB.

Conclusion: -- Revision DB does match FortiGate. -- No changes were installed to FortiGate yet. -- Device DB doesn't match Revision DB. -- No changes were done on FortiGate (auto-update) but configuration was retrieved instead

After an Auto-Update or Retrieve: device database = latest revision = FGT

Then after a manual change on FMG end (but no install yet): latest revision = FGT (still) but now device database has been modified (is different).

After reverting to a previous revision in revision history: device database = reverted revision != FGT

Topic 2, Main Questions Pool B