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 75

Question 740

A healthcare organization needs to separate approved device-level maintenance from centrally authored but not-yet-installed address changes. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Use device-level revision comparison to restore an approved local configuration baseline when appropriate and separately validate that the current ADOM package remains correct before installing it. Verify: Take a staged device revision, make a local interface setting error, restore the target configuration and confirm an unrelated ADOM service object and second firewall package remain unchanged.
  2. Implement: Inspect the FortiManager configuration comparison and revision history for a managed firewall, determine whether an unapproved local change or an uninstalled central object update explains the difference, and choose a scoped remedy. Verify: Modify one staged FortiGate locally and separately edit an ADOM address object without installation, compare status and history, then demonstrate the correct action for each case.
  3. Implement: Inspect the FortiManager configuration comparison and revision history for a managed firewall, determine whether an unapproved local change or an uninstalled central object update explains the difference, and choose a scoped remedy. Verify: In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation.
  4. Implement: Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path. Verify: Modify one staged FortiGate locally and separately edit an ADOM address object without installation, compare status and history, then demonstrate the correct action for each case.

Answer & Explanations

Correct answer: B

A.

The question is set in this situation: A healthcare organization needs to separate approved device-level maintenance from centrally authored but not-yet-installed address changes. This action/test pair addresses “Restore a managed FortiGate's device database without overwriting independent ADOM changes”. Use device-level revision comparison to restore an approved local configuration baseline when appropriate and separately validate that the current ADOM package remains correct before installing it. Take a staged device revision, make a local interface setting error, restore the target configuration and confirm an unrelated ADOM service object and second firewall package remain unchanged. The case instead calls for: Inspect the FortiManager configuration comparison and revision history for a managed firewall, determine whether an unapproved local change or an uninstalled central object update explains the difference, and choose a scoped remedy.

B.

The question is set in this situation: A healthcare organization needs to separate approved device-level maintenance from centrally authored but not-yet-installed address changes. Inspect the FortiManager configuration comparison and revision history for a managed firewall, determine whether an unapproved local change or an uninstalled central object update explains the difference, and choose a scoped remedy. Confirm it through this test: Modify one staged FortiGate locally and separately edit an ADOM address object without installation, compare status and history, then demonstrate the correct action for each case. A missing policy install and a direct FortiGate CLI edit may produce similar high-level status warnings but require opposite corrective actions: install approved intent or retrieve and review actual local state.

C.

The question is set in this situation: A healthcare organization needs to separate approved device-level maintenance from centrally authored but not-yet-installed address changes. The action is applicable: Inspect the FortiManager configuration comparison and revision history for a managed firewall, determine whether an unapproved local change or an uninstalled central object update explains the difference, and choose a scoped remedy. But its proposed test—In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation.—addresses “Diagnose an ADOM version compatibility warning on a mixed-firmware FortiGate fleet”. This requirement is confirmed instead by: Modify one staged FortiGate locally and separately edit an ADOM address object without installation, compare status and history, then demonstrate the correct action for each case.

D.

The question is set in this situation: A healthcare organization needs to separate approved device-level maintenance from centrally authored but not-yet-installed address changes. The test would be relevant: Modify one staged FortiGate locally and separately edit an ADOM address object without installation, compare status and history, then demonstrate the correct action for each case. But the offered implementation—Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path.—addresses “Diagnose an ADOM version compatibility warning on a mixed-firmware FortiGate fleet”. The action needed here is: Inspect the FortiManager configuration comparison and revision history for a managed firewall, determine whether an unapproved local change or an uninstalled central object update explains the difference, and choose a scoped remedy.

Question 741

A bank manages branch FortiGates on different software releases and only one device rejects an updated policy package. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. Identify FortiManager partitions, database storage and safe cleanup options when disk usage is high, preserve required configuration backups and audit history, and verify adequate free space before resuming heavy policy tasks.
  2. Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path.
  3. Use device-level revision comparison to restore an approved local configuration baseline when appropriate and separately validate that the current ADOM package remains correct before installing it.
  4. Compare the managed device's target-specific database and retrieved FortiGate configuration with shared ADOM policy objects, identifying which layer diverges before selecting retrieve, import or install operations.

Answer & Explanations

Correct answer: B

A.

