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 54

Question 530

A managed services team is diagnosing a failed install preview on one customer's ADOM and must distinguish invalid configuration from a connectivity problem. Which combined implementation and verification plan is the best match for this workload?

  1. 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: 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.
  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: 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.
  3. 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: 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.
  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: D

A.

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

B.

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

C.

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

D.

The question is set in this situation: A managed services team is diagnosing a failed install preview on one customer's ADOM and must distinguish invalid configuration from a connectivity problem. 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. Confirm it through this test: 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. 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.

Question 531

A retail branch replaces a failed FortiGate appliance and needs to restore its last approved centralized policy without accidentally permitting extra traffic. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

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

Answer & Explanations

Correct answer: A

A.

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

B.

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

C.

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

D.

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

Question 532

A retail branch replaces a failed FortiGate appliance and needs to restore its last approved centralized policy without accidentally permitting extra traffic. The engineer proposes the following change: 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. Which mechanism explains why it works?

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

A.

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 previously approved package can restore intended filtering, but changed hardware ports, device serial numbers and target associations may require reconciliation before a safe reinstall.

B.

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 previously approved package can restore intended filtering, but changed hardware ports, device serial numbers and target associations may require reconciliation before a safe reinstall.

C.

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

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

A retail branch replaces a failed FortiGate appliance and needs to restore its last approved centralized policy without accidentally permitting extra traffic. After implementing this change—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.—which test most directly validates its intended outcome?

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

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

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

C.

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

D.

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

Question 534

A retail branch replaces a failed FortiGate appliance and needs to restore its last approved centralized policy without accidentally permitting extra traffic. Which proposed shortcut most directly risks unprotected or disconnected branch when replacement hardware is assumed to inherit policy without authenticated management and installation and should therefore be rejected?

  1. Click Install All as soon as an ADOM package saves and assume the wizard cannot generate any unexpected per-device configuration changes.
  2. 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.
  3. Make an internet-access exception on one shared FortiManager package and assume its description automatically limits installation to the requesting branch.
  4. 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.

Answer & Explanations

Correct answer: B

A.

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

B.

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. The foreseeable failure is unprotected or disconnected branch when replacement hardware is assumed to inherit policy without authenticated management and installation. The safer response 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.

C.

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

D.

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

Question 535

A retail branch replaces a failed FortiGate appliance and needs to restore its last approved centralized policy without accidentally permitting extra traffic. Which combined implementation and verification plan is the best match for this workload?

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

A.

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

B.

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

C.

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.

D.

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

Question 536

A government facility is preparing a spare gateway and wants to test policy reinstallation including different interface hardware and management enrollment. 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. 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.
  3. Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change.
  4. 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.

Answer & Explanations

Correct answer: D

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

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

C.

Configure a supported workspace mode for ADOM policy management, instruct administrators to acquire required locks before editing, and confirm another editor cannot overwrite the protected change. This addresses “Enable FortiManager workspace mode for concurrent policy editing”, where the governing principle is: Workspace locking coordinates concurrent write sessions inside FortiManager, preventing conflicting central edits; authentication alone does not serialize administrators editing the same object. The stated case instead calls for: 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.

D.

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

Question 537

A government facility is preparing a spare gateway and wants to test policy reinstallation including different interface hardware and management enrollment. The engineer proposes the following change: 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. Which mechanism explains why it works?

  1. 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.
  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 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.
  4. Workspace locking coordinates concurrent write sessions inside FortiManager, preventing conflicting central edits; authentication alone does not serialize administrators editing the same object.

Answer & Explanations

Correct answer: A

A.

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

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. 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 previously approved package can restore intended filtering, but changed hardware ports, device serial numbers and target associations may require reconciliation before a safe reinstall.

C.

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 previously approved package can restore intended filtering, but changed hardware ports, device serial numbers and target associations may require reconciliation before a safe reinstall.

D.

Workspace locking coordinates concurrent write sessions inside FortiManager, preventing conflicting central edits; authentication alone does not serialize administrators editing the same object. That explains “Enable FortiManager workspace mode for concurrent policy editing”, not the mechanism behind the described change. The relevant principle is: 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 538

A government facility is preparing a spare gateway and wants to test policy reinstallation including different interface hardware and management enrollment. After implementing this change—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.—which test most directly validates its intended outcome?

  1. Have two lab administrators open the same ADOM, let one acquire the permitted lock and change a dummy object, and confirm the second cannot commit a conflicting edit until release.
  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. 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.
  4. 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.

Answer & Explanations

Correct answer: C

A.

Have two lab administrators open the same ADOM, let one acquire the permitted lock and change a dummy object, and confirm the second cannot commit a conflicting edit until release. That would help test “Enable FortiManager workspace mode for concurrent policy editing”, not the outcome required in this scenario. The relevant acceptance check is: 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.

B.

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

C.

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

D.

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

Question 539

A government facility is preparing a spare gateway and wants to test policy reinstallation including different interface hardware and management enrollment. Which proposed shortcut most directly risks unprotected or disconnected branch when replacement hardware is assumed to inherit policy without authenticated management and installation and should therefore be rejected?

  1. Accept every failed mapping in an import report and then install the incomplete package over production before comparing it with the existing gateway policy.
  2. 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.
  3. Allow two administrators to simultaneously change the same production policy package with workspace disabled and assume last-writer conflict cannot occur because their logins are different.
  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: B

A.

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

B.

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. 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. The foreseeable failure is unprotected or disconnected branch when replacement hardware is assumed to inherit policy without authenticated management and installation. The safer response 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.

C.

Allow two administrators to simultaneously change the same production policy package with workspace disabled and assume last-writer conflict cannot occur because their logins are different. That shortcut risks lost or overwritten firewall policy edits when concurrent administrators lack controlled workspace locking. Here the specific shortcut is: 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.

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

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?

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

A.

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.

B.

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.

C.

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.

D.

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.

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