Fortinet FortiManager 7.6 Administrator FCP_FMG_AD-7.6 Exam Dumps: Updated Questions & Answers (September 2025)

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

The administrator can lock policy blocks and FortiManager global ADOM.

The same administrator can lock more than one ADOM at the same time.

The administrator must have access to the ADOM to approve changes.

Assign only one policy package to the firewall because FortiManager does not allow more than one policy package assigned per device at the same time.

Import the policy package to change the unknown status and synchronize the policy package.

Use the install wizard to install the central policy package on the BR1-FGT-1 firewall.

First resolve the modified status in the configuration and provisioning templates to allow a smooth installation.

Configure RADIUS authentication to assign ADOM roles to each user.

Enable workflow mode, which is the only way to prevent concurrent configuration conflicts.

Assign administrators with JSON API access to the FortiManager.

Activate workspace mode in the ADOM settings.

FortiManager sets both the 100.65.0.120 IP address and 10.0.13.120 IP address on FortiGate.

FortiManager sets both the 100.65.0.120 IP address and 100.65.0.101 IP address on FortiGate.

FortiManager sets the 100.65.0.101 IP address on FortiGate.

FortiManager sets the 100.65.0.120 IP address on FortiGate.

The administrator must use a user local meta field to assign FortiToken.

The administrator must use a valid FortiToken that exists on HQ-NGFW-1.

The administrator must use a metadata variable to assign the same FortiToken to multiple users in FortiManager.

The administrator must use per-device mapping to assign the FortiToken to HQ-NGFW-1.

Use the Install Wizard located on the device manager.

Enable workflow mode to allow policy creation and approval.

Make sure the ADOM and FortiGate firmware versions match and use the ADOM policy package.

Use a FortiManager script to apply the configuration changes.

The latest revision history for the managed FortiGate does not match the device-level database.

Configuration changes have been installed on FortiGate, updating policy and device-level database.

The latest revision history for the managed FortiGate does match the FortiManager policy database.

The system template default will override device-level database configurations.

Check and repair the global configuration database before upgrading.

Export firewall policies to Excel, delete them on the ADOM. then reimport them after upgradingthe ADOM.

Find unused firmware templates, then delete them before upgrading.

Limit ADOM revisions before upgrading.

The customer administrator can edit the header policy by using workspace mode on the global ADOM.

The customer administrator can edit the header policy by using workflow mode on the global ADOM and My_ADOM.

The service provider administrator can unlock the global policy from the global ADOM to authorize changes to the customer administrator.

The customer administrator cannot edit the global header policy; only the service provider administrator can make changes from the global ADOM.