View the following exhibit.
What of the following statements are true regarding the output? (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
|
Download Printable PDF. VALID exam to help you PASS. |
 |
I think it is C and D
A says “does match”, and not “does not match” which would be kind of more intuitive.
A & C
This example shows that FortiGate configuration is in sync with the latest running revision history. However,
changes have been made to device-level settings. That is why the CLI output is showing db:modified and
the cond is showing as pending. Once the changes are installed on FortiGate, it will show db:unmodified
and cond:OK.
Page 153
A & C
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
Study Guide – Page 150