Identify FortiManager partitions, database storage and safe cleanup options when disk usage is high, preserve required configuration backups and audit history, and verify adequate free space before resuming heavy policy tasks. This addresses “Investigate FortiManager high disk usage and protected log or backup retention”, where the governing principle is: Insufficient central storage can interfere with management databases and revisions, but indiscriminately deleting backup or database files risks destroying recovery artifacts and making the condition worse. The stated case instead calls for: Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path.

B.

Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path. Policy and object schema is tied to supported ADOM versions; a configuration that works on one firmware generation may be invalid on another, even with healthy FGFM. Verify the result with this test: In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation.

C.

Use device-level revision comparison to restore an approved local configuration baseline when appropriate and separately validate that the current ADOM package remains correct before installing it. This addresses “Restore a managed FortiGate's device database without overwriting independent ADOM changes”, where the governing principle is: Device revisions are narrower than an ADOM-wide object revision; restoring a gateway configuration should not silently reverse unrelated centrally reviewed changes for other devices. The stated case instead calls for: Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path.

D.

Compare the managed device's target-specific database and retrieved FortiGate configuration with shared ADOM policy objects, identifying which layer diverges before selecting retrieve, import or install operations. This addresses “Compare FortiManager device-level database against ADOM-level policy objects to locate drift”, where the governing principle is: Shared policy/object databases and device-specific configuration records serve different purposes; a status mismatch can arise from a local change, an uninstalled ADOM package or a missing interface map. The stated case instead calls for: Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path.

Question 742

A bank manages branch FortiGates on different software releases and only one device rejects an updated policy package. The engineer proposes the following change: Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path. Which mechanism explains why it works?

  1. Shared policy/object databases and device-specific configuration records serve different purposes; a status mismatch can arise from a local change, an uninstalled ADOM package or a missing interface map.
  2. Device revisions are narrower than an ADOM-wide object revision; restoring a gateway configuration should not silently reverse unrelated centrally reviewed changes for other devices.
  3. Insufficient central storage can interfere with management databases and revisions, but indiscriminately deleting backup or database files risks destroying recovery artifacts and making the condition worse.
  4. Policy and object schema is tied to supported ADOM versions; a configuration that works on one firmware generation may be invalid on another, even with healthy FGFM.

Answer & Explanations

Correct answer: D

A.

Shared policy/object databases and device-specific configuration records serve different purposes; a status mismatch can arise from a local change, an uninstalled ADOM package or a missing interface map. That explains “Compare FortiManager device-level database against ADOM-level policy objects to locate drift”, not the mechanism behind the described change. The relevant principle is: Policy and object schema is tied to supported ADOM versions; a configuration that works on one firmware generation may be invalid on another, even with healthy FGFM.

B.

Device revisions are narrower than an ADOM-wide object revision; restoring a gateway configuration should not silently reverse unrelated centrally reviewed changes for other devices. That explains “Restore a managed FortiGate's device database without overwriting independent ADOM changes”, not the mechanism behind the described change. The relevant principle is: Policy and object schema is tied to supported ADOM versions; a configuration that works on one firmware generation may be invalid on another, even with healthy FGFM.

C.

Insufficient central storage can interfere with management databases and revisions, but indiscriminately deleting backup or database files risks destroying recovery artifacts and making the condition worse. That explains “Investigate FortiManager high disk usage and protected log or backup retention”, not the mechanism behind the described change. The relevant principle is: Policy and object schema is tied to supported ADOM versions; a configuration that works on one firmware generation may be invalid on another, even with healthy FGFM.

D.

Policy and object schema is tied to supported ADOM versions; a configuration that works on one firmware generation may be invalid on another, even with healthy FGFM. The corresponding implementation is: Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path.

Question 743

A bank manages branch FortiGates on different software releases and only one device rejects an updated policy package. After implementing this change—Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path.—which test most directly validates its intended outcome?

  1. In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation.
  2. In a lab simulate a storage threshold alarm, inspect supported filesystem and application usage tools, remove only approved disposable data and confirm policy database and backup integrity remain intact.
  3. Create a harmless shared ADOM service edit and a separate local device change, inspect both database views, classify each drift and reconcile them independently through approved operations.
  4. Take a staged device revision, make a local interface setting error, restore the target configuration and confirm an unrelated ADOM service object and second firewall package remain unchanged.

Answer & Explanations

Correct answer: A

A.

In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation. This check is decisive because policy and object schema is tied to supported ADOM versions; a configuration that works on one firmware generation may be invalid on another, even with healthy FGFM.

B.

