Fortinet NSE5_FMG-7.2 Exam Questions Instant Access

Question 1

When an installation is performed from FortiManager, what is the recovery logic used between FortiManager and FortiGate for an FGFM tunnel?

AAfter 15 minutes, FortiGate will unset all CLI commands that were part of the installation that caused the tunnel to go down.

BFortiManager will revert and install a previous configuration revision on the managed FortiGate.

CFortiGate will reject the CLI commands that will cause the tunnel to go down.

DFortiManager will not push the CLI commands as a part of the installation that will cause the tunnel to go down.

Answer : A

The configuration change will break the fgfm connection, causing the FortiGate unit to attempt to reconnect for 900 seconds. If the FortiGate cannot reconnect, it will rollback to its previous configuration.

Question 2

Refer to the following exhibit:

Which of the following statements are true based on this configuration? (Choose two.)

AThe same administrator can lock more than one ADOM at the same time

BUngraceful closed sessions will keep the ADOM in a locked state until the administrator session times out

CUnlocking an ADOM will submit configuration changes automatically to the approval administrator

DUnlocking an ADOM will install configuration automatically on managed devices

Answer : A, B

Question 3

Push updates are failing on a FortiGate device that is located behind a NAT device Which two settings should the administrator check? (Choose two.)

AThat the virtual IP address and correct ports are set on the NAT device

BThat the NAT device IP address and correct ports are configured on FortiManager

CThat the external IP address on the NAT device is set to DHCP and configured with the virtual IP

DThat the override server IP address is set on FortiManager and the NAT device

Answer : B, C

Question 4

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

AVIP and IP Pools

BFirewall policies

CSecurity profiles

DRouting

Answer : C

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.

Question 5

View the following exhibit.

What is the purpose of setting ADOM Mode to Advanced?

AThe setting allows automatic updates to the policy package configuration for a managed device

BThe setting enables the ADOMs feature on FortiManager

CThis setting allows you to assign different VDOMs from the same FortiGate to different ADOMs.

DThe setting disables concurrent ADOM access and adds ADOM locking

Answer : C

Question 6

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

AThe Security Fabric license, group name and password are required for the FortiManager Security Fabric
integration

BThe Fabric View module enables you to generate the Security Fabric ratings for Security Fabric devices

CThe Security Fabric settings are part of the device level settings

DThe Fabric View module enables you to view the Security Fabric ratings for Security Fabric devices

Answer : C, D

Question 7

Refer to the exhibit.

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

AThe latest revision history for the managed FortiGate does match with the FortiGate running configuration

BConfiguration changes have been installed to FortiGate and represents FortiGate configuration has been changed

CThe latest history for the managed FortiGate does not match with the device-level database

DConfiguration changes directly made on the FortiGate have been automatically updated to device-level
database

Answer : 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

Topic 2, Main Questions Pool B

Fortinet NSE 5 - FortiManager 7.2 NSE5_FMG-7.2 Exam Questions