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 74

Question 730

A university network team needs to identify whether a policy installation issue is rooted in a shared address object or one FortiGate's local configuration. 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: 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: 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.
  4. 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: 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.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: A university network team needs to identify whether a policy installation issue is rooted in a shared address object or one FortiGate's local configuration. 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. Confirm it through this test: 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. 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.

B.

The question is set in this situation: A university network team needs to identify whether a policy installation issue is rooted in a shared address object or one FortiGate's local configuration. This action/test pair addresses “Diagnose an ADOM version compatibility warning on a mixed-firmware FortiGate fleet”. 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. In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation. The case instead calls for: 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.

C.

The question is set in this situation: A university network team needs to identify whether a policy installation issue is rooted in a shared address object or one FortiGate's local configuration. The action is applicable: 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. But its proposed 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.—addresses “Distinguish local FortiGate edits from ADOM object changes in a configuration mismatch”. This requirement is confirmed instead by: 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.

D.

The question is set in this situation: A university network team needs to identify whether a policy installation issue is rooted in a shared address object or one FortiGate's local configuration. The test would be relevant: 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. But the offered implementation—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.—addresses “Distinguish local FortiGate edits from ADOM object changes in a configuration mismatch”. The action needed here is: 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.

Question 731

A national retailer sees conflicting firewall status reports after regional teams edited central policy and an emergency technician also modified one branch locally. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. 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.
  2. 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.
  3. 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.
  4. Collect supported FortiManager process status, system events and narrowly scoped debug output for the affected operation, correlate timestamps and stop temporary diagnostics after identifying a specific service or connectivity issue.

Answer & Explanations

Correct answer: B

A.

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

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

C.

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. This addresses “Diagnose an ADOM version compatibility warning on a mixed-firmware FortiGate fleet”, where the governing 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. The stated 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.

D.

Collect supported FortiManager process status, system events and narrowly scoped debug output for the affected operation, correlate timestamps and stop temporary diagnostics after identifying a specific service or connectivity issue. This addresses “Use FortiManager process status and debug evidence for a persistent management fault”, where the governing principle is: A generic GUI error can originate from API services, device management processes or database handling; targeted debug evidence is more reliable than resetting the entire environment without identifying the failing component. The stated 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.

Question 732

A national retailer sees conflicting firewall status reports after regional teams edited central policy and an emergency technician also modified one branch locally. The engineer proposes the following change: 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. Which mechanism explains why it works?

  1. 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.
  2. A generic GUI error can originate from API services, device management processes or database handling; targeted debug evidence is more reliable than resetting the entire environment without identifying the failing component.
  3. 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.
  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.

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. That explains “Diagnose an ADOM version compatibility warning on a mixed-firmware FortiGate fleet”, not the mechanism behind the described change. The relevant principle is: 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.

B.

A generic GUI error can originate from API services, device management processes or database handling; targeted debug evidence is more reliable than resetting the entire environment without identifying the failing component. That explains “Use FortiManager process status and debug evidence for a persistent management fault”, not the mechanism behind the described change. The relevant principle is: 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.

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

D.

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

Question 733

A national retailer sees conflicting firewall status reports after regional teams edited central policy and an emergency technician also modified one branch locally. After implementing this change—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.—which test most directly validates its intended outcome?

  1. 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.
  2. 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.
  3. 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. Reproduce a benign stalled policy task on a staging manager, inspect relevant process status and logs, isolate the cause and confirm a targeted correction restores the intended action.

Answer & Explanations

Correct answer: A

A.

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

B.

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

C.

In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation. That would help test “Diagnose an ADOM version compatibility warning on a mixed-firmware FortiGate fleet”, not the outcome required in this scenario. The relevant acceptance check is: 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.

Reproduce a benign stalled policy task on a staging manager, inspect relevant process status and logs, isolate the cause and confirm a targeted correction restores the intended action. That would help test “Use FortiManager process status and debug evidence for a persistent management fault”, not the outcome required in this scenario. The relevant acceptance check is: 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.

Question 734

A national retailer sees conflicting firewall status reports after regional teams edited central policy and an emergency technician also modified one branch locally. Which proposed shortcut most directly risks unsafe acceptance of unauthorized local settings after status indicators are resolved without provenance and should therefore be rejected?

  1. 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.
  2. Ignore a FortiOS compatibility warning and force a new unsupported policy feature to every branch simply because the latest FortiManager UI can display it.
  3. Enable maximum debugging indefinitely on all central processes and reboot every gateway on the first error message without preserving or analyzing the relevant FortiManager logs.
  4. Automatically retrieve every local FortiGate change and approve it as central policy whenever a configuration mismatch appears without reviewing whether the change was authorized.

Answer & Explanations

Correct answer: D

A.

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: Automatically retrieve every local FortiGate change and approve it as central policy whenever a configuration mismatch appears without reviewing whether the change was authorized.

B.

Ignore a FortiOS compatibility warning and force a new unsupported policy feature to every branch simply because the latest FortiManager UI can display it. That shortcut risks rejected policy and inconsistent enforcement across device firmware variants after version support is assumed. Here the specific shortcut is: Automatically retrieve every local FortiGate change and approve it as central policy whenever a configuration mismatch appears without reviewing whether the change was authorized.

C.

