FortiManager Install Preview & Revision History: Review CLI Changes Before Pushing to FortiGate
A FortiManager administrator wants to push policy package changes to a managed FortiGate, but wants to see what changes will be applied before committing. Which FortiManager feature should the administrator use?
⚠ Common exam trap
Many exam-takers confuse revision history (which shows past changes) with install preview (which shows future changes), leading them to select revision history as a way to see pending changes.
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
✓
Install preview
Install preview is the correct feature because it allows the administrator to simulate the installation of policy package changes on a managed FortiGate without actually applying them. This provides a detailed diff of what will be added, modified, or removed, enabling verification before committing the changes. It is specifically designed for pre-commit validation in FortiManager's centralized management workflow.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Install preview
Why this is correct
Install preview generates a read-only diff of the policy package against the FortiGate's running configuration, showing exactly which objects and rules would change. This satisfies the administrator's requirement to inspect pending changes before committing, without altering the device. Installation proceeds only after explicit confirmation.
- ✗
Meta fields
Why it's wrong here
Meta fields are dynamic policy variables populated from device metadata, used to build reusable policy objects across many FortiGates; they do not display pending configuration differences. They tempt because they relate to policy packages. The installation preview, comparing the package against the device's running configuration, is the required feature.
- ✗
Automation stitch
Why it's wrong here
Automation stitches trigger actions in response to events, such as sending alerts or running scripts; they do not preview pending policy differences. The tempting fit is orchestration of repetitive tasks, which is their real purpose. Installation preview, showing exactly what will change before commit, is what this scenario requires.
- ✗
Revision history
Why it's wrong here
Revision history records previously installed policy package versions for rollback and comparison, but does not preview pending uncommitted changes. It is tempting because it does show configuration differences, and it is the correct tool when auditing what a FortiGate ran previously or reverting to an earlier package.
Go deeper
Related to this question
About these practice questions
Courseiva writes every NSE7 question from scratch — 718 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 →
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.