Fortinet NSE5_FMG-7.2 Practice Test - Questions Answers, Page 4

List of questions
Question 31

View the following exhibit.
Given the configurations shown in the exhibit, what can you conclude from the installation targets in the Install On column?
Question 32

View the following exhibit.
An administrator is importing a new device to FortiManager and has selected the shown options. What will happen if the administrator makes the changes and installs the modified policy package on this managed FortiGate?
Question 33

View the following exhibit, which shows the Download Import Report:
Why it is failing to import firewall policy ID 2?
FortiManager_6.4_Study_Guide-Online -- page 331 & 332
Question 34

View the following exhibit:
Which two statements are true if the script is executed using the Remote FortiGate Directly (via CLI) option? (Choose two.)
Question 35

Refer to the exhibit.
Which two statements about the output are true? (Choose two.)
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
Question 36

Which two statements regarding device management on FortiManager are true? (Choose two.)
Question 37

Which two statements about Security Fabric integration with FortiManager are true? (Choose two.)
Question 38

Refer to the exhibit.
Which two statements are true if the script is executed using the Device Database option? (Choose two.)
Question 39

Refer to the exhibit.
An administrator logs into the FortiManager GUI and sees the panes shown in the exhibit.
Which two reasons can explain why the FortiAnalyzer feature panes do not appear? (Choose two.)
Question 40

Which two items are included in the FortiManager backup? (Choose two.)
Question