Enable maximum debugging indefinitely on all central processes and reboot every gateway on the first error message without preserving or analyzing the relevant FortiManager logs. That shortcut risks lost diagnostic evidence and collateral disruption after uncontrolled debugging and unrelated restarts. Here the specific shortcut is: Automatically retrieve every local FortiGate change and approve it as central policy whenever a configuration mismatch appears without reviewing whether the change was authorized.

D.

Automatically retrieve every local FortiGate change and approve it as central policy whenever a configuration mismatch appears without reviewing whether the change was authorized. The foreseeable failure is unsafe acceptance of unauthorized local settings after status indicators are resolved without provenance. The safer response 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 735

A national retailer sees conflicting firewall status reports after regional teams edited central policy and an emergency technician also modified one branch locally. 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: 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.
  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: 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.
  4. 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.

Answer & Explanations

Correct answer: B

A.

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.

B.

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.

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.

D.

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.

Question 736

A healthcare organization needs to separate approved device-level maintenance from centrally authored but not-yet-installed address changes. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. 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.
  2. Read the FortiManager task and installation logs to determine whether an object or configuration copy into the central device database failed versus a later push to the FortiGate, then repair the correct stage.
  3. 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.
  4. 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.

Answer & Explanations

Correct answer: C

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

Read the FortiManager task and installation logs to determine whether an object or configuration copy into the central device database failed versus a later push to the FortiGate, then repair the correct stage. This addresses “Distinguish a FortiManager copy failure from an installation failure”, where the governing principle is: FortiManager builds desired configuration in multiple management and target database steps; a failure before device installation should not be diagnosed as a FortiGate packet-forwarding problem without evidence. The stated 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.

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

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. 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. This addresses “Diagnose an ADOM version compatibility warning on a mixed-firmware FortiGate fleet”, where the governing 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. The stated 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.

Question 737

A healthcare organization needs to separate approved device-level maintenance from centrally authored but not-yet-installed address changes. The engineer proposes the following change: 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. Which mechanism explains why it works?

  1. FortiManager builds desired configuration in multiple management and target database steps; a failure before device installation should not be diagnosed as a FortiGate packet-forwarding problem without evidence.
  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. 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. 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.

Answer & Explanations

Correct answer: D

A.

FortiManager builds desired configuration in multiple management and target database steps; a failure before device installation should not be diagnosed as a FortiGate packet-forwarding problem without evidence. That explains “Distinguish a FortiManager copy failure from an installation failure”, not the mechanism behind the described change. The relevant principle is: 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.

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. 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: 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. 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. That explains “Diagnose an ADOM version compatibility warning on a mixed-firmware FortiGate fleet”, not the mechanism behind the described change. The relevant principle is: 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.

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

A healthcare organization needs to separate approved device-level maintenance from centrally authored but not-yet-installed address changes. After implementing this change—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.—which test most directly validates its intended outcome?

  1. 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.
  2. 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. 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.
  4. Deliberately create an invalid referenced object in a staging policy, compare the reported copy and installation task stages, correct it and verify a clean package build and later device install.

Answer & Explanations

Correct answer: A

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

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. In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation. That would help test “Diagnose an ADOM version compatibility warning on a mixed-firmware FortiGate fleet”, not the outcome required in this scenario. The relevant acceptance check is: 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.

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

Deliberately create an invalid referenced object in a staging policy, compare the reported copy and installation task stages, correct it and verify a clean package build and later device install. That would help test “Distinguish a FortiManager copy failure from an installation failure”, not the outcome required in this scenario. The relevant acceptance check is: 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.

Question 739

A healthcare organization needs to separate approved device-level maintenance from centrally authored but not-yet-installed address changes. Which proposed shortcut most directly risks unsafe acceptance of unauthorized local settings after status indicators are resolved without provenance and should therefore be rejected?

  1. Reboot all branch FortiGates after every FortiManager copy-failed message because every error must be caused by a network timeout during firewall installation.
  2. Ignore a FortiOS compatibility warning and force a new unsupported policy feature to every branch simply because the latest FortiManager UI can display it.
  3. Automatically retrieve every local FortiGate change and approve it as central policy whenever a configuration mismatch appears without reviewing whether the change was authorized.
  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.

Reboot all branch FortiGates after every FortiManager copy-failed message because every error must be caused by a network timeout during firewall installation. That shortcut risks unnecessary branch downtime and persistent policy build errors after misclassifying an internal copy failure. Here the specific shortcut is: Automatically retrieve every local FortiGate change and approve it as central policy whenever a configuration mismatch appears without reviewing whether the change was authorized.

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. Ignore a FortiOS compatibility warning and force a new unsupported policy feature to every branch simply because the latest FortiManager UI can display it. That shortcut risks rejected policy and inconsistent enforcement across device firmware variants after version support is assumed. Here the specific shortcut is: Automatically retrieve every local FortiGate change and approve it as central policy whenever a configuration mismatch appears without reviewing whether the change was authorized.

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. Automatically retrieve every local FortiGate change and approve it as central policy whenever a configuration mismatch appears without reviewing whether the change was authorized. The foreseeable failure is unsafe acceptance of unauthorized local settings after status indicators are resolved without provenance. The safer response 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.

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. 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: Automatically retrieve every local FortiGate change and approve it as central policy whenever a configuration mismatch appears without reviewing whether the change was authorized.

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.

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