Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 45
Question 440
An MSP must reverse a widespread shared object rename without restoring unrelated local FortiGate interface changes. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: A
The question is set in this situation: An MSP must reverse a widespread shared object rename without restoring unrelated local FortiGate interface changes. Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path. Confirm it through this test: Save an ADOM revision, alter a harmless shared object and package order in a lab, inspect the differences and restore only an approved central baseline without affecting unrelated device-only settings. An ADOM revision records central policy/object state at a point in time; a device configuration revision for one FortiGate cannot replace the broader ADOM snapshot used to recover shared packages.
The action is applicable: Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path. But its proposed test—Produce two lab ADOM revisions with separate service-object and rule-order edits, compare them and validate one selected rollback while keeping the unrelated approved change.—addresses “Compare two FortiManager ADOM revisions to isolate a shared object change”. This requirement is confirmed instead by: Save an ADOM revision, alter a harmless shared object and package order in a lab, inspect the differences and restore only an approved central baseline without affecting unrelated device-only settings.
The test would be relevant: Save an ADOM revision, alter a harmless shared object and package order in a lab, inspect the differences and restore only an approved central baseline without affecting unrelated device-only settings. But the offered implementation—Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified.—addresses “Compare two FortiManager ADOM revisions to isolate a shared object change”. The action needed here is: Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path.
This action/test pair addresses “Reconcile ADOM revision recovery with package installation state on managed FortiGates”. After restoring or choosing an approved FortiManager ADOM revision, preview and explicitly install the corresponding policy package to affected target devices and verify their actual enforced revision. Restore a test ADOM revision, confirm the central package version changed, inspect a staged FortiGate's still-running old policy, then install and verify the approved restored package. The case instead calls for: Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path.
Question 441
A bank discovers a shared address object was modified during maintenance but another team's emergency policy fix also occurred afterward. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: C
Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path. This addresses “Capture a FortiManager ADOM revision before a shared policy reorganization”, where the governing principle is: An ADOM revision records central policy/object state at a point in time; a device configuration revision for one FortiGate cannot replace the broader ADOM snapshot used to recover shared packages. The stated case instead calls for: Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified.
After restoring or choosing an approved FortiManager ADOM revision, preview and explicitly install the corresponding policy package to affected target devices and verify their actual enforced revision. This addresses “Reconcile ADOM revision recovery with package installation state on managed FortiGates”, where the governing principle is: An ADOM revision changes central database content; existing FortiGates do not automatically roll back running policies merely because an older management snapshot was selected. The stated case instead calls for: Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified.
Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified. Comparing central snapshots distinguishes authorized changes from accidental object drift; blindly restoring an older snapshot may erase independent legitimate edits made later in the same ADOM. Verify the result with this test: Produce two lab ADOM revisions with separate service-object and rule-order edits, compare them and validate one selected rollback while keeping the unrelated approved change.
Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change. This addresses “Enable FortiManager workspace mode for concurrent policy editing”, where the governing principle is: Workspace locking coordinates concurrent write sessions inside FortiManager, preventing conflicting central edits; authentication alone does not serialize administrators editing the same object. The stated case instead calls for: Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified.
Question 442
A bank discovers a shared address object was modified during maintenance but another team's emergency policy fix also occurred afterward. The engineer proposes the following change: Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified. Which mechanism explains why it works?
Answer & Explanations
Correct answer: B
Workspace locking coordinates concurrent write sessions inside FortiManager, preventing conflicting central edits; authentication alone does not serialize administrators editing the same object. That explains “Enable FortiManager workspace mode for concurrent policy editing”, not the mechanism behind the described change. The relevant principle is: Comparing central snapshots distinguishes authorized changes from accidental object drift; blindly restoring an older snapshot may erase independent legitimate edits made later in the same ADOM.
Comparing central snapshots distinguishes authorized changes from accidental object drift; blindly restoring an older snapshot may erase independent legitimate edits made later in the same ADOM. The corresponding implementation is: Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified.
An ADOM revision records central policy/object state at a point in time; a device configuration revision for one FortiGate cannot replace the broader ADOM snapshot used to recover shared packages. That explains “Capture a FortiManager ADOM revision before a shared policy reorganization”, not the mechanism behind the described change. The relevant principle is: Comparing central snapshots distinguishes authorized changes from accidental object drift; blindly restoring an older snapshot may erase independent legitimate edits made later in the same ADOM.
An ADOM revision changes central database content; existing FortiGates do not automatically roll back running policies merely because an older management snapshot was selected. That explains “Reconcile ADOM revision recovery with package installation state on managed FortiGates”, not the mechanism behind the described change. The relevant principle is: Comparing central snapshots distinguishes authorized changes from accidental object drift; blindly restoring an older snapshot may erase independent legitimate edits made later in the same ADOM.
Question 443
A bank discovers a shared address object was modified during maintenance but another team's emergency policy fix also occurred afterward. After implementing this change—Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: D
Save an ADOM revision, alter a harmless shared object and package order in a lab, inspect the differences and restore only an approved central baseline without affecting unrelated device-only settings. That would help test “Capture a FortiManager ADOM revision before a shared policy reorganization”, not the outcome required in this scenario. The relevant acceptance check is: Produce two lab ADOM revisions with separate service-object and rule-order edits, compare them and validate one selected rollback while keeping the unrelated approved change.
Restore a test ADOM revision, confirm the central package version changed, inspect a staged FortiGate's still-running old policy, then install and verify the approved restored package. That would help test “Reconcile ADOM revision recovery with package installation state on managed FortiGates”, not the outcome required in this scenario. The relevant acceptance check is: Produce two lab ADOM revisions with separate service-object and rule-order edits, compare them and validate one selected rollback while keeping the unrelated approved change.
Have two lab administrators open the same ADOM, let one acquire the permitted lock and change a dummy object, and confirm the second cannot commit a conflicting edit until release. That would help test “Enable FortiManager workspace mode for concurrent policy editing”, not the outcome required in this scenario. The relevant acceptance check is: Produce two lab ADOM revisions with separate service-object and rule-order edits, compare them and validate one selected rollback while keeping the unrelated approved change.
Produce two lab ADOM revisions with separate service-object and rule-order edits, compare them and validate one selected rollback while keeping the unrelated approved change. This check is decisive because comparing central snapshots distinguishes authorized changes from accidental object drift; blindly restoring an older snapshot may erase independent legitimate edits made later in the same ADOM.
Question 444
A bank discovers a shared address object was modified during maintenance but another team's emergency policy fix also occurred afterward. Which proposed shortcut most directly risks unnecessary interruption after a broad central rollback erases valid later policy changes and should therefore be rejected?
Answer & Explanations
Correct answer: A
Restore the first-ever ADOM revision whenever one object is wrong, without inspecting what valid subsequent business rules and device assignments will be removed. The foreseeable failure is unnecessary interruption after a broad central rollback erases valid later policy changes. The safer response is: Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified.
Allow two administrators to simultaneously change the same production policy package with workspace disabled and assume last-writer conflict cannot occur because their logins are different. That shortcut risks lost or overwritten firewall policy edits when concurrent administrators lack controlled workspace locking. Here the specific shortcut is: Restore the first-ever ADOM revision whenever one object is wrong, without inspecting what valid subsequent business rules and device assignments will be removed.
Restore a previous ADOM revision and report every gateway instantly rolled back even though no installation tasks or device policy checks were performed. That shortcut risks incorrect change records after management database restoration is confused with actual firewall enforcement rollback. Here the specific shortcut is: Restore the first-ever ADOM revision whenever one object is wrong, without inspecting what valid subsequent business rules and device assignments will be removed.
Before restructuring a customer ADOM delete its policy packages and count on a single branch FortiGate revision history to recreate every central object automatically. That shortcut risks permanent loss of shared policy context after an ADOM-wide change without an appropriate central revision. Here the specific shortcut is: Restore the first-ever ADOM revision whenever one object is wrong, without inspecting what valid subsequent business rules and device assignments will be removed.
Question 445
A bank discovers a shared address object was modified during maintenance but another team's emergency policy fix also occurred afterward. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: A
Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified. Confirm it through this test: Produce two lab ADOM revisions with separate service-object and rule-order edits, compare them and validate one selected rollback while keeping the unrelated approved change. Comparing central snapshots distinguishes authorized changes from accidental object drift; blindly restoring an older snapshot may erase independent legitimate edits made later in the same ADOM.
This action/test pair addresses “Reconcile ADOM revision recovery with package installation state on managed FortiGates”. After restoring or choosing an approved FortiManager ADOM revision, preview and explicitly install the corresponding policy package to affected target devices and verify their actual enforced revision. Restore a test ADOM revision, confirm the central package version changed, inspect a staged FortiGate's still-running old policy, then install and verify the approved restored package. The case instead calls for: Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified.
The action is applicable: Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified. But its proposed test—Save an ADOM revision, alter a harmless shared object and package order in a lab, inspect the differences and restore only an approved central baseline without affecting unrelated device-only settings.—addresses “Capture a FortiManager ADOM revision before a shared policy reorganization”. This requirement is confirmed instead by: Produce two lab ADOM revisions with separate service-object and rule-order edits, compare them and validate one selected rollback while keeping the unrelated approved change.
The test would be relevant: Produce two lab ADOM revisions with separate service-object and rule-order edits, compare them and validate one selected rollback while keeping the unrelated approved change. But the offered implementation—Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path.—addresses “Capture a FortiManager ADOM revision before a shared policy reorganization”. The action needed here is: Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified.
Question 446
A university is reviewing FortiManager's central revision history to determine which change caused an installation warning across a shared gateway package. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: B
Use FortiManager's policy installation preview and validation to inspect intended commands, target devices and object/interface resolution, then obtain approval before deploying a package. This addresses “Preview a FortiManager Install Wizard plan before changing a FortiGate”, where the governing principle is: The central package editor expresses desired state; the Install Wizard translates it into target-specific configuration and may reveal missing mappings or unexpected changes that are not visible from the package name. The stated case instead calls for: Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified.
The question is set in this situation: A university is reviewing FortiManager's central revision history to determine which change caused an installation warning across a shared gateway package. Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified. Comparing central snapshots distinguishes authorized changes from accidental object drift; blindly restoring an older snapshot may erase independent legitimate edits made later in the same ADOM. Verify the result with this test: Produce two lab ADOM revisions with separate service-object and rule-order edits, compare them and validate one selected rollback while keeping the unrelated approved change.
The question is set in this situation: A university is reviewing FortiManager's central revision history to determine which change caused an installation warning across a shared gateway package. After restoring or choosing an approved FortiManager ADOM revision, preview and explicitly install the corresponding policy package to affected target devices and verify their actual enforced revision. This addresses “Reconcile ADOM revision recovery with package installation state on managed FortiGates”, where the governing principle is: An ADOM revision changes central database content; existing FortiGates do not automatically roll back running policies merely because an older management snapshot was selected. The stated case instead calls for: Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified.
The question is set in this situation: A university is reviewing FortiManager's central revision history to determine which change caused an installation warning across a shared gateway package. Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path. This addresses “Capture a FortiManager ADOM revision before a shared policy reorganization”, where the governing principle is: An ADOM revision records central policy/object state at a point in time; a device configuration revision for one FortiGate cannot replace the broader ADOM snapshot used to recover shared packages. The stated case instead calls for: Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified.
Question 447
A university is reviewing FortiManager's central revision history to determine which change caused an installation warning across a shared gateway package. The engineer proposes the following change: Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified. Which mechanism explains why it works?
Answer & Explanations
Correct answer: C
The question is set in this situation: A university is reviewing FortiManager's central revision history to determine which change caused an installation warning across a shared gateway package. An ADOM revision records central policy/object state at a point in time; a device configuration revision for one FortiGate cannot replace the broader ADOM snapshot used to recover shared packages. That explains “Capture a FortiManager ADOM revision before a shared policy reorganization”, not the mechanism behind the described change. The relevant principle is: Comparing central snapshots distinguishes authorized changes from accidental object drift; blindly restoring an older snapshot may erase independent legitimate edits made later in the same ADOM.
The question is set in this situation: A university is reviewing FortiManager's central revision history to determine which change caused an installation warning across a shared gateway package. An ADOM revision changes central database content; existing FortiGates do not automatically roll back running policies merely because an older management snapshot was selected. That explains “Reconcile ADOM revision recovery with package installation state on managed FortiGates”, not the mechanism behind the described change. The relevant principle is: Comparing central snapshots distinguishes authorized changes from accidental object drift; blindly restoring an older snapshot may erase independent legitimate edits made later in the same ADOM.
The question is set in this situation: A university is reviewing FortiManager's central revision history to determine which change caused an installation warning across a shared gateway package. Comparing central snapshots distinguishes authorized changes from accidental object drift; blindly restoring an older snapshot may erase independent legitimate edits made later in the same ADOM. The corresponding implementation is: Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified.
The central package editor expresses desired state; the Install Wizard translates it into target-specific configuration and may reveal missing mappings or unexpected changes that are not visible from the package name. That explains “Preview a FortiManager Install Wizard plan before changing a FortiGate”, not the mechanism behind the described change. The relevant principle is: Comparing central snapshots distinguishes authorized changes from accidental object drift; blindly restoring an older snapshot may erase independent legitimate edits made later in the same ADOM.
Question 448
A university is reviewing FortiManager's central revision history to determine which change caused an installation warning across a shared gateway package. After implementing this change—Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: D
The question is set in this situation: A university is reviewing FortiManager's central revision history to determine which change caused an installation warning across a shared gateway package. Save an ADOM revision, alter a harmless shared object and package order in a lab, inspect the differences and restore only an approved central baseline without affecting unrelated device-only settings. That would help test “Capture a FortiManager ADOM revision before a shared policy reorganization”, not the outcome required in this scenario. The relevant acceptance check is: Produce two lab ADOM revisions with separate service-object and rule-order edits, compare them and validate one selected rollback while keeping the unrelated approved change.
The question is set in this situation: A university is reviewing FortiManager's central revision history to determine which change caused an installation warning across a shared gateway package. Restore a test ADOM revision, confirm the central package version changed, inspect a staged FortiGate's still-running old policy, then install and verify the approved restored package. That would help test “Reconcile ADOM revision recovery with package installation state on managed FortiGates”, not the outcome required in this scenario. The relevant acceptance check is: Produce two lab ADOM revisions with separate service-object and rule-order edits, compare them and validate one selected rollback while keeping the unrelated approved change.
Preview a staging package with a dynamic object for two FortiGate targets, compare each generated change, install to one test device and confirm its actual policy counters. That would help test “Preview a FortiManager Install Wizard plan before changing a FortiGate”, not the outcome required in this scenario. The relevant acceptance check is: Produce two lab ADOM revisions with separate service-object and rule-order edits, compare them and validate one selected rollback while keeping the unrelated approved change.
The question is set in this situation: A university is reviewing FortiManager's central revision history to determine which change caused an installation warning across a shared gateway package. Produce two lab ADOM revisions with separate service-object and rule-order edits, compare them and validate one selected rollback while keeping the unrelated approved change. This check is decisive because comparing central snapshots distinguishes authorized changes from accidental object drift; blindly restoring an older snapshot may erase independent legitimate edits made later in the same ADOM.
Question 449
A university is reviewing FortiManager's central revision history to determine which change caused an installation warning across a shared gateway package. Which proposed shortcut most directly risks unnecessary interruption after a broad central rollback erases valid later policy changes and should therefore be rejected?
Answer & Explanations
Correct answer: A
The question is set in this situation: A university is reviewing FortiManager's central revision history to determine which change caused an installation warning across a shared gateway package. Restore the first-ever ADOM revision whenever one object is wrong, without inspecting what valid subsequent business rules and device assignments will be removed. The foreseeable failure is unnecessary interruption after a broad central rollback erases valid later policy changes. The safer response is: Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified.
The question is set in this situation: A university is reviewing FortiManager's central revision history to determine which change caused an installation warning across a shared gateway package. Restore a previous ADOM revision and report every gateway instantly rolled back even though no installation tasks or device policy checks were performed. That shortcut risks incorrect change records after management database restoration is confused with actual firewall enforcement rollback. Here the specific shortcut is: Restore the first-ever ADOM revision whenever one object is wrong, without inspecting what valid subsequent business rules and device assignments will be removed.
The question is set in this situation: A university is reviewing FortiManager's central revision history to determine which change caused an installation warning across a shared gateway package. Before restructuring a customer ADOM delete its policy packages and count on a single branch FortiGate revision history to recreate every central object automatically. That shortcut risks permanent loss of shared policy context after an ADOM-wide change without an appropriate central revision. Here the specific shortcut is: Restore the first-ever ADOM revision whenever one object is wrong, without inspecting what valid subsequent business rules and device assignments will be removed.
Click Install All as soon as an ADOM package saves and assume the wizard cannot generate any unexpected per-device configuration changes. That shortcut risks network exposure or traffic disruption after deploying unchecked generated policy differences. Here the specific shortcut is: Restore the first-ever ADOM revision whenever one object is wrong, without inspecting what valid subsequent business rules and device assignments will be removed.
Question 450
A university is reviewing FortiManager's central revision history to determine which change caused an installation warning across a shared gateway package. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: C
The action is applicable: Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified. But its proposed test—Restore a test ADOM revision, confirm the central package version changed, inspect a staged FortiGate's still-running old policy, then install and verify the approved restored package.—addresses “Reconcile ADOM revision recovery with package installation state on managed FortiGates”. This requirement is confirmed instead by: Produce two lab ADOM revisions with separate service-object and rule-order edits, compare them and validate one selected rollback while keeping the unrelated approved change.
The test would be relevant: Produce two lab ADOM revisions with separate service-object and rule-order edits, compare them and validate one selected rollback while keeping the unrelated approved change. But the offered implementation—After restoring or choosing an approved FortiManager ADOM revision, preview and explicitly install the corresponding policy package to affected target devices and verify their actual enforced revision.—addresses “Reconcile ADOM revision recovery with package installation state on managed FortiGates”. The action needed here is: Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified.
The question is set in this situation: A university is reviewing FortiManager's central revision history to determine which change caused an installation warning across a shared gateway package. Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified. Confirm it through this test: Produce two lab ADOM revisions with separate service-object and rule-order edits, compare them and validate one selected rollback while keeping the unrelated approved change. Comparing central snapshots distinguishes authorized changes from accidental object drift; blindly restoring an older snapshot may erase independent legitimate edits made later in the same ADOM.
This action/test pair addresses “Capture a FortiManager ADOM revision before a shared policy reorganization”. Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path. Save an ADOM revision, alter a harmless shared object and package order in a lab, inspect the differences and restore only an approved central baseline without affecting unrelated device-only settings. The case instead calls for: Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- Fortinet FCP_FMG_AD-7.6 Practice Test 43 - 10 Questions (Last Reviewed 09-Oct-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 44 - 10 Questions (Last Reviewed 08-Oct-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 45 - 10 Questions (Last Reviewed 07-Oct-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 46 - 10 Questions (Last Reviewed 06-Oct-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 47 - 10 Questions (Last Reviewed 05-Oct-2026)