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 69

Question 680

An MSP onboards a customer gateway with many local service objects and must repair only the import translation failures rather than erase the running rules. Which combined implementation and verification plan is the best match for this workload?

  1. 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: 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.
  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: 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.
  3. 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: Import a staging firewall with a deliberately missing interface alias, reproduce the failed import report, correct the mapping and verify the imported package represents existing rules without unwanted replacement.
  4. Implement: 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. Verify: 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.

Answer & Explanations

Correct answer: C

A.

The test would be relevant: 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. But the offered implementation—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.—addresses “Distinguish a FortiManager copy failure from an installation failure”. The action needed here is: 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.

B.

The action is applicable: 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. But its proposed test—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.—addresses “Distinguish a FortiManager copy failure from an installation failure”. This requirement is confirmed instead by: 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.

C.

The question is set in this situation: An MSP onboards a customer gateway with many local service objects and must repair only the import translation failures rather than erase the running rules. 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. Confirm it through this 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. Policy import depends on translating device-specific configuration into centrally defined ADOM objects; a successful FGFM connection does not make absent central mappings or unsupported fields valid.

D.

This action/test pair addresses “Investigate a failed reload and central database integrity after an unclean shutdown”. 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. 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. The case instead calls for: 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.

Question 681

A financial organization sees a FortiManager policy install task fail before its central log shows any target device execution. 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. Read the FortiManager task and installation logs to determine whether an object or configuration copy into the central device database failed versus a later push to the FortiGate, then repair the correct stage.
  3. Inspect the FortiManager 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.
  4. 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.

Answer & Explanations

Correct answer: B

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

B.

Read the FortiManager task and installation logs to determine whether an object or configuration copy into the central device database failed versus a later push to the FortiGate, then repair the correct stage. FortiManager builds desired configuration in multiple management and target database steps; a failure before device installation should not be diagnosed as a FortiGate packet-forwarding problem without evidence. Verify the result with this test: 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.

C.

Inspect the FortiManager policy import report, identify the specific missing device interface or unresolved address object, repair the corresponding ADOM database mapping and retry the import after a scoped backup. This addresses “Localize a FortiManager import failure to missing interface mappings or objects”, where the governing principle is: Policy import depends on translating device-specific configuration into centrally defined ADOM objects; a successful FGFM connection does not make absent central mappings or unsupported fields valid. The stated case instead calls for: 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.

D.

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

Question 682

A financial organization sees a FortiManager policy install task fail before its central log shows any target device execution. The engineer proposes the following change: 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. Which mechanism explains why it works?

  1. 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.
  2. 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.
  3. Policy import depends on translating device-specific configuration into centrally defined ADOM objects; a successful FGFM connection does not make absent central mappings or unsupported fields valid.
  4. FortiManager builds desired configuration in multiple management and target database steps; a failure before device installation should not be diagnosed as a FortiGate packet-forwarding problem without evidence.

Answer & Explanations

Correct answer: D

A.

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

B.

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

C.

Policy import depends on translating device-specific configuration into centrally defined ADOM objects; a successful FGFM connection does not make absent central mappings or unsupported fields valid. That explains “Localize a FortiManager import failure to missing interface mappings or objects”, not the mechanism behind the described change. The relevant principle is: FortiManager builds desired configuration in multiple management and target database steps; a failure before device installation should not be diagnosed as a FortiGate packet-forwarding problem without evidence.

D.

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

Question 683

A financial organization sees a FortiManager policy install task fail before its central log shows any target device execution. After implementing this change—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.—which test most directly validates its intended outcome?

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

A.

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

B.

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

C.

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

D.

Import a staging firewall with a deliberately missing interface alias, reproduce the failed import report, correct the mapping and verify the imported package represents existing rules without unwanted replacement. That would help test “Localize a FortiManager import failure to missing interface mappings or objects”, not the outcome required in this scenario. The relevant acceptance check is: 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.

Question 684

A financial organization sees a FortiManager policy install task fail before its central log shows any target device execution. Which proposed shortcut most directly risks unnecessary branch downtime and persistent policy build errors after misclassifying an internal copy failure and should therefore be rejected?

  1. Reboot all branch FortiGates after every FortiManager copy-failed message because every error must be caused by a network timeout during firewall installation.
  2. Unregister and factory-reset the FortiGate whenever an import wizard reports an unresolved interface reference, without examining or preserving the live firewall policy.
  3. Dismiss a FortiManager database reload failure and repeatedly install the same policy to production gateways without inspecting management storage or backup integrity.
  4. 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.

