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 70

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.

Question 691

A utility company lost power to its FortiManager VM and sees database reload warnings before a planned policy maintenance window. 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. 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.
  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. 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.

Answer & Explanations

Correct answer: C

A.

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

B.

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

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

D.

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

Question 692

A utility company lost power to its FortiManager VM and sees database reload warnings before a planned policy maintenance window. The engineer proposes the following change: 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. 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. 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.
  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: B

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

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

C.

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

D.

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

Question 693

A utility company lost power to its FortiManager VM and sees database reload warnings before a planned policy maintenance window. After implementing this change—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.—which test most directly validates its intended outcome?

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

A.

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

B.

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

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

D.

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

Question 694

A utility company lost power to its FortiManager VM and sees database reload warnings before a planned policy maintenance window. Which proposed shortcut most directly risks wider management database corruption and inconsistent installations after ignoring an underlying reload or filesystem error and should therefore be rejected?

  1. 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.
  2. Dismiss a FortiManager database reload failure and repeatedly install the same policy to production gateways without inspecting management storage or backup integrity.
  3. 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.
  4. Unregister and factory-reset the FortiGate whenever an import wizard reports an unresolved interface reference, without examining or preserving the live firewall policy.

Answer & Explanations

Correct answer: B

A.

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

B.

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

C.

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

D.

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

Question 695

A utility company lost power to its FortiManager VM and sees database reload warnings before a planned policy maintenance window. Which combined implementation and verification plan is the best match for this workload?

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

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

B.

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

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

D.

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

Question 696

A bank's central management appliance rebooted unexpectedly and its security team needs a disciplined integrity and recovery check before authoring changes. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. 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.
  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. Inspect the exact failed installation log, target FortiGate firmware support and generated configuration command, then revise the central object or mapping and rerun a controlled install to only the affected device.
  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: D

A.

The question is set in this situation: A bank's central management appliance rebooted unexpectedly and its security team needs a disciplined integrity and recovery check before authoring changes. 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: 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.

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

C.

Inspect the exact failed installation log, target FortiGate firmware support and generated configuration command, then revise the central object or mapping and rerun a controlled install to only the affected device. This addresses “Use FortiManager failed-install logs to identify a rejected target command”, where the governing principle is: An installation can fail because a generated command is invalid for one firmware or model, even when the management session remains healthy; opening extra management ports does not fix unsupported syntax. The stated case instead calls for: 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.

D.

The question is set in this situation: A bank's central management appliance rebooted unexpectedly and its security team needs a disciplined integrity and recovery check before authoring changes. 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. 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. Verify the result with this test: 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.

Question 697

A bank's central management appliance rebooted unexpectedly and its security team needs a disciplined integrity and recovery check before authoring changes. The engineer proposes the following change: 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. Which mechanism explains why it works?

  1. An installation can fail because a generated command is invalid for one firmware or model, even when the management session remains healthy; opening extra management ports does not fix unsupported syntax.
  2. 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.
  3. 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.
  4. 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.

Answer & Explanations

Correct answer: D

A.

An installation can fail because a generated command is invalid for one firmware or model, even when the management session remains healthy; opening extra management ports does not fix unsupported syntax. That explains “Use FortiManager failed-install logs to identify a rejected target command”, not the mechanism behind the described change. The relevant 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.

B.

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

C.

The question is set in this situation: A bank's central management appliance rebooted unexpectedly and its security team needs a disciplined integrity and recovery check before authoring changes. 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: 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.

D.

The question is set in this situation: A bank's central management appliance rebooted unexpectedly and its security team needs a disciplined integrity and recovery check before authoring changes. 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 corresponding implementation is: 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.

Question 698

A bank's central management appliance rebooted unexpectedly and its security team needs a disciplined integrity and recovery check before authoring changes. After implementing this change—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.—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. Install a harmless test package containing one unsupported setting to a compatible staging target, capture the device rejection and confirm the corrected generated configuration installs cleanly.
  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 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: C

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

