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 73

Question 720

A university recovered its central management VM from a hypervisor outage and requires evidence that object and device revision histories remain consistent. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Use supported FortiManager filesystem and database status diagnostics after storage or power faults, verify backups and snapshots, and perform documented recovery before trusting policy histories or large-scale install operations. Verify: In a nonproduction failure rehearsal compare central ADOM revision availability, filesystem checks and backup integrity, restore a known configuration if required and perform one harmless device install.
  2. Implement: Inspect the FortiManager policy import report, identify the specific missing device interface or unresolved address object, repair the corresponding ADOM database mapping and retry the import after a scoped backup. Verify: In a nonproduction failure rehearsal compare central ADOM revision availability, filesystem checks and backup integrity, restore a known configuration if required and perform one harmless device install.
  3. Implement: 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. Verify: 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.
  4. Implement: Use supported FortiManager filesystem and database status diagnostics after storage or power faults, verify backups and snapshots, and perform documented recovery before trusting policy histories or large-scale install operations. Verify: Import a staging firewall with a deliberately missing interface alias, reproduce the failed import report, correct the mapping and verify the imported package represents existing rules without unwanted replacement.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: A university recovered its central management VM from a hypervisor outage and requires evidence that object and device revision histories remain consistent. Use supported FortiManager filesystem and database status diagnostics after storage or power faults, verify backups and snapshots, and perform documented recovery before trusting policy histories or large-scale install operations. Confirm it through this test: In a nonproduction failure rehearsal compare central ADOM revision availability, filesystem checks and backup integrity, restore a known configuration if required and perform one harmless device install. A central management database can be inconsistent while registered FortiGates continue enforcing old policies; a healthy firewall data plane therefore does not demonstrate the manager's database is safe to use.

B.

The test would be relevant: In a nonproduction failure rehearsal compare central ADOM revision availability, filesystem checks and backup integrity, restore a known configuration if required and perform one harmless device install. But the offered implementation—Inspect the FortiManager policy import report, identify the specific missing device interface or unresolved address object, repair the corresponding ADOM database mapping and retry the import after a scoped backup.—addresses “Localize a FortiManager import failure to missing interface mappings or objects”. The action needed here is: Use supported FortiManager filesystem and database status diagnostics after storage or power faults, verify backups and snapshots, and perform documented recovery before trusting policy histories or large-scale install operations.

C.

This action/test pair addresses “Distinguish a FortiManager copy failure from an installation failure”. 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. 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. The case instead calls for: Use supported FortiManager filesystem and database status diagnostics after storage or power faults, verify backups and snapshots, and perform documented recovery before trusting policy histories or large-scale install operations.

D.

The action is applicable: Use supported FortiManager filesystem and database status diagnostics after storage or power faults, verify backups and snapshots, and perform documented recovery before trusting policy histories or large-scale install operations. But its proposed test—Import a staging firewall with a deliberately missing interface alias, reproduce the failed import report, correct the mapping and verify the imported package represents existing rules without unwanted replacement.—addresses “Localize a FortiManager import failure to missing interface mappings or objects”. This requirement is confirmed instead by: In a nonproduction failure rehearsal compare central ADOM revision availability, filesystem checks and backup integrity, restore a known configuration if required and perform one harmless device install.

Question 721

A bank's FortiManager shows one branch firewall out of sync after a local route fix while other sites share the same central policy package. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. When FortiManager is behind an upstream NAT device, plan the correct reachable management endpoint and supported FGFM routing and firewall rules, then test registration and policy delivery from an actual external FortiGate.
  2. Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path.
  3. 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.
  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.

When FortiManager is behind an upstream NAT device, plan the correct reachable management endpoint and supported FGFM routing and firewall rules, then test registration and policy delivery from an actual external FortiGate. This addresses “Diagnose FortiManager behind-NAT connectivity for managed remote FortiGates”, where the governing principle is: A private management IP may respond locally while a remote gateway cannot establish FGFM to the translated address; an HTTPS port-forward test alone does not prove management control traffic and identity are correct. The stated 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.

B.

Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path. 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: 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.

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

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

A bank's FortiManager shows one branch firewall out of sync after a local route fix while other sites share the same central policy package. The engineer proposes the following change: 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. 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. 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.
  3. A private management IP may respond locally while a remote gateway cannot establish FGFM to the translated address; an HTTPS port-forward test alone does not prove management control traffic and identity are correct.
  4. Policy and object schema is tied to supported ADOM versions; a configuration that works on one firmware generation may be invalid on another, even with healthy FGFM.

Answer & Explanations

Correct answer: B

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

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

C.

A private management IP may respond locally while a remote gateway cannot establish FGFM to the translated address; an HTTPS port-forward test alone does not prove management control traffic and identity are correct. That explains “Diagnose FortiManager behind-NAT connectivity for managed remote FortiGates”, not the mechanism behind the described change. The relevant 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.

D.

Policy and object schema is tied to supported ADOM versions; a configuration that works on one firmware generation may be invalid on another, even with healthy FGFM. 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: 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.

Question 723