In a lab simulate a storage threshold alarm, inspect supported filesystem and application usage tools, remove only approved disposable data and confirm policy database and backup integrity remain intact. That would help test “Investigate FortiManager high disk usage and protected log or backup retention”, not the outcome required in this scenario. The relevant acceptance check is: In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation.

C.

Create a harmless shared ADOM service edit and a separate local device change, inspect both database views, classify each drift and reconcile them independently through approved operations. That would help test “Compare FortiManager device-level database against ADOM-level policy objects to locate drift”, not the outcome required in this scenario. The relevant acceptance check is: In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation.

D.

Take a staged device revision, make a local interface setting error, restore the target configuration and confirm an unrelated ADOM service object and second firewall package remain unchanged. That would help test “Restore a managed FortiGate's device database without overwriting independent ADOM changes”, not the outcome required in this scenario. The relevant acceptance check is: In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation.

Question 744

A bank manages branch FortiGates on different software releases and only one device rejects an updated policy package. Which proposed shortcut most directly risks rejected policy and inconsistent enforcement across device firmware variants after version support is assumed and should therefore be rejected?

  1. Delete arbitrary FortiManager database directories and every configuration archive to clear an alarm immediately without checking which files contain active ADOM objects.
  2. Fix an out-of-sync device by deleting the entire customer ADOM because central and device databases must always be byte-for-byte identical at all times.
  3. Ignore a FortiOS compatibility warning and force a new unsupported policy feature to every branch simply because the latest FortiManager UI can display it.
  4. Restore the entire FortiManager global database because one branch FortiGate's interface description is incorrect and assume no other tenants or policies can be affected.

Answer & Explanations

Correct answer: C

A.

Delete arbitrary FortiManager database directories and every configuration archive to clear an alarm immediately without checking which files contain active ADOM objects. That shortcut risks irrecoverable management data loss after an uncontrolled disk cleanup removes critical central records. Here the specific shortcut is: Ignore a FortiOS compatibility warning and force a new unsupported policy feature to every branch simply because the latest FortiManager UI can display it.

B.

Fix an out-of-sync device by deleting the entire customer ADOM because central and device databases must always be byte-for-byte identical at all times. That shortcut risks avoidable loss of shared policy state when device-specific drift is mistaken for corruption of the ADOM database. Here the specific shortcut is: Ignore a FortiOS compatibility warning and force a new unsupported policy feature to every branch simply because the latest FortiManager UI can display it.

C.

Ignore a FortiOS compatibility warning and force a new unsupported policy feature to every branch simply because the latest FortiManager UI can display it. The foreseeable failure is rejected policy and inconsistent enforcement across device firmware variants after version support is assumed. The safer response is: Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path.

D.

Restore the entire FortiManager global database because one branch FortiGate's interface description is incorrect and assume no other tenants or policies can be affected. That shortcut risks unrelated policy rollback and cross-tenant disruption after a device-only problem is treated as global management recovery. Here the specific shortcut is: Ignore a FortiOS compatibility warning and force a new unsupported policy feature to every branch simply because the latest FortiManager UI can display it.

Question 745

A bank manages branch FortiGates on different software releases and only one device rejects an updated policy package. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path. Verify: Take a staged device revision, make a local interface setting error, restore the target configuration and confirm an unrelated ADOM service object and second firewall package remain unchanged.
  2. Implement: Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path. Verify: In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation.
  3. Implement: Compare the managed device's target-specific database and retrieved FortiGate configuration with shared ADOM policy objects, identifying which layer diverges before selecting retrieve, import or install operations. Verify: Create a harmless shared ADOM service edit and a separate local device change, inspect both database views, classify each drift and reconcile them independently through approved operations.
  4. Implement: Use device-level revision comparison to restore an approved local configuration baseline when appropriate and separately validate that the current ADOM package remains correct before installing it. Verify: In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation.

Answer & Explanations

Correct answer: B

A.

The action is applicable: Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path. But its proposed test—Take a staged device revision, make a local interface setting error, restore the target configuration and confirm an unrelated ADOM service object and second firewall package remain unchanged.—addresses “Restore a managed FortiGate's device database without overwriting independent ADOM changes”. This requirement is confirmed instead by: In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation.

B.

Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path. Confirm it through this test: In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation. Policy and object schema is tied to supported ADOM versions; a configuration that works on one firmware generation may be invalid on another, even with healthy FGFM.

C.