B.

Install a harmless test package containing one unsupported setting to a compatible staging target, capture the device rejection and confirm the corrected generated configuration installs cleanly. That would help test “Use FortiManager failed-install logs to identify a rejected target command”, not the outcome required in this scenario. The relevant acceptance check is: 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.

C.

The question is set in this situation: A bank's central management appliance rebooted unexpectedly and its security team needs a disciplined integrity and recovery check before authoring changes. 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. This check is decisive because 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.

D.

The question is set in this situation: A bank's central management appliance rebooted unexpectedly and its security team needs a disciplined integrity and recovery check before authoring changes. 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: 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.

Question 699

A bank's central management appliance rebooted unexpectedly and its security team needs a disciplined integrity and recovery check before authoring changes. Which proposed shortcut most directly risks wider management database corruption and inconsistent installations after ignoring an underlying reload or filesystem error 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. 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.
  4. Disable all branch firewall filtering whenever FortiManager logs a command syntax error and assume unrestricted network access will make the invalid command acceptable.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: A bank's central management appliance rebooted unexpectedly and its security team needs a disciplined integrity and recovery check before authoring changes. Dismiss a FortiManager database reload failure and repeatedly install the same policy to production gateways without inspecting management storage or backup integrity. The foreseeable failure is wider management database corruption and inconsistent installations after ignoring an underlying reload or filesystem error. The safer response is: 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.

B.

Ignore a FortiOS compatibility warning and force a new unsupported policy feature to every branch simply because the latest FortiManager UI can display it. That shortcut risks rejected policy and inconsistent enforcement across device firmware variants after version support is assumed. Here the specific shortcut is: Dismiss a FortiManager database reload failure and repeatedly install the same policy to production gateways without inspecting management storage or backup integrity.

C.

The question is set in this situation: A bank's central management appliance rebooted unexpectedly and its security team needs a disciplined integrity and recovery check before authoring changes. 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: Dismiss a FortiManager database reload failure and repeatedly install the same policy to production gateways without inspecting management storage or backup integrity.

D.

Disable all branch firewall filtering whenever FortiManager logs a command syntax error and assume unrestricted network access will make the invalid command acceptable. That shortcut risks continued policy installation failure and unnecessary exposure after treating device syntax rejection as a network problem. Here the specific shortcut is: Dismiss a FortiManager database reload failure and repeatedly install the same policy to production gateways without inspecting management storage or backup integrity.

Question 700

A bank's central management appliance rebooted unexpectedly and its security team needs a disciplined integrity and recovery check before authoring changes. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Inspect the exact failed installation log, target FortiGate firmware support and generated configuration command, then revise the central object or mapping and rerun a controlled install to only the affected device. 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.
  2. 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.
  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: Install a harmless test package containing one unsupported setting to a compatible staging target, capture the device rejection and confirm the corrected generated configuration installs cleanly.
  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: 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: B

A.

The test would be relevant: 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. But the offered implementation—Inspect the exact failed installation log, target FortiGate firmware support and generated configuration command, then revise the central object or mapping and rerun a controlled install to only the affected device.—addresses “Use FortiManager failed-install logs to identify a rejected target command”. The action needed here is: 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.

B.

The question is set in this situation: A bank's central management appliance rebooted unexpectedly and its security team needs a disciplined integrity and recovery check before authoring changes. 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. Confirm it through this test: 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. 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.

C.

The action is applicable: 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. But its proposed test—Install a harmless test package containing one unsupported setting to a compatible staging target, capture the device rejection and confirm the corrected generated configuration installs cleanly.—addresses “Use FortiManager failed-install logs to identify a rejected target command”. This requirement is confirmed instead by: 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.

D.

This action/test pair addresses “Confirm FortiManager database recovery after power failure before rebuilding policies”. 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. 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. The case instead calls for: 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.

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