Answer & Explanations

Correct answer: A

A.

Reboot all branch FortiGates after every FortiManager copy-failed message because every error must be caused by a network timeout during firewall installation. The foreseeable failure is unnecessary branch downtime and persistent policy build errors after misclassifying an internal copy failure. The safer response is: 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.

B.

Unregister and factory-reset the FortiGate whenever an import wizard reports an unresolved interface reference, without examining or preserving the live firewall policy. That shortcut risks lost production configuration and repeated import failure after troubleshooting an object mapping as a hardware fault. Here the specific shortcut is: Reboot all branch FortiGates after every FortiManager copy-failed message because every error must be caused by a network timeout during firewall installation.

C.

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: Reboot all branch FortiGates after every FortiManager copy-failed message because every error must be caused by a network timeout during firewall installation.

D.

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: Reboot all branch FortiGates after every FortiManager copy-failed message because every error must be caused by a network timeout during firewall installation.

Question 685

A financial organization sees a FortiManager policy install task fail before its central log shows any target device execution. Which combined implementation and verification plan is the best match for this workload?

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

A.

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

B.

Read the FortiManager task and installation logs to determine whether an object or configuration copy into the central device database failed versus a later push to the FortiGate, then repair the correct stage. Confirm it through this test: 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. FortiManager builds desired configuration in multiple management and target database steps; a failure before device installation should not be diagnosed as a FortiGate packet-forwarding problem without evidence.

C.

This action/test pair addresses “Investigate a failed reload and central database integrity after an unclean shutdown”. 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. 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. The case instead calls for: 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.

D.

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

Question 686

A university's change ticket needs to determine whether a failed rule update originated in the ADOM object database or in FortiGate communication. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. 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.
  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. 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.
  4. 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.

Answer & Explanations

Correct answer: C

A.

The question is set in this situation: A university's change ticket needs to determine whether a failed rule update originated in the ADOM object database or in FortiGate communication. Inspect the FortiManager policy import report, identify the specific missing device interface or unresolved address object, repair the corresponding ADOM database mapping and retry the import after a scoped backup. This addresses “Localize a FortiManager import failure to missing interface mappings or objects”, where the governing principle is: Policy import depends on translating device-specific configuration into centrally defined ADOM objects; a successful FGFM connection does not make absent central mappings or unsupported fields valid. The stated case instead calls for: 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.

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

C.

The question is set in this situation: A university's change ticket needs to determine whether a failed rule update originated in the ADOM object database or in FortiGate communication. 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. FortiManager builds desired configuration in multiple management and target database steps; a failure before device installation should not be diagnosed as a FortiGate packet-forwarding problem without evidence. Verify the result with this test: 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.

D.

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. This addresses “Confirm FortiManager database recovery after power failure before rebuilding policies”, where the governing principle is: 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. The stated case instead calls for: 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.

Question 687

A university's change ticket needs to determine whether a failed rule update originated in the ADOM object database or in FortiGate communication. The engineer proposes the following change: 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. Which mechanism explains why it works?

  1. FortiManager builds desired configuration in multiple management and target database steps; a failure before device installation should not be diagnosed as a FortiGate packet-forwarding problem without evidence.
  2. 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.
  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. Policy import depends on translating device-specific configuration into centrally defined ADOM objects; a successful FGFM connection does not make absent central mappings or unsupported fields valid.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: A university's change ticket needs to determine whether a failed rule update originated in the ADOM object database or in FortiGate communication. FortiManager builds desired configuration in multiple management and target database steps; a failure before device installation should not be diagnosed as a FortiGate packet-forwarding problem without evidence. The corresponding implementation is: 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.

B.

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

C.

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

D.

The question is set in this situation: A university's change ticket needs to determine whether a failed rule update originated in the ADOM object database or in FortiGate communication. Policy import depends on translating device-specific configuration into centrally defined ADOM objects; a successful FGFM connection does not make absent central mappings or unsupported fields valid. That explains “Localize a FortiManager import failure to missing interface mappings or objects”, not the mechanism behind the described change. The relevant principle is: FortiManager builds desired configuration in multiple management and target database steps; a failure before device installation should not be diagnosed as a FortiGate packet-forwarding problem without evidence.

Question 688

A university's change ticket needs to determine whether a failed rule update originated in the ADOM object database or in FortiGate communication. After implementing this change—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.—which test most directly validates its intended outcome?

  1. In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation.
  2. 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.
  3. 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.
  4. Deliberately create an invalid referenced object in a staging policy, compare the reported copy and installation task stages, correct it and verify a clean package build and later device install.

