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 52

Question 510

A retailer acquires branches with existing custom firewall rules and needs a safe policy onboarding process before standardizing packages. Which combined implementation and verification plan is the best match for this workload?

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

Answer & Explanations

Correct answer: D

A.

This action/test pair addresses “Avoid accidental overwrite of local FortiGate changes during central policy installation”. Compare FortiManager's intended package and device database with recent approved local FortiGate changes, retrieve or reconcile legitimate differences, and preview the installation impact before pushing central configuration. Add a harmless approved local rule in a staging firewall, compare central package and device revisions, import or translate it to managed policy, then install and confirm the exception is preserved. The case instead calls for: Run FortiManager's supported policy import wizard for the selected managed device, reconcile interface mappings and address/service objects, review import warnings and create a package for explicit later approval and installation.

B.

The action is applicable: Run FortiManager's supported policy import wizard for the selected managed device, reconcile interface mappings and address/service objects, review import warnings and create a package for explicit later approval and installation. But its proposed test—Install a harmless lab policy to two gateways, disconnect one during the task, verify only one successful result and reconcile the failed target after connectivity returns.—addresses “Confirm FortiManager package status after a successful installation”. This requirement is confirmed instead by: Import a staging FortiGate containing one custom address and service, compare its running rules to the new package, fix a deliberate interface mapping warning and document that no install occurred merely from import.

C.

The test would be relevant: Import a staging FortiGate containing one custom address and service, compare its running rules to the new package, fix a deliberate interface mapping warning and document that no install occurred merely from import. But the offered implementation—Inspect FortiManager's package status, installation logs and managed FortiGate revision to confirm the intended policy actually reached the correct target, and investigate any out-of-sync status before closing the change ticket.—addresses “Confirm FortiManager package status after a successful installation”. The action needed here is: Run FortiManager's supported policy import wizard for the selected managed device, reconcile interface mappings and address/service objects, review import warnings and create a package for explicit later approval and installation.

D.

The question is set in this situation: A retailer acquires branches with existing custom firewall rules and needs a safe policy onboarding process before standardizing packages. Run FortiManager's supported policy import wizard for the selected managed device, reconcile interface mappings and address/service objects, review import warnings and create a package for explicit later approval and installation. Confirm it through this test: Import a staging FortiGate containing one custom address and service, compare its running rules to the new package, fix a deliberate interface mapping warning and document that no install occurred merely from import. A policy import captures device-side rules into central database scope; it is distinct from copying configuration to the gateway, and unresolved references can cause problems during later installs.

Question 511

A medical center wants to assess how one FortiManager package will modify each clinic firewall before the scheduled maintenance window. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. 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.
  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. 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.
  4. Define a suitable dynamic mapping for a centrally shared policy object and configure distinct authorized values per target FortiGate without copying private branch subnets into one universal static object.

Answer & Explanations

Correct answer: B

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

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

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

D.

Define a suitable dynamic mapping for a centrally shared policy object and configure distinct authorized values per target FortiGate without copying private branch subnets into one universal static object. This addresses “Use FortiManager dynamic objects for per-device address differences”, where the governing principle is: Dynamic objects let a common logical name resolve to different device-specific values at installation; leaving a mapping undefined or treating it as globally identical can send traffic to the wrong destination. The stated case instead calls for: 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.

Question 512

A medical center wants to assess how one FortiManager package will modify each clinic firewall before the scheduled maintenance window. The engineer proposes the following change: 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. 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. Dynamic objects let a common logical name resolve to different device-specific values at installation; leaving a mapping undefined or treating it as globally identical can send traffic to the wrong destination.
  3. 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.
  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.

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

B.

Dynamic objects let a common logical name resolve to different device-specific values at installation; leaving a mapping undefined or treating it as globally identical can send traffic to the wrong destination. That explains “Use FortiManager dynamic objects for per-device address differences”, not the mechanism behind the described change. The relevant principle is: 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.

C.

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

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

Question 513

A medical center wants to assess how one FortiManager package will modify each clinic firewall before the scheduled maintenance window. After implementing this change—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.—which test most directly validates its intended outcome?

  1. Map a logical internal-network object to two different lab branch subnets, preview the installed package for each FortiGate and verify the generated addresses match the site.
  2. 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. 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. 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: D

A.

Map a logical internal-network object to two different lab branch subnets, preview the installed package for each FortiGate and verify the generated addresses match the site. That would help test “Use FortiManager dynamic objects for per-device address differences”, not the outcome required in this scenario. The relevant acceptance check is: 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.

B.

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

C.

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

D.

Preview a staging package with a dynamic object for two FortiGate targets, compare each generated change, install to one test device and confirm its actual policy counters. This check is decisive because 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.

Question 514

A medical center wants to assess how one FortiManager package will modify each clinic firewall before the scheduled maintenance window. Which proposed shortcut most directly risks network exposure or traffic disruption after deploying unchecked generated policy differences and should therefore be rejected?

  1. 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.
  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. Click Install All as soon as an ADOM package saves and assume the wizard cannot generate any unexpected per-device configuration changes.
  4. Set every branch object's address to the first store's network and assume FortiManager automatically discovers the correct site-specific values from an identical object name.