This action/test pair addresses “Compare FortiManager device-level database against ADOM-level policy objects to locate drift”. Compare the managed device's target-specific database and retrieved FortiGate configuration with shared ADOM policy objects, identifying which layer diverges before selecting retrieve, import or install operations. Create a harmless shared ADOM service edit and a separate local device change, inspect both database views, classify each drift and reconcile them independently through approved operations. The case instead calls for: Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path.

D.

The test would be relevant: In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation. But the offered implementation—Use device-level revision comparison to restore an approved local configuration baseline when appropriate and separately validate that the current ADOM package remains correct before installing it.—addresses “Restore a managed FortiGate's device database without overwriting independent ADOM changes”. The action needed here is: Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path.

Question 746

An MSP is moving a customer from an old ADOM version to FortiOS 7.6 while maintaining uninterrupted policy control of other customer devices. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path.
  2. Inspect the FortiManager policy import report, identify the specific missing device interface or unresolved address object, repair the corresponding ADOM database mapping and retry the import after a scoped backup.
  3. Use device-level revision comparison to restore an approved local configuration baseline when appropriate and separately validate that the current ADOM package remains correct before installing it.
  4. Compare the managed device's target-specific database and retrieved FortiGate configuration with shared ADOM policy objects, identifying which layer diverges before selecting retrieve, import or install operations.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: An MSP is moving a customer from an old ADOM version to FortiOS 7.6 while maintaining uninterrupted policy control of other customer devices. Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path. Policy and object schema is tied to supported ADOM versions; a configuration that works on one firmware generation may be invalid on another, even with healthy FGFM. Verify the result with this test: In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation.

B.

Inspect the FortiManager policy import report, identify the specific missing device interface or unresolved address object, repair the corresponding ADOM database mapping and retry the import after a scoped backup. This addresses “Localize a FortiManager import failure to missing interface mappings or objects”, where the governing principle is: Policy import depends on translating device-specific configuration into centrally defined ADOM objects; a successful FGFM connection does not make absent central mappings or unsupported fields valid. The stated case instead calls for: Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path.

C.

The question is set in this situation: An MSP is moving a customer from an old ADOM version to FortiOS 7.6 while maintaining uninterrupted policy control of other customer devices. Use device-level revision comparison to restore an approved local configuration baseline when appropriate and separately validate that the current ADOM package remains correct before installing it. This addresses “Restore a managed FortiGate's device database without overwriting independent ADOM changes”, where the governing principle is: Device revisions are narrower than an ADOM-wide object revision; restoring a gateway configuration should not silently reverse unrelated centrally reviewed changes for other devices. The stated case instead calls for: Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path.

D.

The question is set in this situation: An MSP is moving a customer from an old ADOM version to FortiOS 7.6 while maintaining uninterrupted policy control of other customer devices. Compare the managed device's target-specific database and retrieved FortiGate configuration with shared ADOM policy objects, identifying which layer diverges before selecting retrieve, import or install operations. This addresses “Compare FortiManager device-level database against ADOM-level policy objects to locate drift”, where the governing principle is: Shared policy/object databases and device-specific configuration records serve different purposes; a status mismatch can arise from a local change, an uninstalled ADOM package or a missing interface map. The stated case instead calls for: Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path.

Question 747

An MSP is moving a customer from an old ADOM version to FortiOS 7.6 while maintaining uninterrupted policy control of other customer devices. The engineer proposes the following change: Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path. Which mechanism explains why it works?

  1. Shared policy/object databases and device-specific configuration records serve different purposes; a status mismatch can arise from a local change, an uninstalled ADOM package or a missing interface map.
  2. Policy import depends on translating device-specific configuration into centrally defined ADOM objects; a successful FGFM connection does not make absent central mappings or unsupported fields valid.
  3. Policy and object schema is tied to supported ADOM versions; a configuration that works on one firmware generation may be invalid on another, even with healthy FGFM.
  4. Device revisions are narrower than an ADOM-wide object revision; restoring a gateway configuration should not silently reverse unrelated centrally reviewed changes for other devices.

Answer & Explanations

Correct answer: C

A.

The question is set in this situation: An MSP is moving a customer from an old ADOM version to FortiOS 7.6 while maintaining uninterrupted policy control of other customer devices. Shared policy/object databases and device-specific configuration records serve different purposes; a status mismatch can arise from a local change, an uninstalled ADOM package or a missing interface map. That explains “Compare FortiManager device-level database against ADOM-level policy objects to locate drift”, not the mechanism behind the described change. The relevant principle is: Policy and object schema is tied to supported ADOM versions; a configuration that works on one firmware generation may be invalid on another, even with healthy FGFM.

