Important Fortinet NSE6_FMG_AD-7.6 Exam Questions

Answer: C

Explanation:

FortiManager helps with mass provisioning by using templates that allow administrators to configure the same settings on multiple FortiGate devices simultaneously, streamlining deployment and management.

Answer: D

Explanation:

The correct answer is D. The FortiManager 7.6 Administrator Study Guide gives the exact extract under Web Filter and Email Filter: ''fgdlinkd --- Responsible for downloading web filter and email filter databases''. The same study guide section explains that the execute top command displays real-time CPU and RAM usage, and the %MEM column shows the memory percentage used by each process.

In the exhibit, the line for fgdlinkd shows %MEM 2.9. Therefore, the process responsible for downloading the web and email filter databases is using 2.9% of RAM. That matches option D exactly. The other values belong to different processes, such as fgdsvr and other FortiGuard-related daemons, but not the downloader process identified in the study guide.

=========

Answer: D

Explanation:

ADOM revisions save the current state of all policy packages and objects within an ADOM, allowing administrators to track changes over time and revert to previous configurations if needed.

Answer: B

Explanation:

The correct answer is B. The FortiManager 7.6 Administrator Study Guide gives the exact extract: ''Also note when you upgrade the FortiManager firmware version the existing ADOMs are not automatically upgraded.'' This directly explains why the administrator saw the FortiManager upgrade complete while the ADOM versions remained unchanged.

The same section also explains that ADOM upgrades are a separate action: ''You can upgrade an ADOM in System Settings > ADOMs'' and ''Can upgrade to one version higher at a time.'' In addition, the guide recommends: ''upgrade all devices first, and then upgrade the ADOM.''

So the issue is not workspace mode, locked ADOMs, or a stuck task. The ADOMs simply require their own manual upgrade step after the FortiManager firmware upgrade.

Answer: C, D

Explanation:

The output shows dev-db: not modified; conf: in sync, which means the device-level database is aligned with the latest revision history, so A is false. The study guide explains that ''Synchronized / Auto-update: The latest revision history configuration entry ... is aligned with the configuration on FortiGate,'' and dev-db: not modified indicates the device-level settings are not changed on FortiManager.

For the policy layer, the output shows pkg:[imported]BR1-FGT-1. The study guide states ''Imported: indicates that a policy package was successfully imported for a managed device,'' so the policy package in FortiManager matches what was imported from the managed device context, making C correct.

D is also correct because the lab guide explicitly says ''All Provisioning Templates applied on FortiGate devices have precedence over any configuration you apply on the device layer of the FortiManager.''