Practice Exams:

Fortinet FCP_FMG_AD-7.6 Dumps

EXAM: Fortinet NSE 5 - FortiManager 7.6 Administrator
Verified By Experts
Premium Bundle
$49.99

FCP_FMG_AD-7.6 Premium ETE File


  • Premium File 62 Questions & Answers
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Fortinet FCP_FMG_AD-7.6 Practice Test 56

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?

  1. Implement: 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. Verify: 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.
  2. Implement: 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. Verify: 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.
  3. Implement: 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. Verify: 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.
  4. Implement: 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. Verify: 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.

Answer & Explanations

Correct answer: A

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.

B.

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.

C.

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.

D.

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.

Question 551

A hospital branch received an emergency firewall exception during an outage and the central team must incorporate it before the next routine package push. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. 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.
  2. 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.
  3. 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.
  4. 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.

Answer & Explanations

Correct answer: C

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. This addresses “Import existing FortiGate policy into a reviewed FortiManager policy package”, where the governing 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 stated case instead calls for: 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.

B.

Use FortiManager's policy installation preview and validation to inspect intended commands, target devices and object/interface resolution, then obtain approval before deploying a package. This addresses “Preview a FortiManager Install Wizard plan before changing a FortiGate”, where the governing principle is: The central package editor expresses desired state; the Install Wizard translates it into target-specific configuration and may reveal missing mappings or unexpected changes that are not visible from the package name. The stated case instead calls for: 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.

C.

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. 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. Verify the result with this 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.

D.

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. This addresses “Choose ADOM or policy package lock scope appropriate to the change”, where the governing principle is: A broad ADOM lock can protect consistency but impede independent change tickets, while a narrower supported lock may safely permit unrelated edits under the chosen workspace mode. The stated case instead calls for: 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.

Question 552

A hospital branch received an emergency firewall exception during an outage and the central team must incorporate it before the next routine package push. The engineer proposes the following change: 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. Which mechanism explains why it works?

  1. 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.
  2. 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.
  3. A broad ADOM lock can protect consistency but impede independent change tickets, while a narrower supported lock may safely permit unrelated edits under the chosen workspace mode.
  4. 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.

Answer & Explanations

Correct answer: B

A.

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. That explains “Import existing FortiGate policy into a reviewed FortiManager policy package”, not the mechanism behind the described change. The relevant 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.

B.

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 corresponding implementation is: 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.

C.

A broad ADOM lock can protect consistency but impede independent change tickets, while a narrower supported lock may safely permit unrelated edits under the chosen workspace mode. That explains “Choose ADOM or policy package lock scope appropriate to the change”, not the mechanism behind the described change. The relevant 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.

D.

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 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.

Question 553

A hospital branch received an emergency firewall exception during an outage and the central team must incorporate it before the next routine package push. After implementing this change—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.—which test most directly validates its intended outcome?

  1. 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.
  2. 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.
  3. 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.
  4. 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.

Answer & Explanations

Correct answer: D

A.

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. That would help test “Import existing FortiGate policy into a reviewed FortiManager policy package”, not the outcome required in this scenario. The relevant acceptance check is: 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.

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: 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.

C.

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. That would help test “Choose ADOM or policy package lock scope appropriate to the change”, not the outcome required in this scenario. The relevant acceptance check is: 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.

D.

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. This check is decisive because 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.

Question 554

A hospital branch received an emergency firewall exception during an outage and the central team must incorporate it before the next routine package push. Which proposed shortcut most directly risks unexpected site outage when central management overwrites an authorized local change that was never reconciled and should therefore be rejected?

  1. Run an unchanged old policy package after a branch emergency change and assume FortiManager always merges every local edit without review or possible overwrite.
  2. Accept every failed mapping in an import report and then install the incomplete package over production before comparing it with the existing gateway policy.
  3. Click Install All as soon as an ADOM package saves and assume the wizard cannot generate any unexpected per-device configuration changes.
  4. Claim that a read-only object label grants exclusive policy editing authority and skip required workspace locks during concurrent policy modifications.

Answer & Explanations

Correct answer: A

A.

Run an unchanged old policy package after a branch emergency change and assume FortiManager always merges every local edit without review or possible overwrite. The foreseeable failure is unexpected site outage when central management overwrites an authorized local change that was never reconciled. The safer response is: 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.

B.

Accept every failed mapping in an import report and then install the incomplete package over production before comparing it with the existing gateway policy. That shortcut risks loss of valid access rules after an incomplete first import is treated as ready for installation. Here the specific shortcut is: Run an unchanged old policy package after a branch emergency change and assume FortiManager always merges every local edit without review or possible overwrite.

C.

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: Run an unchanged old policy package after a branch emergency change and assume FortiManager always merges every local edit without review or possible overwrite.

D.

