A FortiGate device shows a policy that is different from what is in the FortiManager policy package assigned to it. The administrator checks the device's configuration and confirms the policy is out of sync. What is the most likely cause and the correct first step to resolve it?

The FortiGate has a different firmware version; upgrade the device.

The device was configured locally outside of FortiManager; import the device configuration to re-sync.

The FortiManager database is corrupted; reboot FortiManager.

The policy package was never installed; run the install wizard again.

In a multi-admin environment, how does FortiManager's workflow mode help manage policy changes?

It logs all changes but does not require approval

It prevents all administrators from making changes unless they are the super admin

It requires changes to be submitted and approved before they can be installed

It automatically reverts any change that is not approved within 24 hours

What is a common method to troubleshoot policy synchronization issues between FortiManager and FortiGate?

Deleting the device from FortiManager and re-adding it

Checking the synchronization status and reviewing the device's configuration revision history

Rebooting the FortiGate device to force a re-synchronization

Changing the FortiGate's administrative password

After installing a new policy package to a FortiGate device, the network team notices that a legitimate application is now blocked. The previous policy package was working correctly. What is the fastest way to restore service while preserving the ability to audit why the change was made?

Manually edit the policy on the FortiGate CLI to allow the application.

Delete the policy package from FortiManager and re-create it from scratch.

Use FortiManager's revision history to roll back to the previous policy package version.

Reboot the FortiGate device to revert to the last saved configuration.

A FortiGate device is not receiving policy updates from FortiManager. The administrator verifies that the device is online and the management tunnel is up. The last install was successful, but subsequent changes to the policy package are not being pushed. What is the most likely cause?

The FortiGate device has been rebooted and lost the management tunnel.

The FortiManager database is corrupted.

The policy package was not re-installed after the changes were made.

The FortiGate device is in a different ADOM than the policy package.

FortinetNSE 7 - Enterprise Firewall Administrator

Domain 2Objective 2

Policy and Object Management at Scale NSE7-ENTERPRISE-FIREWALL-ADMINISTRATOR Practice Questions (Page 4)

Part of the Central Management domain, which makes up ~25% of our current practice bank. Fortinet does not publish an official question count, but from its 70-minute exam (~30–45 total, ~8–11 in this domain), expect 3–4 from this objective — we provide 22 practice questions to prepare you well beyond it. (estimate)

22questions here

5free pages

7concepts

Questions 16–20

16application · medium
A FortiGate device shows a policy that is different from what is in the FortiManager policy package assigned to it. The administrator checks the device's configuration and confirms the policy is out of sync. What is the most likely cause and the correct first step to resolve it?
Select an answer first
17foundation · easy
In a multi-admin environment, how does FortiManager's workflow mode help manage policy changes?
Select an answer first
18foundation · easy
What is a common method to troubleshoot policy synchronization issues between FortiManager and FortiGate?
Select an answer first
19application · medium
After installing a new policy package to a FortiGate device, the network team notices that a legitimate application is now blocked. The previous policy package was working correctly. What is the fastest way to restore service while preserving the ability to audit why the change was made?
Select an answer first
20expert · hard
A FortiGate device is not receiving policy updates from FortiManager. The administrator verifies that the device is online and the management tunnel is up. The last install was successful, but subsequent changes to the policy package are not being pushed. What is the most likely cause?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to NSE7-ENTERPRISE-FIREWALL-ADMINISTRATOR

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Fortinet. “NSE7-ENTERPRISE-FIREWALL-ADMINISTRATOR” is a trademark of its owner, used for identification only.