Answer & Explanations

Correct answer: C

A.

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: Click Install All as soon as an ADOM package saves and assume the wizard cannot generate any unexpected per-device configuration changes.

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: Click Install All as soon as an ADOM package saves and assume the wizard cannot generate any unexpected per-device configuration changes.

C.

Click Install All as soon as an ADOM package saves and assume the wizard cannot generate any unexpected per-device configuration changes. The foreseeable failure is network exposure or traffic disruption after deploying unchecked generated policy differences. The safer response is: 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.

D.

Set every branch object's address to the first store's network and assume FortiManager automatically discovers the correct site-specific values from an identical object name. That shortcut risks cross-site routing errors or unintended access after failing to map a shared dynamic object for each target device. Here the specific shortcut is: Click Install All as soon as an ADOM package saves and assume the wizard cannot generate any unexpected per-device configuration changes.

Question 515

A medical center wants to assess how one FortiManager package will modify each clinic firewall before the scheduled maintenance window. Which combined implementation and verification plan is the best match for this workload?

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

A.

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

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

C.

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

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

Question 516

An MSP needs auditors to confirm policy targets and command diffs were reviewed prior to production installation. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. 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.
  2. 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.
  3. 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.
  4. Use FortiManager policy checks and relevant object validations to inspect shadowed, inconsistent or invalid rules and referenced interfaces, then resolve significant issues before installing to production targets.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: An MSP needs auditors to confirm policy targets and command diffs were reviewed prior to production installation. 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. 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. Verify the result with this 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.

B.

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

C.

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

D.

Use FortiManager policy checks and relevant object validations to inspect shadowed, inconsistent or invalid rules and referenced interfaces, then resolve significant issues before installing to production targets. This addresses “Run FortiManager policy check before approving a package installation”, where the governing principle is: A syntactically saved rule may never match because a broader earlier rule captures traffic; checking effective policy logic prevents false assumptions that a newly written rule changes enforcement. The stated case instead calls for: 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.

Question 517

An MSP needs auditors to confirm policy targets and command diffs were reviewed prior to production installation. The engineer proposes the following change: 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. 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 syntactically saved rule may never match because a broader earlier rule captures traffic; checking effective policy logic prevents false assumptions that a newly written rule changes enforcement.
  3. 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.
  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: D

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

B.

A syntactically saved rule may never match because a broader earlier rule captures traffic; checking effective policy logic prevents false assumptions that a newly written rule changes enforcement. That explains “Run FortiManager policy check before approving a package installation”, not the mechanism behind the described change. The relevant principle is: 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.

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

D.

The question is set in this situation: An MSP needs auditors to confirm policy targets and command diffs were reviewed prior to production installation. 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 corresponding implementation is: 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.

Question 518

An MSP needs auditors to confirm policy targets and command diffs were reviewed prior to production installation. After implementing this change—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.—which test most directly validates its intended outcome?

  1. 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.
  2. 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. Add a narrowly scoped deny beneath a broad allow in a lab package, use the available policy analysis and simulated traffic to reveal the shadowed behavior, then revise approved rule order.
  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.

The question is set in this situation: An MSP needs auditors to confirm policy targets and command diffs were reviewed prior to production installation. 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. This check is decisive because 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.

B.

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

C.

Add a narrowly scoped deny beneath a broad allow in a lab package, use the available policy analysis and simulated traffic to reveal the shadowed behavior, then revise approved rule order. That would help test “Run FortiManager policy check before approving a package installation”, not the outcome required in this scenario. The relevant acceptance check is: 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.

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

Question 519

An MSP needs auditors to confirm policy targets and command diffs were reviewed prior to production installation. Which proposed shortcut most directly risks network exposure or traffic disruption after deploying unchecked generated policy differences 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. Click Install All as soon as an ADOM package saves and assume the wizard cannot generate any unexpected per-device configuration changes.
  3. Save a new deny rule at the end of a policy list and assume it always overrides an earlier matching allow because its description says High Priority.
  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.

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: Click Install All as soon as an ADOM package saves and assume the wizard cannot generate any unexpected per-device configuration changes.

B.

The question is set in this situation: An MSP needs auditors to confirm policy targets and command diffs were reviewed prior to production installation. Click Install All as soon as an ADOM package saves and assume the wizard cannot generate any unexpected per-device configuration changes. The foreseeable failure is network exposure or traffic disruption after deploying unchecked generated policy differences. The safer response is: 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.

C.

Save a new deny rule at the end of a policy list and assume it always overrides an earlier matching allow because its description says High Priority. That shortcut risks unintended permitted access after an ineffective shadowed security rule is installed without verification. Here the specific shortcut is: Click Install All as soon as an ADOM package saves and assume the wizard cannot generate any unexpected per-device configuration changes.

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: Click Install All as soon as an ADOM package saves and assume the wizard cannot generate any unexpected per-device configuration changes.

Question 520

An MSP needs auditors to confirm policy targets and command diffs were reviewed prior to production installation. 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: 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: 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.
  4. 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: 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: 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.

B.

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

C.

The question is set in this situation: An MSP needs auditors to confirm policy targets and command diffs were reviewed prior to production installation. 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. Confirm it through this 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. 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.

D.

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

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