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 76

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.

Question 751

A regional hospital wants to roll back a failed device maintenance setting without removing a separately approved corporate security rule. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. Inspect supported FortiManager system resource utilization, current processes and task queue during slow policy edits, identify the actual bottleneck, and plan a targeted approved remediation rather than rebooting unrelated gateways.
  2. 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.
  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. 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.

Answer & Explanations

Correct answer: C

A.

Inspect supported FortiManager system resource utilization, current processes and task queue during slow policy edits, identify the actual bottleneck, and plan a targeted approved remediation rather than rebooting unrelated gateways. This addresses “Use FortiManager CPU and memory diagnostics before restarting management services”, where the governing principle is: High manager CPU or memory can delay policy compilation and administrator sessions while FortiGate enforcement remains operational; measuring the management host prevents diagnosing the wrong system. The stated case instead calls for: 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.

B.

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

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

D.

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. This addresses “Distinguish local FortiGate edits from ADOM object changes in a configuration mismatch”, where the governing 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. The stated case instead calls for: 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.

Question 752

A regional hospital wants to roll back a failed device maintenance setting without removing a separately approved corporate security rule. The engineer proposes the following change: 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. Which mechanism explains why it works?

  1. 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.
  2. High manager CPU or memory can delay policy compilation and administrator sessions while FortiGate enforcement remains operational; measuring the management host prevents diagnosing the wrong system.
  3. 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.
  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: D

A.

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. That explains “Distinguish local FortiGate edits from ADOM object changes in a configuration mismatch”, not the mechanism behind the described change. The relevant 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.

B.

High manager CPU or memory can delay policy compilation and administrator sessions while FortiGate enforcement remains operational; measuring the management host prevents diagnosing the wrong system. That explains “Use FortiManager CPU and memory diagnostics before restarting management services”, not the mechanism behind the described change. The relevant 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.

C.

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

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

Question 753

A regional hospital wants to roll back a failed device maintenance setting without removing a separately approved corporate security rule. After implementing this change—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.—which test most directly validates its intended outcome?

  1. 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. Generate a safe load on a disposable FortiManager, monitor process and resource counters during a policy task, and show service performance improves after correcting the identified pressure.
  3. 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. 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: D

A.

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

B.

Generate a safe load on a disposable FortiManager, monitor process and resource counters during a policy task, and show service performance improves after correcting the identified pressure. That would help test “Use FortiManager CPU and memory diagnostics before restarting management services”, not the outcome required in this scenario. The relevant acceptance check is: 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.

C.

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. That would help test “Distinguish local FortiGate edits from ADOM object changes in a configuration mismatch”, not the outcome required in this scenario. The relevant acceptance check is: 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.

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

Question 754

A regional hospital wants to roll back a failed device maintenance setting without removing a separately approved corporate security rule. Which proposed shortcut most directly risks unrelated policy rollback and cross-tenant disruption after a device-only problem is treated as global management recovery and should therefore be rejected?

  1. Reboot all customer FortiGates because FortiManager's web interface responds slowly, without checking whether the manager has exhausted CPU or memory.
  2. Automatically retrieve every local FortiGate change and approve it as central policy whenever a configuration mismatch appears without reviewing whether the change was authorized.
  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: C

A.

Reboot all customer FortiGates because FortiManager's web interface responds slowly, without checking whether the manager has exhausted CPU or memory. That shortcut risks widespread customer disruption when central management performance problems trigger unrelated firewall restarts. Here the specific shortcut is: 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.

B.

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

C.

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. The foreseeable failure is unrelated policy rollback and cross-tenant disruption after a device-only problem is treated as global management recovery. The safer response is: 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.

D.

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

Question 755

A regional hospital wants to roll back a failed device maintenance setting without removing a separately approved corporate security rule. Which combined implementation and verification plan is the best match for this workload?

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

A.

This action/test pair addresses “Distinguish local FortiGate edits from ADOM object changes in a configuration mismatch”. 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. 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. The case instead calls for: 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.

B.

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

C.

The test would be relevant: 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. But the offered implementation—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.—addresses “Compare FortiManager device-level database against ADOM-level policy objects to locate drift”. The action needed here is: 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.

D.

The action is applicable: 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. But its proposed 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.—addresses “Compare FortiManager device-level database against ADOM-level policy objects to locate drift”. This requirement is confirmed instead by: 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.

Question 756

A university's branch firewall has a local DNS misconfiguration and the central team needs to restore it without resetting the ADOM's recent shared object 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. 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. When both management and managed FortiGate systems reside behind NAT, explicitly verify supported central management addresses, session direction, translated routing and firewall allowances from each side before declaring the design operational.
  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: A university's branch firewall has a local DNS misconfiguration and the central team needs to restore it without resetting the ADOM's recent shared object 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. 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. Verify the result with this 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.

B.

The question is set in this situation: A university's branch firewall has a local DNS misconfiguration and the central team needs to restore it without resetting the ADOM's recent shared object 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. This addresses “Distinguish local FortiGate edits from ADOM object changes in a configuration mismatch”, where the governing 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. The stated case instead calls for: 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.

C.

When both management and managed FortiGate systems reside behind NAT, explicitly verify supported central management addresses, session direction, translated routing and firewall allowances from each side before declaring the design operational. This addresses “Plan FortiManager and FortiGate both behind separate NAT boundaries”, where the governing principle is: Two private address realms can each work locally while no valid end-to-end FGFM session exists; consistent external reachability and session initiation are separate from local ping success. The stated case instead calls for: 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.