Claim that a read-only object label grants exclusive policy editing authority and skip required workspace locks during concurrent policy modifications. That shortcut risks accidental edit conflicts or avoidable maintenance delays after choosing no lock or overly broad lock scope. Here the specific shortcut is: Run an unchanged old policy package after a branch emergency change and assume FortiManager always merges every local edit without review or possible overwrite.

Question 555

A hospital branch received an emergency firewall exception during an outage and the central team must incorporate it before the next routine package push. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: 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. Verify: 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.
  2. Implement: 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. Verify: 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.
  3. Implement: 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. Verify: 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.
  4. Implement: 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. Verify: 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.

Answer & Explanations

Correct answer: B

A.

The test would be relevant: 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. But the offered implementation—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.—addresses “Import existing FortiGate policy into a reviewed FortiManager policy package”. The action needed here is: 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.

B.

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. Confirm it through this 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. 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.

C.

The action is applicable: 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. But its proposed 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.—addresses “Import existing FortiGate policy into a reviewed FortiManager policy package”. This requirement is confirmed instead by: 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.

D.

This action/test pair addresses “Preview a FortiManager Install Wizard plan before changing a FortiGate”. 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. 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. The case instead calls for: 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.

Question 556

A retail chain is moving toward central change control but some field engineers still make local FortiGate edits that must be reviewed rather than silently erased. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. 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.
  2. 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.
  3. 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.
  4. 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.

Answer & Explanations

Correct answer: C

A.

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: 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.

B.

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: 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.

C.

The question is set in this situation: A retail chain is moving toward central change control but some field engineers still make local FortiGate edits that must be reviewed rather than silently erased. 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. 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. Verify the result with this 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.

D.

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: 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.

Question 557

A retail chain is moving toward central change control but some field engineers still make local FortiGate edits that must be reviewed rather than silently erased. The engineer proposes the following change: 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. Which mechanism explains why it works?

  1. 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.
  2. 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.
  3. 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.
  4. 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.

Answer & Explanations

Correct answer: C

A.

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 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.

B.

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 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.

C.

The question is set in this situation: A retail chain is moving toward central change control but some field engineers still make local FortiGate edits that must be reviewed rather than silently erased. 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 corresponding implementation is: 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.

D.

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 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.

Question 558

A retail chain is moving toward central change control but some field engineers still make local FortiGate edits that must be reviewed rather than silently erased. After implementing this change—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.—which test most directly validates its intended outcome?

  1. 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.
  2. 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.
  3. 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.
  4. 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.

Answer & Explanations

Correct answer: B

A.

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: 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.

B.

The question is set in this situation: A retail chain is moving toward central change control but some field engineers still make local FortiGate edits that must be reviewed rather than silently erased. 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. This check is decisive because 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.

C.

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: 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.

D.

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: 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.

Question 559

A retail chain is moving toward central change control but some field engineers still make local FortiGate edits that must be reviewed rather than silently erased. Which proposed shortcut most directly risks unexpected site outage when central management overwrites an authorized local change that was never reconciled and should therefore be rejected?

  1. Install a policy package using an unmapped generic interface label across all models and assume FortiManager magically substitutes every local port correctly.
  2. 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.
  3. 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.
  4. Run an unchanged old policy package after a branch emergency change and assume FortiManager always merges every local edit without review or possible overwrite.

Answer & Explanations

Correct answer: D

A.

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: Run an unchanged old policy package after a branch emergency change and assume FortiManager always merges every local edit without review or possible overwrite.

B.

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: Run an unchanged old policy package after a branch emergency change and assume FortiManager always merges every local edit without review or possible overwrite.

C.

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: Run an unchanged old policy package after a branch emergency change and assume FortiManager always merges every local edit without review or possible overwrite.

D.

The question is set in this situation: A retail chain is moving toward central change control but some field engineers still make local FortiGate edits that must be reviewed rather than silently erased. Run an unchanged old policy package after a branch emergency change and assume FortiManager always merges every local edit without review or possible overwrite. The foreseeable failure is unexpected site outage when central management overwrites an authorized local change that was never reconciled. The safer response is: 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.

Question 560

A retail chain is moving toward central change control but some field engineers still make local FortiGate edits that must be reviewed rather than silently erased. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: 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. Verify: 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.
  2. Implement: 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. Verify: 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.
  3. Implement: 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. Verify: 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.
  4. Implement: 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. Verify: 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.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: A retail chain is moving toward central change control but some field engineers still make local FortiGate edits that must be reviewed rather than silently erased. 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. Confirm it through this 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. 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.

B.

The action is applicable: 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. 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: 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.

C.

The test would be relevant: 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. 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: 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.

D.

This action/test pair addresses “Confirm FortiManager package status after a successful installation”. 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. 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 case instead calls for: 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.

Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests