Enforce Policy Packages with FortiManager Central Management
A company is deploying a Security Fabric with multiple FortiGate devices managed by FortiManager. The administrator wants to apply a policy package to multiple FortiGate devices in the Fabric. However, after assigning the policy package to the devices in FortiManager and installing the configuration, the policies are not applied consistently across all devices. The administrator notices that some devices have local policies that override the policy package. What is the best practice to ensure that the policy package is enforced on all devices?
Quick Answer
The answer is to enable Central Management in FortiManager and use Install On Policy Package to push policies. This is correct because Central Management makes the policy package the authoritative source for all managed FortiGate devices, ensuring that when you install the policy package, FortiManager overwrites any local policies that might otherwise persist and cause inconsistencies across the Security Fabric. On the Fortinet NSE 7 Advanced Security NSE7 exam, this concept tests your understanding of how FortiManager enforces centralized control versus allowing device-level autonomy, often appearing in scenarios where local policies silently override pushed configurations. A common trap is assuming a simple policy assignment is enough, but without Central Management enabled, devices retain local policies that take precedence. Memory tip: think of Central Management as the “override switch”—if it’s off, local rules win; if it’s on, the package rules all.
⚠ Common exam trap
Many candidates assume that simply installing a policy package via FortiManager is enough to override local policies, without realizing that 'Central Management' must be explicitly enabled to prevent local policy edits from persisting and overriding the pushed configuration.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Enable 'Central Management' in FortiManager and use 'Install On Policy Package' to push policies.
Enabling 'Central Management' in FortiManager ensures that the policy package is the authoritative source for all managed FortiGate devices. When 'Install On Policy Package' is used, FortiManager overwrites any local policies on the devices, enforcing consistent policy application across the Security Fabric. Without central management, local policies can persist and override the pushed policy package, leading to inconsistencies.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Enable 'Central Management' in FortiManager and use 'Install On Policy Package' to push policies.
Why this is correct
Central management enforces that only policies from FortiManager are active.
- ✗
Disable the 'Auto Update' feature on the managed devices.
Why it's wrong here
Auto Update affects firmware, not policy enforcement.
- ✗
Use the same policy package name on all devices and manually sync them.
Why it's wrong here
Manual sync is error-prone and not a best practice.
- ✗
Ensure that the Security Fabric is fully established and all devices are visible in the topology.
Why it's wrong here
Fabric connectivity does not prevent local policies.
Go deeper
Related to this question
About these practice questions
Courseiva writes every NSE7 question from scratch — 940 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on NSE7
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Refer to the exhibit. A FortiGate is connected to the Security Fabric and registered with FortiManager. However, the administrator notices that the FortiGate is not receiving policy updates from FortiManager. What is the most likely cause?
hard- A.The Fabric Root serial number is incorrect
- B.The FortiGate is not registered with FortiManager
- ✓ C.The policy package on FortiManager is not assigned to the correct device group or policy target
- D.The Security Fabric is not fully connected
Why C: FortiManager uses policy packages that must be explicitly assigned to a device group or specific FortiGate. Even if the FortiGate is registered and part of the Security Fabric, if the policy package is not assigned to the correct device group or policy target, the FortiGate will not receive policy updates. This is a common misconfiguration where the policy package exists but is not linked to the device.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This NSE7 practice question is part of Courseiva's free Fortinet certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the NSE7 exam.