Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 46
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.
Question 451
A regional insurer wants to reverse a shared access rule change across several branch gateways and must show they received the corrected installed policy. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: D
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. This addresses “Compare two FortiManager ADOM revisions to isolate a shared object change”, where the governing 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 stated case instead calls for: 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.
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: 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.
Define a suitable dynamic mapping for a centrally shared policy object and configure distinct authorized values per target FortiGate without copying private branch subnets into one universal static object. This addresses “Use FortiManager dynamic objects for per-device address differences”, where the governing principle is: Dynamic objects let a common logical name resolve to different device-specific values at installation; leaving a mapping undefined or treating it as globally identical can send traffic to the wrong destination. The stated case instead calls for: 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.
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. An ADOM revision changes central database content; existing FortiGates do not automatically roll back running policies merely because an older management snapshot was selected. Verify the result with this 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.
Question 452
A regional insurer wants to reverse a shared access rule change across several branch gateways and must show they received the corrected installed policy. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: B
Dynamic objects let a common logical name resolve to different device-specific values at installation; leaving a mapping undefined or treating it as globally identical can send traffic to the wrong destination. That explains “Use FortiManager dynamic objects for per-device address differences”, not the mechanism behind the described change. The relevant 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.
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 corresponding implementation is: 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.
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. That explains “Compare two FortiManager ADOM revisions to isolate a shared object change”, not the mechanism behind the described change. The relevant 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.
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: An ADOM revision changes central database content; existing FortiGates do not automatically roll back running policies merely because an older management snapshot was selected.
Question 453
A regional insurer wants to reverse a shared access rule change across several branch gateways and must show they received the corrected installed policy. After implementing this change—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.—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: 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.
Map a logical internal-network object to two different lab branch subnets, preview the installed package for each FortiGate and verify the generated addresses match the site. That would help test “Use FortiManager dynamic objects for per-device address differences”, not the outcome required in this scenario. The relevant acceptance check is: 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.
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. That would help test “Compare two FortiManager ADOM revisions to isolate a shared object change”, not the outcome required in this scenario. The relevant acceptance check is: 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.
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. This check is decisive because an ADOM revision changes central database content; existing FortiGates do not automatically roll back running policies merely because an older management snapshot was selected.
Question 454
A regional insurer wants to reverse a shared access rule change across several branch gateways and must show they received the corrected installed policy. Which proposed shortcut most directly risks incorrect change records after management database restoration is confused with actual firewall enforcement rollback and should therefore be rejected?
Answer & Explanations
Correct answer: A
Restore a previous ADOM revision and report every gateway instantly rolled back even though no installation tasks or device policy checks were performed. The foreseeable failure is incorrect change records after management database restoration is confused with actual firewall enforcement rollback. The safer response is: 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.
Set every branch object's address to the first store's network and assume FortiManager automatically discovers the correct site-specific values from an identical object name. That shortcut risks cross-site routing errors or unintended access after failing to map a shared dynamic object for each target device. Here the specific shortcut is: Restore a previous ADOM revision and report every gateway instantly rolled back even though no installation tasks or device policy checks were performed.
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 a previous ADOM revision and report every gateway instantly rolled back even though no installation tasks or device policy checks were performed.
Restore the first-ever ADOM revision whenever one object is wrong, without inspecting what valid subsequent business rules and device assignments will be removed. That shortcut risks unnecessary interruption after a broad central rollback erases valid later policy changes. Here the specific shortcut is: Restore a previous ADOM revision and report every gateway instantly rolled back even though no installation tasks or device policy checks were performed.
Question 455
A regional insurer wants to reverse a shared access rule change across several branch gateways and must show they received the corrected installed policy. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: C
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: 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.
The test would be relevant: 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. 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: 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.
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. Confirm it through this 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. 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 action is applicable: 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. 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: 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.
Question 456
An MSP's auditor asks why a FortiManager ADOM revision was restored but one disconnected branch FortiGate still enforces a newer package. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: B
The question is set in this situation: An MSP's auditor asks why a FortiManager ADOM revision was restored but one disconnected branch FortiGate still enforces a newer 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. This addresses “Compare two FortiManager ADOM revisions to isolate a shared object change”, where the governing 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 stated case instead calls for: 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.
The question is set in this situation: An MSP's auditor asks why a FortiManager ADOM revision was restored but one disconnected branch FortiGate still enforces a newer 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. An ADOM revision changes central database content; existing FortiGates do not automatically roll back running policies merely because an older management snapshot was selected. Verify the result with this 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.
Use FortiManager policy checks and relevant object validations to inspect shadowed, inconsistent or invalid rules and referenced interfaces, then resolve significant issues before installing to production targets. This addresses “Run FortiManager policy check before approving a package installation”, where the governing principle is: A syntactically saved rule may never match because a broader earlier rule captures traffic; checking effective policy logic prevents false assumptions that a newly written rule changes enforcement. The stated case instead calls for: 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.
The question is set in this situation: An MSP's auditor asks why a FortiManager ADOM revision was restored but one disconnected branch FortiGate still enforces a newer 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: 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.
Question 457
An MSP's auditor asks why a FortiManager ADOM revision was restored but one disconnected branch FortiGate still enforces a newer package. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: D
The question is set in this situation: An MSP's auditor asks why a FortiManager ADOM revision was restored but one disconnected branch FortiGate still enforces a newer 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. That explains “Compare two FortiManager ADOM revisions to isolate a shared object change”, not the mechanism behind the described change. The relevant 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.
A syntactically saved rule may never match because a broader earlier rule captures traffic; checking effective policy logic prevents false assumptions that a newly written rule changes enforcement. That explains “Run FortiManager policy check before approving a package installation”, not the mechanism behind the described change. The relevant 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 question is set in this situation: An MSP's auditor asks why a FortiManager ADOM revision was restored but one disconnected branch FortiGate still enforces a newer 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: 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 question is set in this situation: An MSP's auditor asks why a FortiManager ADOM revision was restored but one disconnected branch FortiGate still enforces a newer 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. The corresponding implementation is: 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.
Question 458
An MSP's auditor asks why a FortiManager ADOM revision was restored but one disconnected branch FortiGate still enforces a newer package. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: A
The question is set in this situation: An MSP's auditor asks why a FortiManager ADOM revision was restored but one disconnected branch FortiGate still enforces a newer 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. This check is decisive because 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 question is set in this situation: An MSP's auditor asks why a FortiManager ADOM revision was restored but one disconnected branch FortiGate still enforces a newer 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. That would help test “Compare two FortiManager ADOM revisions to isolate a shared object change”, not the outcome required in this scenario. The relevant acceptance check is: 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 question is set in this situation: An MSP's auditor asks why a FortiManager ADOM revision was restored but one disconnected branch FortiGate still enforces a newer 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: 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.
Add a narrowly scoped deny beneath a broad allow in a lab package, use the available policy analysis and simulated traffic to reveal the shadowed behavior, then revise approved rule order. That would help test “Run FortiManager policy check before approving a package installation”, not the outcome required in this scenario. The relevant acceptance check is: 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.
Question 459
An MSP's auditor asks why a FortiManager ADOM revision was restored but one disconnected branch FortiGate still enforces a newer package. Which proposed shortcut most directly risks incorrect change records after management database restoration is confused with actual firewall enforcement rollback and should therefore be rejected?
Answer & Explanations
Correct answer: C
The question is set in this situation: An MSP's auditor asks why a FortiManager ADOM revision was restored but one disconnected branch FortiGate still enforces a newer 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 a previous ADOM revision and report every gateway instantly rolled back even though no installation tasks or device policy checks were performed.
The question is set in this situation: An MSP's auditor asks why a FortiManager ADOM revision was restored but one disconnected branch FortiGate still enforces a newer 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. That shortcut risks unnecessary interruption after a broad central rollback erases valid later policy changes. Here the specific shortcut is: Restore a previous ADOM revision and report every gateway instantly rolled back even though no installation tasks or device policy checks were performed.
The question is set in this situation: An MSP's auditor asks why a FortiManager ADOM revision was restored but one disconnected branch FortiGate still enforces a newer package. Restore a previous ADOM revision and report every gateway instantly rolled back even though no installation tasks or device policy checks were performed. The foreseeable failure is incorrect change records after management database restoration is confused with actual firewall enforcement rollback. The safer response is: 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.
Save a new deny rule at the end of a policy list and assume it always overrides an earlier matching allow because its description says High Priority. That shortcut risks unintended permitted access after an ineffective shadowed security rule is installed without verification. Here the specific shortcut is: Restore a previous ADOM revision and report every gateway instantly rolled back even though no installation tasks or device policy checks were performed.
Question 460
An MSP's auditor asks why a FortiManager ADOM revision was restored but one disconnected branch FortiGate still enforces a newer package. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: B
The test would be relevant: 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. 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: 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.
The question is set in this situation: An MSP's auditor asks why a FortiManager ADOM revision was restored but one disconnected branch FortiGate still enforces a newer 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. Confirm it through this 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. An ADOM revision changes central database content; existing FortiGates do not automatically roll back running policies merely because an older management snapshot was selected.
This action/test pair addresses “Compare two FortiManager ADOM revisions to isolate a shared object 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. 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 case instead calls for: 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.
The action is applicable: 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. 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: 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.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- 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)
- Fortinet FCP_FMG_AD-7.6 Practice Test 48 - 10 Questions (Last Reviewed 04-Oct-2026)