D.

The question is set in this situation: A university's branch firewall has a local DNS misconfiguration and the central team needs to restore it without resetting the ADOM's recent shared object changes. 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: 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.

Question 757

A university's branch firewall has a local DNS misconfiguration and the central team needs to restore it without resetting the ADOM's recent shared object changes. The engineer proposes the following change: 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. 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. 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.
  3. 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.
  4. Two private address realms can each work locally while no valid end-to-end FGFM session exists; consistent external reachability and session initiation are separate from local ping success.

Answer & Explanations

Correct answer: C

A.

The question is set in this situation: A university's branch firewall has a local DNS misconfiguration and the central team needs to restore it without resetting the ADOM's recent shared object changes. 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: 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.

B.

The question is set in this situation: A university's branch firewall has a local DNS misconfiguration and the central team needs to restore it without resetting the ADOM's recent shared object 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. That explains “Distinguish local FortiGate edits from ADOM object changes in a configuration mismatch”, not the mechanism behind the described change. The relevant 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.

C.

The question is set in this situation: A university's branch firewall has a local DNS misconfiguration and the central team needs to restore it without resetting the ADOM's recent shared object 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. The corresponding implementation is: 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.

D.

Two private address realms can each work locally while no valid end-to-end FGFM session exists; consistent external reachability and session initiation are separate from local ping success. That explains “Plan FortiManager and FortiGate both behind separate NAT boundaries”, not the mechanism behind the described change. The relevant 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.

Question 758

A university's branch firewall has a local DNS misconfiguration and the central team needs to restore it without resetting the ADOM's recent shared object changes. After implementing this change—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.—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. Build a safe lab with two independent NAT devices, establish the intended FGFM connection, inspect translated flows and show both registration and an authorized policy installation succeed.
  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: D

A.

The question is set in this situation: A university's branch firewall has a local DNS misconfiguration and the central team needs to restore it without resetting the ADOM's recent shared object 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. That would help test “Distinguish local FortiGate edits from ADOM object changes in a configuration mismatch”, not the outcome required in this scenario. The relevant acceptance check is: 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.

B.

Build a safe lab with two independent NAT devices, establish the intended FGFM connection, inspect translated flows and show both registration and an authorized policy installation succeed. That would help test “Plan FortiManager and FortiGate both behind separate NAT boundaries”, not the outcome required in this scenario. The relevant acceptance check is: 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.

C.

The question is set in this situation: A university's branch firewall has a local DNS misconfiguration and the central team needs to restore it without resetting the ADOM's recent shared object changes. 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: 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.

D.

The question is set in this situation: A university's branch firewall has a local DNS misconfiguration and the central team needs to restore it without resetting the ADOM's recent shared object 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. This check is decisive because 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.

Question 759

A university's branch firewall has a local DNS misconfiguration and the central team needs to restore it without resetting the ADOM's recent shared object changes. Which proposed shortcut most directly risks unrelated policy rollback and cross-tenant disruption after a device-only problem is treated as global management recovery 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. Assume the identical private IP on the FortiManager and FortiGate sides guarantees mutual management through separate internet connections without routing or NAT configuration.
  3. 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.
  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: A

A.

The question is set in this situation: A university's branch firewall has a local DNS misconfiguration and the central team needs to restore it without resetting the ADOM's recent shared object 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. The foreseeable failure is unrelated policy rollback and cross-tenant disruption after a device-only problem is treated as global management recovery. The safer response is: 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.

B.

Assume the identical private IP on the FortiManager and FortiGate sides guarantees mutual management through separate internet connections without routing or NAT configuration. That shortcut risks unrecoverable central connection failures caused by overlapping private addresses and unverified double-NAT design. Here the specific shortcut is: 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.

C.

The question is set in this situation: A university's branch firewall has a local DNS misconfiguration and the central team needs to restore it without resetting the ADOM's recent shared object changes. 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: 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.

D.

The question is set in this situation: A university's branch firewall has a local DNS misconfiguration and the central team needs to restore it without resetting the ADOM's recent shared object 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. That shortcut risks unsafe acceptance of unauthorized local settings after status indicators are resolved without provenance. Here the specific shortcut is: 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.

Question 760

A university's branch firewall has a local DNS misconfiguration and the central team needs to restore it without resetting the ADOM's recent shared object changes. 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: 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: 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.
  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: 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: 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: 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: B

A.

The question is set in this situation: A university's branch firewall has a local DNS misconfiguration and the central team needs to restore it without resetting the ADOM's recent shared object changes. The test would be relevant: 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. But the offered implementation—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.—addresses “Compare FortiManager device-level database against ADOM-level policy objects to locate drift”. The action needed here is: 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.

B.

The question is set in this situation: A university's branch firewall has a local DNS misconfiguration and the central team needs to restore it without resetting the ADOM's recent shared object 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. Confirm it through this 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. 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.

C.

The question is set in this situation: A university's branch firewall has a local DNS misconfiguration and the central team needs to restore it without resetting the ADOM's recent shared object changes. This action/test pair addresses “Distinguish local FortiGate edits from ADOM object changes in a configuration mismatch”. 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. 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. The case instead calls for: 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.

D.

The question is set in this situation: A university's branch firewall has a local DNS misconfiguration and the central team needs to restore it without resetting the ADOM's recent shared object changes. The action is applicable: 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. But its proposed 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.—addresses “Compare FortiManager device-level database against ADOM-level policy objects to locate drift”. This requirement is confirmed instead by: 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.

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