B.

Policy import depends on translating device-specific configuration into centrally defined ADOM objects; a successful FGFM connection does not make absent central mappings or unsupported fields valid. That explains “Localize a FortiManager import failure to missing interface mappings or objects”, not the mechanism behind the described change. The relevant principle is: Policy and object schema is tied to supported ADOM versions; a configuration that works on one firmware generation may be invalid on another, even with healthy FGFM.

C.

The question is set in this situation: An MSP is moving a customer from an old ADOM version to FortiOS 7.6 while maintaining uninterrupted policy control of other customer devices. Policy and object schema is tied to supported ADOM versions; a configuration that works on one firmware generation may be invalid on another, even with healthy FGFM. The corresponding implementation is: Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path.

D.

The question is set in this situation: An MSP is moving a customer from an old ADOM version to FortiOS 7.6 while maintaining uninterrupted policy control of other customer devices. Device revisions are narrower than an ADOM-wide object revision; restoring a gateway configuration should not silently reverse unrelated centrally reviewed changes for other devices. That explains “Restore a managed FortiGate's device database without overwriting independent ADOM changes”, not the mechanism behind the described change. The relevant principle is: Policy and object schema is tied to supported ADOM versions; a configuration that works on one firmware generation may be invalid on another, even with healthy FGFM.

Question 748

An MSP is moving a customer from an old ADOM version to FortiOS 7.6 while maintaining uninterrupted policy control of other customer devices. After implementing this change—Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path.—which test most directly validates its intended outcome?

  1. Take a staged device revision, make a local interface setting error, restore the target configuration and confirm an unrelated ADOM service object and second firewall package remain unchanged.
  2. Create a harmless shared ADOM service edit and a separate local device change, inspect both database views, classify each drift and reconcile them independently through approved operations.
  3. Import a staging firewall with a deliberately missing interface alias, reproduce the failed import report, correct the mapping and verify the imported package represents existing rules without unwanted replacement.
  4. In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation.

Answer & Explanations

Correct answer: D

A.

The question is set in this situation: An MSP is moving a customer from an old ADOM version to FortiOS 7.6 while maintaining uninterrupted policy control of other customer devices. Take a staged device revision, make a local interface setting error, restore the target configuration and confirm an unrelated ADOM service object and second firewall package remain unchanged. That would help test “Restore a managed FortiGate's device database without overwriting independent ADOM changes”, not the outcome required in this scenario. The relevant acceptance check is: In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation.

B.

The question is set in this situation: An MSP is moving a customer from an old ADOM version to FortiOS 7.6 while maintaining uninterrupted policy control of other customer devices. Create a harmless shared ADOM service edit and a separate local device change, inspect both database views, classify each drift and reconcile them independently through approved operations. That would help test “Compare FortiManager device-level database against ADOM-level policy objects to locate drift”, not the outcome required in this scenario. The relevant acceptance check is: In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation.

C.

Import a staging firewall with a deliberately missing interface alias, reproduce the failed import report, correct the mapping and verify the imported package represents existing rules without unwanted replacement. That would help test “Localize a FortiManager import failure to missing interface mappings or objects”, not the outcome required in this scenario. The relevant acceptance check is: In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation.

D.

The question is set in this situation: An MSP is moving a customer from an old ADOM version to FortiOS 7.6 while maintaining uninterrupted policy control of other customer devices. In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation. This check is decisive because policy and object schema is tied to supported ADOM versions; a configuration that works on one firmware generation may be invalid on another, even with healthy FGFM.

Question 749

An MSP is moving a customer from an old ADOM version to FortiOS 7.6 while maintaining uninterrupted policy control of other customer devices. Which proposed shortcut most directly risks rejected policy and inconsistent enforcement across device firmware variants after version support is assumed and should therefore be rejected?

  1. Ignore a FortiOS compatibility warning and force a new unsupported policy feature to every branch simply because the latest FortiManager UI can display it.
  2. Unregister and factory-reset the FortiGate whenever an import wizard reports an unresolved interface reference, without examining or preserving the live firewall policy.
  3. Restore the entire FortiManager global database because one branch FortiGate's interface description is incorrect and assume no other tenants or policies can be affected.
  4. Fix an out-of-sync device by deleting the entire customer ADOM because central and device databases must always be byte-for-byte identical at all times.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: An MSP is moving a customer from an old ADOM version to FortiOS 7.6 while maintaining uninterrupted policy control of other customer devices. Ignore a FortiOS compatibility warning and force a new unsupported policy feature to every branch simply because the latest FortiManager UI can display it. The foreseeable failure is rejected policy and inconsistent enforcement across device firmware variants after version support is assumed. The safer response is: Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path.

