Cisco®
CompTIA
Checkpoint
ISC
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk®
Scrum
All Vendors
  2. Home
  3. Exams
  4. Fortinet
  5. NSE5_FMG-6.4

Free NSE5_FMG-6.4 Exam Braindumps (page: 3)

Page 2 of 15
PDF with 59 Questions

Which two conditions trigger FortiManager to create a new revision history? (Choose two.)

  1. When configuration revision is reverted to previous revision in the revision history
  2. When FortiManager installs device-level changes to a managed device
  3. When FortiManager is auto-updated with configuration changes made directly on a managed device
  4. When changes to device-level database is made on FortiManager

Answer(s): B,C


Reference:

https://help.fortinet.com/fmgr/50hlp/56/5-6- 1/FortiManager_Admin_Guide/1000_Device%20Manager/1500_Manage_device_configs/0 600_Manage%20config%20rev%20history.htm



Which configuration setting for FortiGate is part of a device-level database on FortiManager?

  1. VIP and IP Pools
  2. Firewall policies
  3. Security profiles
  4. Routing

Answer(s): D

Explanation:

The FortiManager stores the FortiGate configuration details in two distinct databases. The device-level database includes configuration details related to device-level settings, such as interfaces, DNS, routing, and more. The ADOM-level database includes configuration details related to firewall policies, objects, and security profiles.



Refer to the exhibit.



Which two statements about the output are true? (Choose two.)

  1. The latest revision history for the managed FortiGate does match with the FortiGate running configuration
  2. Configuration changes have been installed to FortiGate and represents FortiGate configuration has been changed
  3. The latest history for the managed FortiGate does not match with the device-level database
  4. Configuration changes directly made on the FortiGate have been automatically updated to device-level
    database

Answer(s): A,C

Explanation:

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



An administrator would like to review, approve, or reject all the firewall policy changes made by the junior administrators.

How should the Workspace mode be configured on FortiManager?

  1. Set to workflow and use the ADOM locking feature
  2. Set to read/write and use the policy locking feature
  3. Set to normal and use the policy locking feature
  4. Set to disable and use the policy locking feature

Answer(s): A


Reference:

https://help.fortinet.com/fmgr/50hlp/52/5-2- 0/FMG_520_Online_Help/200_What's-New.03.03.html






Post your Comments and Discuss Fortinet NSE5_FMG-6.4 exam with other Community members: