Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 55
Question 540
A government facility is preparing a spare gateway and wants to test policy reinstallation including different interface hardware and management enrollment. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: D
The test would be relevant: Bind a staged replacement FortiGate to its intended FortiManager device entry, preview the existing approved package and install it while testing both permitted and denied representative flows. But the offered implementation—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.—addresses “Avoid accidental overwrite of local FortiGate changes during central policy installation”. The action needed here is: After a managed FortiGate is replaced or recovered, verify the new device identity, supported firmware and interface mappings, then perform an approved policy package reinstall and validate actual enforcement.
This action/test pair addresses “Import existing FortiGate policy into a reviewed FortiManager policy package”. 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. 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 case instead calls for: After a managed FortiGate is replaced or recovered, verify the new device identity, supported firmware and interface mappings, then perform an approved policy package reinstall and validate actual enforcement.
The action is applicable: After a managed FortiGate is replaced or recovered, verify the new device identity, supported firmware and interface mappings, then perform an approved policy package reinstall and validate actual enforcement. But its proposed test—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.—addresses “Avoid accidental overwrite of local FortiGate changes during central policy installation”. This requirement is confirmed instead by: Bind a staged replacement FortiGate to its intended FortiManager device entry, preview the existing approved package and install it while testing both permitted and denied representative flows.
The question is set in this situation: A government facility is preparing a spare gateway and wants to test policy reinstallation including different interface hardware and management enrollment. After a managed FortiGate is replaced or recovered, verify the new device identity, supported firmware and interface mappings, then perform an approved policy package reinstall and validate actual enforcement. Confirm it through this test: Bind a staged replacement FortiGate to its intended FortiManager device entry, preview the existing approved package and install it while testing both permitted and denied representative flows. A previously approved package can restore intended filtering, but changed hardware ports, device serial numbers and target associations may require reconciliation before a safe reinstall.
Question 541
A bank deploys one reviewed policy package to multiple branches and needs evidence that each target, not only the central job, completed successfully. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: A
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. 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. Verify the result with this 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.
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: 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.
After a managed FortiGate is replaced or recovered, verify the new device identity, supported firmware and interface mappings, then perform an approved policy package reinstall and validate actual enforcement. This addresses “Reinstall a known approved FortiManager policy package after device replacement”, where the governing principle is: A previously approved package can restore intended filtering, but changed hardware ports, device serial numbers and target associations may require reconciliation before a safe reinstall. The stated case instead calls for: 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.
Configure the intended interface mapping for each target firewall so policy packages referencing normalized logical interfaces resolve to the real supported FortiGate ports at installation. This addresses “Map normalized FortiManager policy interfaces to differing FortiGate port names”, where the governing principle is: Physical interface names and zone membership differ across appliance models; central policy rules cannot be deployed safely when a logical interface mapping is absent or points to the wrong data path. The stated case instead calls for: 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.
Question 542
A bank deploys one reviewed policy package to multiple branches and needs evidence that each target, not only the central job, completed successfully. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: C
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 successful central submission is not proof every gateway accepted and enforced the generated policy; per-device execution and database synchronization states provide necessary evidence.
A previously approved package can restore intended filtering, but changed hardware ports, device serial numbers and target associations may require reconciliation before a safe reinstall. That explains “Reinstall a known approved FortiManager policy package after device replacement”, not the mechanism behind the described change. The relevant 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.
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 corresponding implementation is: 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.
Physical interface names and zone membership differ across appliance models; central policy rules cannot be deployed safely when a logical interface mapping is absent or points to the wrong data path. That explains “Map normalized FortiManager policy interfaces to differing FortiGate port names”, not the mechanism behind the described change. The relevant 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.
Question 543
A bank deploys one reviewed policy package to multiple branches and needs evidence that each target, not only the central job, completed successfully. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: B
Bind a staged replacement FortiGate to its intended FortiManager device entry, preview the existing approved package and install it while testing both permitted and denied representative flows. That would help test “Reinstall a known approved FortiManager policy package after device replacement”, not the outcome required in this scenario. The relevant acceptance check is: 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.
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. This check is decisive because 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.
Preview one branch package targeting a FortiGate with wan1 and another with a differently named uplink, verify mapped interface values and run controlled permitted/denied traffic tests after install. That would help test “Map normalized FortiManager policy interfaces to differing FortiGate port names”, not the outcome required in this scenario. The relevant acceptance check is: 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.
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: 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.
Question 544
A bank deploys one reviewed policy package to multiple branches and needs evidence that each target, not only the central job, completed successfully. Which proposed shortcut most directly risks false audit evidence and inconsistent network filtering after installation task state is mistaken for device enforcement and should therefore be rejected?
Answer & Explanations
Correct answer: D
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: 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.
Ship a replacement firewall with factory-default permit behavior and assume FortiManager automatically installs every old policy as soon as the new device has the same hostname. That shortcut risks unprotected or disconnected branch when replacement hardware is assumed to inherit policy without authenticated management and installation. Here the specific shortcut is: 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.
Install a policy package using an unmapped generic interface label across all models and assume FortiManager magically substitutes every local port correctly. That shortcut risks broken connectivity or bypassed filtering after shared policy interfaces resolve incorrectly on target FortiGates. Here the specific shortcut is: 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.
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. The foreseeable failure is false audit evidence and inconsistent network filtering after installation task state is mistaken for device enforcement. The safer response is: 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.
Question 545
A bank deploys one reviewed policy package to multiple branches and needs evidence that each target, not only the central job, completed successfully. 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: 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.
The test would be relevant: 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. But the offered implementation—After a managed FortiGate is replaced or recovered, verify the new device identity, supported firmware and interface mappings, then perform an approved policy package reinstall and validate actual enforcement.—addresses “Reinstall a known approved FortiManager policy package after device replacement”. The action needed here is: 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.
The action is applicable: 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. But its proposed test—Bind a staged replacement FortiGate to its intended FortiManager device entry, preview the existing approved package and install it while testing both permitted and denied representative flows.—addresses “Reinstall a known approved FortiManager policy package after device replacement”. This requirement is confirmed instead by: 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.
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. Confirm it through this 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. 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.
Question 546
A university is investigating why an ADOM shows a policy package out of sync even though last night's central installation task was scheduled. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: A
The question is set in this situation: A university is investigating why an ADOM shows a policy package out of sync even though last night's central installation task was scheduled. 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. 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. Verify the result with this 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.
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: 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.
Set the intended supported installation target or per-policy scope for a FortiManager rule, review how it applies to individual managed FortiGates, and preview each target's resulting policy before committing installation. This addresses “Verify per-policy installation targets rather than relying on package-wide assumptions”, where the governing principle is: One centrally shared package may contain rules relevant only to particular branches; leaving rule targets overly broad can create unintended permissions even when the package assignment itself is correct. The stated case instead calls for: 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.
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: 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.
Question 547
A university is investigating why an ADOM shows a policy package out of sync even though last night's central installation task was scheduled. The engineer proposes the following change: 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. 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 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 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 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 question is set in this situation: A university is investigating why an ADOM shows a policy package out of sync even though last night's central installation task was scheduled. 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 corresponding implementation is: 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.
One centrally shared package may contain rules relevant only to particular branches; leaving rule targets overly broad can create unintended permissions even when the package assignment itself is correct. That explains “Verify per-policy installation targets rather than relying on package-wide assumptions”, not the mechanism behind the described change. The relevant 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.
Question 548
A university is investigating why an ADOM shows a policy package out of sync even though last night's central installation task was scheduled. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: B
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: 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.
The question is set in this situation: A university is investigating why an ADOM shows a policy package out of sync even though last night's central installation task was scheduled. 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. This check is decisive because 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.
In a lab assign a single branch-specific rule only to one of two package targets, compare the generated firewall configurations and confirm the other gateway does not receive the exception. That would help test “Verify per-policy installation targets rather than relying on package-wide assumptions”, not the outcome required in this scenario. The relevant acceptance check is: 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.
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: 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.
Question 549
A university is investigating why an ADOM shows a policy package out of sync even though last night's central installation task was scheduled. Which proposed shortcut most directly risks false audit evidence and inconsistent network filtering after installation task state is mistaken for device enforcement and should therefore be rejected?
Answer & Explanations
Correct answer: D
Make an internet-access exception on one shared FortiManager package and assume its description automatically limits installation to the requesting branch. That shortcut risks overly broad access when a site-specific rule is deployed to every firewall in a shared package. Here the specific shortcut is: 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.
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: 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.
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: 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.
The question is set in this situation: A university is investigating why an ADOM shows a policy package out of sync even though last night's central installation task was scheduled. 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. The foreseeable failure is false audit evidence and inconsistent network filtering after installation task state is mistaken for device enforcement. The safer response is: 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.
Question 550
A university is investigating why an ADOM shows a policy package out of sync even though last night's central installation task was scheduled. 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 university is investigating why an ADOM shows a policy package out of sync even though last night's central installation task was scheduled. 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. Confirm it through this 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. 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 action is applicable: 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. 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: 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.
The test would be relevant: 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. 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: 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 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: 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.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- Fortinet FCP_FMG_AD-7.6 Practice Test 53 - 10 Questions (Last Reviewed 29-Sep-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 54 - 10 Questions (Last Reviewed 28-Sep-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 55 - 10 Questions (Last Reviewed 27-Sep-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 56 - 10 Questions (Last Reviewed 26-Sep-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 57 - 10 Questions (Last Reviewed 21-Nov-2026)