B.

Unregister and factory-reset the FortiGate whenever an import wizard reports an unresolved interface reference, without examining or preserving the live firewall policy. That shortcut risks lost production configuration and repeated import failure after troubleshooting an object mapping as a hardware fault. Here the specific shortcut is: Ignore a FortiOS compatibility warning and force a new unsupported policy feature to every branch simply because the latest FortiManager UI can display it.

C.

The question is set in this situation: An MSP is moving a customer from an old ADOM version to FortiOS 7.6 while maintaining uninterrupted policy control of other customer devices. Restore the entire FortiManager global database because one branch FortiGate's interface description is incorrect and assume no other tenants or policies can be affected. That shortcut risks unrelated policy rollback and cross-tenant disruption after a device-only problem is treated as global management recovery. Here the specific shortcut is: Ignore a FortiOS compatibility warning and force a new unsupported policy feature to every branch simply because the latest FortiManager UI can display it.

D.

The question is set in this situation: An MSP is moving a customer from an old ADOM version to FortiOS 7.6 while maintaining uninterrupted policy control of other customer devices. Fix an out-of-sync device by deleting the entire customer ADOM because central and device databases must always be byte-for-byte identical at all times. That shortcut risks avoidable loss of shared policy state when device-specific drift is mistaken for corruption of the ADOM database. Here the specific shortcut is: Ignore a FortiOS compatibility warning and force a new unsupported policy feature to every branch simply because the latest FortiManager UI can display it.

Question 750

An MSP is moving a customer from an old ADOM version to FortiOS 7.6 while maintaining uninterrupted policy control of other customer devices. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Compare the managed device's target-specific database and retrieved FortiGate configuration with shared ADOM policy objects, identifying which layer diverges before selecting retrieve, import or install operations. Verify: Create a harmless shared ADOM service edit and a separate local device change, inspect both database views, classify each drift and reconcile them independently through approved operations.
  2. Implement: Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path. Verify: In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation.
  3. Implement: Use device-level revision comparison to restore an approved local configuration baseline when appropriate and separately validate that the current ADOM package remains correct before installing it. Verify: In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation.
  4. Implement: Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path. Verify: Take a staged device revision, make a local interface setting error, restore the target configuration and confirm an unrelated ADOM service object and second firewall package remain unchanged.

Answer & Explanations

Correct answer: B

A.

The question is set in this situation: An MSP is moving a customer from an old ADOM version to FortiOS 7.6 while maintaining uninterrupted policy control of other customer devices. This action/test pair addresses “Compare FortiManager device-level database against ADOM-level policy objects to locate drift”. Compare the managed device's target-specific database and retrieved FortiGate configuration with shared ADOM policy objects, identifying which layer diverges before selecting retrieve, import or install operations. Create a harmless shared ADOM service edit and a separate local device change, inspect both database views, classify each drift and reconcile them independently through approved operations. The case instead calls for: Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path.

B.

The question is set in this situation: An MSP is moving a customer from an old ADOM version to FortiOS 7.6 while maintaining uninterrupted policy control of other customer devices. Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path. Confirm it through this test: In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation. Policy and object schema is tied to supported ADOM versions; a configuration that works on one firmware generation may be invalid on another, even with healthy FGFM.

C.

The question is set in this situation: An MSP is moving a customer from an old ADOM version to FortiOS 7.6 while maintaining uninterrupted policy control of other customer devices. The test would be relevant: In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation. But the offered implementation—Use device-level revision comparison to restore an approved local configuration baseline when appropriate and separately validate that the current ADOM package remains correct before installing it.—addresses “Restore a managed FortiGate's device database without overwriting independent ADOM changes”. The action needed here is: Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path.

D.

The question is set in this situation: An MSP is moving a customer from an old ADOM version to FortiOS 7.6 while maintaining uninterrupted policy control of other customer devices. The action is applicable: Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path. But its proposed test—Take a staged device revision, make a local interface setting error, restore the target configuration and confirm an unrelated ADOM service object and second firewall package remain unchanged.—addresses “Restore a managed FortiGate's device database without overwriting independent ADOM changes”. This requirement is confirmed instead by: In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation.

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