Notifications
Clear all
Topic starter
02/07/2022 12:53 pm
Refer to the exhibit.
Which two statements about the output are true? (Choose two.)
- A . The latest revision history for the managed FortiGate does match with the FortiGate running configuration
- B . Configuration changes have been installed to FortiGate and represents FortiGate configuration has been changed
- C . The latest history for the managed FortiGate does not match with the device-level database
- D . Configuration changes directly made on the FortiGate have been automatically updated
to device-level
database
Suggested Answer: A,C
Explanation:
STATUS: dev-db: modified; conf: in sync; cond: pending; dm: retrieved; conn: upC
dev-db: modified C This is the device setting status which indicates that configuration changes were made on FortiManager.C conf: in sync C This is the sync status which shows that the latest revision history is in sync with Fortigate’s configuration.C cond: pending C 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:C Revision DB does match FortiGate.C No changes were installed to FortiGate yet.C Device DB doesn’t match Revision DB.C 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
Explanation:
STATUS: dev-db: modified; conf: in sync; cond: pending; dm: retrieved; conn: upC
dev-db: modified C This is the device setting status which indicates that configuration changes were made on FortiManager.C conf: in sync C This is the sync status which shows that the latest revision history is in sync with Fortigate’s configuration.C cond: pending C 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:C Revision DB does match FortiGate.C No changes were installed to FortiGate yet.C Device DB doesn’t match Revision DB.C 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