Download Fortinet NSE 5 -FortiManager 7-2.NSE5_FMG-7.2.VCEplus.2024-05-01.34q.tqb
| Vendor: | Fortinet |
| Exam Code: | NSE5_FMG-7.2 |
| Exam Name: | Fortinet NSE 5 -FortiManager 7-2 |
| Date: | May 01, 2024 |
| File Size: | 3 MB |
How to open VCEX files?
Files with VCEX extension can be opened by ProfExam Simulator.
Discount: 20%
Demo Questions
Question 1
An administrator would like to create an SD-WAN using central management in the Training ADOM.
To create an SD-WAN using central management, which two steps must be completed? (Choose two.)
- Specify a gateway address when you create a default SD-WAN static route
- Enable SD-WAN central management in the Training ADOM
- Configure and install the SD-WAN firewall policy and SD-WAN static route before installing the SD-WAN template settings
- Remove all the interface references such as routes or policies that will be a part of SD-WAN member interfaces
Correct answer: BD
Question 2
View the following exhibit:
Which two statements are true if the script is executed using the Remote FortiGate Directly (via CLI) option? (Choose two.)
- You must install these changes using Install Wizard
- FortiGate will auto-update the FortiManager's device-level database.
- FortiManager will create a new revision history.
- FortiManager provides a preview of CLI commands before executing this script on a managed FortiGate.
Correct answer: BC
Question 3
Refer to the exhibit.
Which two statements about the output are true? (Choose two.)
- The latest revision history for the managed FortiGate does match with the FortiGate running configuration
- Configuration changes have been installed to FortiGate and represents FortiGate configuration has been changed
- The latest history for the managed FortiGate does not match with the device-level database
- Configuration changes directly made on the FortiGate have been automatically updated to device-level database
Correct answer: AC
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 insteadAfter an Auto-Update or Retrieve: device database = latest revision = FGTThen 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 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
HOW TO OPEN VCE FILES
Use VCE Exam Simulator to open VCE files
HOW TO OPEN VCEX AND EXAM FILES
Use ProfExam Simulator to open VCEX and EXAM files
ProfExam at a 20% markdown
You have the opportunity to purchase ProfExam at a 20% reduced price
Get Now!