A bank's FortiManager shows one branch firewall out of sync after a local route fix while other sites share the same central policy package. After implementing this change—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.—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. 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. From a branch lab firewall test the intended external manager address, inspect upstream NAT and FGFM session state, authorize registration and complete a harmless policy install.
  4. In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation.

Answer & Explanations

Correct answer: A

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

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

C.

From a branch lab firewall test the intended external manager address, inspect upstream NAT and FGFM session state, authorize registration and complete a harmless policy install. That would help test “Diagnose FortiManager behind-NAT connectivity for managed remote FortiGates”, not the outcome required in this scenario. The relevant acceptance check is: 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.

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

Question 724

A bank's FortiManager shows one branch firewall out of sync after a local route fix while other sites share the same central policy package. Which proposed shortcut most directly risks avoidable loss of shared policy state when device-specific drift is mistaken for corruption of the ADOM database and should therefore be rejected?

  1. Ping the FortiManager from its own private subnet and declare all remote FortiGates correctly managed through the public NAT path without any branch-side FGFM test.
  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. Ignore a FortiOS compatibility warning and force a new unsupported policy feature to every branch simply because the latest FortiManager UI can display it.
  4. 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: D

A.

Ping the FortiManager from its own private subnet and declare all remote FortiGates correctly managed through the public NAT path without any branch-side FGFM test. That shortcut risks unreachable central policy control after an address translation hides the actual management server from remote branches. Here the specific shortcut is: 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.

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

C.

Ignore a FortiOS compatibility warning and force a new unsupported policy feature to every branch simply because the latest FortiManager UI can display it. That shortcut risks rejected policy and inconsistent enforcement across device firmware variants after version support is assumed. Here the specific shortcut is: 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.

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. The foreseeable failure is avoidable loss of shared policy state when device-specific drift is mistaken for corruption of the ADOM database. The safer response 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 725

A bank's FortiManager shows one branch firewall out of sync after a local route fix while other sites share the same central policy package. 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: 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: 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.
  3. Implement: Compare the managed device's target-specific database and retrieved FortiGate configuration with shared ADOM policy objects, identifying which layer diverges before selecting retrieve, import or install operations. Verify: Create a harmless shared ADOM service edit and a separate local device change, inspect both database views, classify each drift and reconcile them independently through approved operations.
  4. Implement: 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.

Answer & Explanations

Correct answer: C

A.

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.

B.

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.

C.

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.

D.

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.

Question 726

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 Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. 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.
  2. Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path.
  3. When FortiManager experiences a failed reload or abrupt power loss, review documented system and database integrity checks, confirm usable configuration backups and identify affected services before restarting or restoring management state.
  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: 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. 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. Verify the result with 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.

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

When FortiManager experiences a failed reload or abrupt power loss, review documented system and database integrity checks, confirm usable configuration backups and identify affected services before restarting or restoring management state. This addresses “Investigate a failed reload and central database integrity after an unclean shutdown”, where the governing principle is: Database and filesystem integrity problems differ from individual device connectivity faults; repeatedly pushing policy from a damaged manager can produce inconsistent state rather than recover the underlying management records. The stated 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.

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

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 engineer proposes the following change: 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. Which mechanism explains why it works?

  1. Database and filesystem integrity problems differ from individual device connectivity faults; repeatedly pushing policy from a damaged manager can produce inconsistent state rather than recover the underlying management records.
  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. 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. 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.

Answer & Explanations

Correct answer: D

A.

Database and filesystem integrity problems differ from individual device connectivity faults; repeatedly pushing policy from a damaged manager can produce inconsistent state rather than recover the underlying management records. That explains “Investigate a failed reload and central database integrity after an unclean shutdown”, not the mechanism behind the described change. The relevant 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.

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

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

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

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. After implementing this change—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.—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. Create a harmless shared ADOM service edit and a separate local device change, inspect both database views, classify each drift and reconcile them independently through approved operations.
  3. After a controlled laboratory unclean shutdown inspect safe supported status checks, service logs and revision availability, restore from a verified backup if needed and validate a test ADOM package.
  4. In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation.

Answer & Explanations

Correct answer: B

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

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

C.

After a controlled laboratory unclean shutdown inspect safe supported status checks, service logs and revision availability, restore from a verified backup if needed and validate a test ADOM package. That would help test “Investigate a failed reload and central database integrity after an unclean shutdown”, not the outcome required in this scenario. The relevant acceptance check is: 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. 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: 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.

Question 729

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 proposed shortcut most directly risks avoidable loss of shared policy state when device-specific drift is mistaken for corruption of the ADOM database and should therefore be rejected?

  1. Dismiss a FortiManager database reload failure and repeatedly install the same policy to production gateways without inspecting management storage or backup integrity.
  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. 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: D

A.

Dismiss a FortiManager database reload failure and repeatedly install the same policy to production gateways without inspecting management storage or backup integrity. That shortcut risks wider management database corruption and inconsistent installations after ignoring an underlying reload or filesystem error. Here the specific shortcut is: 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.

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

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

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. 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. The foreseeable failure is avoidable loss of shared policy state when device-specific drift is mistaken for corruption of the ADOM database. The safer response 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 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.

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