Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 51
Question 500
A bank needs to free a package lock during incident response without deleting an engineer's partially reviewed emergency policy 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: A bank needs to free a package lock during incident response without deleting an engineer's partially reviewed emergency policy changes. Inspect FortiManager session and lock ownership before closing a stale session or releasing an ADOM lock, document the intended change status and preserve or intentionally discard uncommitted work through the supported procedure. Confirm it through this test: Create a harmless locked session, simulate an administrator disconnect, identify the lock and draft state, and use the authorized recovery procedure while verifying the committed policy remains correct. A stuck workspace lock may block progress, but force-releasing it without examining pending edits can either lose an authorized change or expose concurrent edits to conflict.
The question is set in this situation: A bank needs to free a package lock during incident response without deleting an engineer's partially reviewed emergency policy changes. This action/test pair addresses “Use FortiManager workflow mode review and approval controls where required”. Configure the supported workflow or session approval process in the chosen FortiManager workspace mode so a submitted production policy change receives designated reviewer approval before being installed. Create a test session containing a harmless object edit, submit it for authorized review, verify a rejected session cannot proceed and an approved one preserves its audit trail. The case instead calls for: Inspect FortiManager session and lock ownership before closing a stale session or releasing an ADOM lock, document the intended change status and preserve or intentionally discard uncommitted work through the supported procedure.
The question is set in this situation: A bank needs to free a package lock during incident response without deleting an engineer's partially reviewed emergency policy changes. The action is applicable: Inspect FortiManager session and lock ownership before closing a stale session or releasing an ADOM lock, document the intended change status and preserve or intentionally discard uncommitted work through the supported procedure. But its proposed test—Open two lab packages under one ADOM, lock only the intended scope, verify a competing edit is denied where needed and unrelated approved work remains possible when supported.—addresses “Choose ADOM or policy package lock scope appropriate to the change”. This requirement is confirmed instead by: Create a harmless locked session, simulate an administrator disconnect, identify the lock and draft state, and use the authorized recovery procedure while verifying the committed policy remains correct.
The question is set in this situation: A bank needs to free a package lock during incident response without deleting an engineer's partially reviewed emergency policy changes. The test would be relevant: Create a harmless locked session, simulate an administrator disconnect, identify the lock and draft state, and use the authorized recovery procedure while verifying the committed policy remains correct. But the offered implementation—Acquire the supported ADOM, policy package or per-policy lock scope required by the FortiManager workspace mode and document the intended change boundary to limit unnecessary blocking of unrelated administrators.—addresses “Choose ADOM or policy package lock scope appropriate to the change”. The action needed here is: Inspect FortiManager session and lock ownership before closing a stale session or releasing an ADOM lock, document the intended change status and preserve or intentionally discard uncommitted work through the supported procedure.
Question 501
A university is centralizing management of legacy lab FortiGates whose local policies have never been imported into FortiManager. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: A
Run FortiManager's supported policy import wizard for the selected managed device, reconcile interface mappings and address/service objects, review import warnings and create a package for explicit later approval and installation. A policy import captures device-side rules into central database scope; it is distinct from copying configuration to the gateway, and unresolved references can cause problems during later installs. Verify the result with this test: Import a staging FortiGate containing one custom address and service, compare its running rules to the new package, fix a deliberate interface mapping warning and document that no install occurred merely from import.
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: Run FortiManager's supported policy import wizard for the selected managed device, reconcile interface mappings and address/service objects, review import warnings and create a package for explicit later approval and installation.
When an Install Wizard detects unresolved objects, interface mappings or package syntax, inspect the specific validation message, correct the originating FortiManager database record and rerun validation before any installation. This addresses “Handle a FortiManager installation validation error before pushing policy”, where the governing principle is: A validation error means the generated target configuration may be incomplete; bypassing it or expanding a rule does not repair the underlying object mapping or unsupported feature. The stated case instead calls for: Run FortiManager's supported policy import wizard for the selected managed device, reconcile interface mappings and address/service objects, review import warnings and create a package for explicit later approval and installation.
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: Run FortiManager's supported policy import wizard for the selected managed device, reconcile interface mappings and address/service objects, review import warnings and create a package for explicit later approval and installation.
Question 502
A university is centralizing management of legacy lab FortiGates whose local policies have never been imported into FortiManager. The engineer proposes the following change: Run FortiManager's supported policy import wizard for the selected managed device, reconcile interface mappings and address/service objects, review import warnings and create a package for explicit later approval and installation. Which mechanism explains why it works?
Answer & Explanations
Correct answer: C
A validation error means the generated target configuration may be incomplete; bypassing it or expanding a rule does not repair the underlying object mapping or unsupported feature. That explains “Handle a FortiManager installation validation error before pushing policy”, not the mechanism behind the described change. The relevant principle is: A policy import captures device-side rules into central database scope; it is distinct from copying configuration to the gateway, and unresolved references can cause problems during later installs.
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: A policy import captures device-side rules into central database scope; it is distinct from copying configuration to the gateway, and unresolved references can cause problems during later installs.
A policy import captures device-side rules into central database scope; it is distinct from copying configuration to the gateway, and unresolved references can cause problems during later installs. The corresponding implementation is: Run FortiManager's supported policy import wizard for the selected managed device, reconcile interface mappings and address/service objects, review import warnings and create a package for explicit later approval and installation.
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: A policy import captures device-side rules into central database scope; it is distinct from copying configuration to the gateway, and unresolved references can cause problems during later installs.
Question 503
A university is centralizing management of legacy lab FortiGates whose local policies have never been imported into FortiManager. After implementing this change—Run FortiManager's supported policy import wizard for the selected managed device, reconcile interface mappings and address/service objects, review import warnings and create a package for explicit later approval and installation.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: D
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: Import a staging FortiGate containing one custom address and service, compare its running rules to the new package, fix a deliberate interface mapping warning and document that no install occurred merely from import.
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: Import a staging FortiGate containing one custom address and service, compare its running rules to the new package, fix a deliberate interface mapping warning and document that no install occurred merely from import.
Create an intentionally missing interface mapping in a disposable package, inspect the exact validation failure, repair the mapping and demonstrate a clean preview and safe test install. That would help test “Handle a FortiManager installation validation error before pushing policy”, not the outcome required in this scenario. The relevant acceptance check is: Import a staging FortiGate containing one custom address and service, compare its running rules to the new package, fix a deliberate interface mapping warning and document that no install occurred merely from import.
Import a staging FortiGate containing one custom address and service, compare its running rules to the new package, fix a deliberate interface mapping warning and document that no install occurred merely from import. This check is decisive because a policy import captures device-side rules into central database scope; it is distinct from copying configuration to the gateway, and unresolved references can cause problems during later installs.
Question 504
A university is centralizing management of legacy lab FortiGates whose local policies have never been imported into FortiManager. Which proposed shortcut most directly risks loss of valid access rules after an incomplete first import is treated as ready for installation and should therefore be rejected?
Answer & Explanations
Correct answer: B
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: Accept every failed mapping in an import report and then install the incomplete package over production before comparing it with the existing gateway policy.
Accept every failed mapping in an import report and then install the incomplete package over production before comparing it with the existing gateway policy. The foreseeable failure is loss of valid access rules after an incomplete first import is treated as ready for installation. The safer response is: Run FortiManager's supported policy import wizard for the selected managed device, reconcile interface mappings and address/service objects, review import warnings and create a package for explicit later approval and installation.
Ignore an install validation error for an unmapped interface and add a broad permit rule to production hoping the firewall will resolve the missing port automatically. That shortcut risks failed installation or unsafe workaround after treating object-mapping validation as a harmless notification. Here the specific shortcut is: Accept every failed mapping in an import report and then install the incomplete package over production before comparing it with the existing gateway policy.
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: Accept every failed mapping in an import report and then install the incomplete package over production before comparing it with the existing gateway policy.
Question 505
A university is centralizing management of legacy lab FortiGates whose local policies have never been imported into FortiManager. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: D
The action is applicable: Run FortiManager's supported policy import wizard for the selected managed device, reconcile interface mappings and address/service objects, review import warnings and create a package for explicit later approval and installation. But its proposed test—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.—addresses “Preview a FortiManager Install Wizard plan before changing a FortiGate”. This requirement is confirmed instead by: Import a staging FortiGate containing one custom address and service, compare its running rules to the new package, fix a deliberate interface mapping warning and document that no install occurred merely from import.
The test would be relevant: Import a staging FortiGate containing one custom address and service, compare its running rules to the new package, fix a deliberate interface mapping warning and document that no install occurred merely from import. But the offered implementation—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.—addresses “Preview a FortiManager Install Wizard plan before changing a FortiGate”. The action needed here is: Run FortiManager's supported policy import wizard for the selected managed device, reconcile interface mappings and address/service objects, review import warnings and create a package for explicit later approval and installation.
This action/test pair addresses “Handle a FortiManager installation validation error before pushing policy”. When an Install Wizard detects unresolved objects, interface mappings or package syntax, inspect the specific validation message, correct the originating FortiManager database record and rerun validation before any installation. Create an intentionally missing interface mapping in a disposable package, inspect the exact validation failure, repair the mapping and demonstrate a clean preview and safe test install. The case instead calls for: Run FortiManager's supported policy import wizard for the selected managed device, reconcile interface mappings and address/service objects, review import warnings and create a package for explicit later approval and installation.
Run FortiManager's supported policy import wizard for the selected managed device, reconcile interface mappings and address/service objects, review import warnings and create a package for explicit later approval and installation. Confirm it through this test: Import a staging FortiGate containing one custom address and service, compare its running rules to the new package, fix a deliberate interface mapping warning and document that no install occurred merely from import. A policy import captures device-side rules into central database scope; it is distinct from copying configuration to the gateway, and unresolved references can cause problems during later installs.
Question 506
A retailer acquires branches with existing custom firewall rules and needs a safe policy onboarding process before standardizing packages. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: C
Inspect FortiManager's package status, installation logs and managed FortiGate revision to confirm the intended policy actually reached the correct target, and investigate any out-of-sync status before closing the change ticket. This addresses “Confirm FortiManager package status after a successful installation”, where the governing principle is: A successful central submission is not proof every gateway accepted and enforced the generated policy; per-device execution and database synchronization states provide necessary evidence. The stated case instead calls for: Run FortiManager's supported policy import wizard for the selected managed device, reconcile interface mappings and address/service objects, review import warnings and create a package for explicit later approval and installation.
Compare FortiManager's intended package and device database with recent approved local FortiGate changes, retrieve or reconcile legitimate differences, and preview the installation impact before pushing central configuration. This addresses “Avoid accidental overwrite of local FortiGate changes during central policy installation”, where the governing principle is: A FortiManager install can replace selected device-side settings with centrally managed intended state; ignoring authorized emergency local edits can make a later normal installation undo critical recovery changes. The stated case instead calls for: Run FortiManager's supported policy import wizard for the selected managed device, reconcile interface mappings and address/service objects, review import warnings and create a package for explicit later approval and installation.
The question is set in this situation: A retailer acquires branches with existing custom firewall rules and needs a safe policy onboarding process before standardizing packages. Run FortiManager's supported policy import wizard for the selected managed device, reconcile interface mappings and address/service objects, review import warnings and create a package for explicit later approval and installation. A policy import captures device-side rules into central database scope; it is distinct from copying configuration to the gateway, and unresolved references can cause problems during later installs. Verify the result with this test: Import a staging FortiGate containing one custom address and service, compare its running rules to the new package, fix a deliberate interface mapping warning and document that no install occurred merely from import.
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: Run FortiManager's supported policy import wizard for the selected managed device, reconcile interface mappings and address/service objects, review import warnings and create a package for explicit later approval and installation.
Question 507
A retailer acquires branches with existing custom firewall rules and needs a safe policy onboarding process before standardizing packages. The engineer proposes the following change: Run FortiManager's supported policy import wizard for the selected managed device, reconcile interface mappings and address/service objects, review import warnings and create a package for explicit later approval and installation. Which mechanism explains why it works?
Answer & Explanations
Correct answer: B
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: A policy import captures device-side rules into central database scope; it is distinct from copying configuration to the gateway, and unresolved references can cause problems during later installs.
The question is set in this situation: A retailer acquires branches with existing custom firewall rules and needs a safe policy onboarding process before standardizing packages. A policy import captures device-side rules into central database scope; it is distinct from copying configuration to the gateway, and unresolved references can cause problems during later installs. The corresponding implementation is: Run FortiManager's supported policy import wizard for the selected managed device, reconcile interface mappings and address/service objects, review import warnings and create a package for explicit later approval and installation.
A successful central submission is not proof every gateway accepted and enforced the generated policy; per-device execution and database synchronization states provide necessary evidence. That explains “Confirm FortiManager package status after a successful installation”, not the mechanism behind the described change. The relevant principle is: A policy import captures device-side rules into central database scope; it is distinct from copying configuration to the gateway, and unresolved references can cause problems during later installs.
A FortiManager install can replace selected device-side settings with centrally managed intended state; ignoring authorized emergency local edits can make a later normal installation undo critical recovery changes. That explains “Avoid accidental overwrite of local FortiGate changes during central policy installation”, not the mechanism behind the described change. The relevant principle is: A policy import captures device-side rules into central database scope; it is distinct from copying configuration to the gateway, and unresolved references can cause problems during later installs.
Question 508
A retailer acquires branches with existing custom firewall rules and needs a safe policy onboarding process before standardizing packages. After implementing this change—Run FortiManager's supported policy import wizard for the selected managed device, reconcile interface mappings and address/service objects, review import warnings and create a package for explicit later approval and installation.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: A
The question is set in this situation: A retailer acquires branches with existing custom firewall rules and needs a safe policy onboarding process before standardizing packages. Import a staging FortiGate containing one custom address and service, compare its running rules to the new package, fix a deliberate interface mapping warning and document that no install occurred merely from import. This check is decisive because a policy import captures device-side rules into central database scope; it is distinct from copying configuration to the gateway, and unresolved references can cause problems during later installs.
Add a harmless approved local rule in a staging firewall, compare central package and device revisions, import or translate it to managed policy, then install and confirm the exception is preserved. That would help test “Avoid accidental overwrite of local FortiGate changes during central policy installation”, not the outcome required in this scenario. The relevant acceptance check is: Import a staging FortiGate containing one custom address and service, compare its running rules to the new package, fix a deliberate interface mapping warning and document that no install occurred merely from import.
Install a harmless lab policy to two gateways, disconnect one during the task, verify only one successful result and reconcile the failed target after connectivity returns. That would help test “Confirm FortiManager package status after a successful installation”, not the outcome required in this scenario. The relevant acceptance check is: Import a staging FortiGate containing one custom address and service, compare its running rules to the new package, fix a deliberate interface mapping warning and document that no install occurred merely from import.
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: Import a staging FortiGate containing one custom address and service, compare its running rules to the new package, fix a deliberate interface mapping warning and document that no install occurred merely from import.
Question 509
A retailer acquires branches with existing custom firewall rules and needs a safe policy onboarding process before standardizing packages. Which proposed shortcut most directly risks loss of valid access rules after an incomplete first import is treated as ready for installation and should therefore be rejected?
Answer & Explanations
Correct answer: A
The question is set in this situation: A retailer acquires branches with existing custom firewall rules and needs a safe policy onboarding process before standardizing packages. Accept every failed mapping in an import report and then install the incomplete package over production before comparing it with the existing gateway policy. The foreseeable failure is loss of valid access rules after an incomplete first import is treated as ready for installation. The safer response is: Run FortiManager's supported policy import wizard for the selected managed device, reconcile interface mappings and address/service objects, review import warnings and create a package for explicit later approval and installation.
Run an unchanged old policy package after a branch emergency change and assume FortiManager always merges every local edit without review or possible overwrite. That shortcut risks unexpected site outage when central management overwrites an authorized local change that was never reconciled. Here the specific shortcut is: Accept every failed mapping in an import report and then install the incomplete package over production before comparing it with the existing gateway policy.
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: Accept every failed mapping in an import report and then install the incomplete package over production before comparing it with the existing gateway policy.
Close a change ticket after the Install Wizard task is queued and report all customer gateways compliant without checking per-device success and installed revision. That shortcut risks false audit evidence and inconsistent network filtering after installation task state is mistaken for device enforcement. Here the specific shortcut is: Accept every failed mapping in an import report and then install the incomplete package over production before comparing it with the existing gateway policy.
Question 510
A retailer acquires branches with existing custom firewall rules and needs a safe policy onboarding process before standardizing packages. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: D
This action/test pair addresses “Avoid accidental overwrite of local FortiGate changes during central policy installation”. Compare FortiManager's intended package and device database with recent approved local FortiGate changes, retrieve or reconcile legitimate differences, and preview the installation impact before pushing central configuration. Add a harmless approved local rule in a staging firewall, compare central package and device revisions, import or translate it to managed policy, then install and confirm the exception is preserved. The case instead calls for: Run FortiManager's supported policy import wizard for the selected managed device, reconcile interface mappings and address/service objects, review import warnings and create a package for explicit later approval and installation.
The action is applicable: Run FortiManager's supported policy import wizard for the selected managed device, reconcile interface mappings and address/service objects, review import warnings and create a package for explicit later approval and installation. But its proposed test—Install a harmless lab policy to two gateways, disconnect one during the task, verify only one successful result and reconcile the failed target after connectivity returns.—addresses “Confirm FortiManager package status after a successful installation”. This requirement is confirmed instead by: Import a staging FortiGate containing one custom address and service, compare its running rules to the new package, fix a deliberate interface mapping warning and document that no install occurred merely from import.
The test would be relevant: Import a staging FortiGate containing one custom address and service, compare its running rules to the new package, fix a deliberate interface mapping warning and document that no install occurred merely from import. But the offered implementation—Inspect FortiManager's package status, installation logs and managed FortiGate revision to confirm the intended policy actually reached the correct target, and investigate any out-of-sync status before closing the change ticket.—addresses “Confirm FortiManager package status after a successful installation”. The action needed here is: Run FortiManager's supported policy import wizard for the selected managed device, reconcile interface mappings and address/service objects, review import warnings and create a package for explicit later approval and installation.
The question is set in this situation: A retailer acquires branches with existing custom firewall rules and needs a safe policy onboarding process before standardizing packages. Run FortiManager's supported policy import wizard for the selected managed device, reconcile interface mappings and address/service objects, review import warnings and create a package for explicit later approval and installation. Confirm it through this test: Import a staging FortiGate containing one custom address and service, compare its running rules to the new package, fix a deliberate interface mapping warning and document that no install occurred merely from import. A policy import captures device-side rules into central database scope; it is distinct from copying configuration to the gateway, and unresolved references can cause problems during later installs.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- Fortinet FCP_FMG_AD-7.6 Practice Test 49 - 10 Questions (Last Reviewed 03-Oct-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 50 - 10 Questions (Last Reviewed 02-Oct-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 51 - 10 Questions (Last Reviewed 01-Oct-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 52 - 10 Questions (Last Reviewed 30-Sep-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 53 - 10 Questions (Last Reviewed 29-Sep-2026)