Answer & Explanations

Correct answer: D

A.

In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation. 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: 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.

B.

The question is set in this situation: A university's change ticket needs to determine whether a failed rule update originated in the ADOM object database or in FortiGate communication. Import a staging firewall with a deliberately missing interface alias, reproduce the failed import report, correct the mapping and verify the imported package represents existing rules without unwanted replacement. That would help test “Localize a FortiManager import failure to missing interface mappings or objects”, not the outcome required in this scenario. The relevant acceptance check is: 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.

C.

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. That would help test “Confirm FortiManager database recovery after power failure before rebuilding policies”, not the outcome required in this scenario. The relevant acceptance check is: 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.

D.

The question is set in this situation: A university's change ticket needs to determine whether a failed rule update originated in the ADOM object database or in FortiGate communication. 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. This check is decisive because fortiManager builds desired configuration in multiple management and target database steps; a failure before device installation should not be diagnosed as a FortiGate packet-forwarding problem without evidence.

Question 689

A university's change ticket needs to determine whether a failed rule update originated in the ADOM object database or in FortiGate communication. Which proposed shortcut most directly risks unnecessary branch downtime and persistent policy build errors after misclassifying an internal copy failure and should therefore be rejected?

  1. Ignore a FortiOS compatibility warning and force a new unsupported policy feature to every branch simply because the latest FortiManager UI can display it.
  2. Delete recent FortiManager backup files to free disk after a crash and assume the device inventory screenshot proves its central object database is fully recoverable.
  3. Unregister and factory-reset the FortiGate whenever an import wizard reports an unresolved interface reference, without examining or preserving the live firewall policy.
  4. Reboot all branch FortiGates after every FortiManager copy-failed message because every error must be caused by a network timeout during firewall installation.

Answer & Explanations

Correct answer: D

A.

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: Reboot all branch FortiGates after every FortiManager copy-failed message because every error must be caused by a network timeout during firewall installation.

B.

Delete recent FortiManager backup files to free disk after a crash and assume the device inventory screenshot proves its central object database is fully recoverable. That shortcut risks loss of management revision and policy recovery capability after corruption warning is ignored and backups are removed. Here the specific shortcut is: Reboot all branch FortiGates after every FortiManager copy-failed message because every error must be caused by a network timeout during firewall installation.

C.

The question is set in this situation: A university's change ticket needs to determine whether a failed rule update originated in the ADOM object database or in FortiGate communication. Unregister and factory-reset the FortiGate whenever an import wizard reports an unresolved interface reference, without examining or preserving the live firewall policy. That shortcut risks lost production configuration and repeated import failure after troubleshooting an object mapping as a hardware fault. Here the specific shortcut is: Reboot all branch FortiGates after every FortiManager copy-failed message because every error must be caused by a network timeout during firewall installation.

D.

The question is set in this situation: A university's change ticket needs to determine whether a failed rule update originated in the ADOM object database or in FortiGate communication. Reboot all branch FortiGates after every FortiManager copy-failed message because every error must be caused by a network timeout during firewall installation. The foreseeable failure is unnecessary branch downtime and persistent policy build errors after misclassifying an internal copy failure. The safer response is: 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.

Question 690

A university's change ticket needs to determine whether a failed rule update originated in the ADOM object database or in FortiGate communication. Which combined implementation and verification plan is the best match for this workload?

  1. 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.
  2. 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: 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.
  3. 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: Import a staging firewall with a deliberately missing interface alias, reproduce the failed import report, correct the mapping and verify the imported package represents existing rules without unwanted replacement.
  4. 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: 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.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: A university's change ticket needs to determine whether a failed rule update originated in the ADOM object database or in FortiGate communication. 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. Confirm it through this test: 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. FortiManager builds desired configuration in multiple management and target database steps; a failure before device installation should not be diagnosed as a FortiGate packet-forwarding problem without evidence.

B.

The test would be relevant: 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. But the offered implementation—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.—addresses “Confirm FortiManager database recovery after power failure before rebuilding policies”. The action needed here is: 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.

C.

This action/test pair addresses “Localize a FortiManager import failure to missing interface mappings or objects”. 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. 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. The case instead calls for: 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.

D.

The action is applicable: 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. But its proposed 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.—addresses “Confirm FortiManager database recovery after power failure before rebuilding policies”. This requirement is confirmed instead by: 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.

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