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 71

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.

Question 701

A managed services provider sees a FortiManager package install fail on one older FortiOS branch while the same package succeeds at other sites. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

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

A.

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

B.

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

C.

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

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

Question 702

A managed services provider sees a FortiManager package install fail on one older FortiOS branch while the same package succeeds at other sites. The engineer proposes the following change: 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. 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. 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. 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.
  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: C

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

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

C.

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

D.

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

Question 703

A managed services provider sees a FortiManager package install fail on one older FortiOS branch while the same package succeeds at other sites. After implementing this change—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.—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. 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. 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. 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.

Answer & Explanations

Correct answer: B

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

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

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

D.

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

Question 704

A managed services provider sees a FortiManager package install fail on one older FortiOS branch while the same package succeeds at other sites. Which proposed shortcut most directly risks continued policy installation failure and unnecessary exposure after treating device syntax rejection as a network problem and should therefore be rejected?

  1. Ping the FortiManager from its own private subnet and declare all remote FortiGates correctly managed through the public NAT path without any branch-side FGFM test.
  2. 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. Dismiss a FortiManager database reload failure and repeatedly install the same policy to production gateways without inspecting management storage or backup integrity.
  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: D

A.

Ping the FortiManager from its own private subnet and declare all remote FortiGates correctly managed through the public NAT path without any branch-side FGFM test. That shortcut risks unreachable central policy control after an address translation hides the actual management server from remote branches. Here the specific shortcut is: Disable all branch firewall filtering whenever FortiManager logs a command syntax error and assume unrestricted network access will make the invalid command acceptable.

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: Disable all branch firewall filtering whenever FortiManager logs a command syntax error and assume unrestricted network access will make the invalid command acceptable.

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: Disable all branch firewall filtering whenever FortiManager logs a command syntax error and assume unrestricted network access will make the invalid command acceptable.

D.

Disable all branch firewall filtering whenever FortiManager logs a command syntax error and assume unrestricted network access will make the invalid command acceptable. The foreseeable failure is continued policy installation failure and unnecessary exposure after treating device syntax rejection as a network problem. The safer response is: 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.

Question 705

A managed services provider sees a FortiManager package install fail on one older FortiOS branch while the same package succeeds at other sites. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Use supported FortiManager filesystem and database status diagnostics after storage or power faults, verify backups and snapshots, and perform documented recovery before trusting policy histories or large-scale install operations. Verify: In a nonproduction failure rehearsal compare central ADOM revision availability, filesystem checks and backup integrity, restore a known configuration if required and perform one harmless device install.
  2. Implement: 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.
  3. 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: 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: 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.

Answer & Explanations

Correct answer: C

A.

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

B.

The test would be relevant: 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. But the offered implementation—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.—addresses “Investigate a failed reload and central database integrity after an unclean shutdown”. The action needed here is: 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.

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

D.

The action is applicable: 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. But its proposed 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.—addresses “Investigate a failed reload and central database integrity after an unclean shutdown”. This requirement is confirmed instead by: 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.

Question 706

A hospital's replacement FortiGate has a different interface schema and its install log identifies a rejected mapping that must be corrected centrally. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

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

Answer & Explanations

Correct answer: B

A.

Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path. This addresses “Diagnose an ADOM version compatibility warning on a mixed-firmware FortiGate fleet”, where the governing principle is: Policy and object schema is tied to supported ADOM versions; a configuration that works on one firmware generation may be invalid on another, even with healthy FGFM. The stated case instead calls for: Inspect the 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.

B.

The question is set in this situation: A hospital's replacement FortiGate has a different interface schema and its install log identifies a rejected mapping that must be corrected centrally. 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. 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. Verify the result with this 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.

C.

The question is set in this situation: A hospital's replacement FortiGate has a different interface schema and its install log identifies a rejected mapping that must be corrected centrally. 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: 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.

D.

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

Question 707

A hospital's replacement FortiGate has a different interface schema and its install log identifies a rejected mapping that must be corrected centrally. The engineer proposes the following change: 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. Which mechanism explains why it works?

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

Answer & Explanations

Correct answer: D

A.

Policy and object schema is tied to supported ADOM versions; a configuration that works on one firmware generation may be invalid on another, even with healthy FGFM. That explains “Diagnose an ADOM version compatibility warning on a mixed-firmware FortiGate fleet”, not the mechanism behind the described change. The relevant principle is: 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.

B.

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

C.

The question is set in this situation: A hospital's replacement FortiGate has a different interface schema and its install log identifies a rejected mapping that must be corrected centrally. 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: 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.

D.

The question is set in this situation: A hospital's replacement FortiGate has a different interface schema and its install log identifies a rejected mapping that must be corrected centrally. 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 corresponding implementation is: 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.

Question 708

A hospital's replacement FortiGate has a different interface schema and its install log identifies a rejected mapping that must be corrected centrally. After implementing this change—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.—which test most directly validates its intended outcome?

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

A.

The question is set in this situation: A hospital's replacement FortiGate has a different interface schema and its install log identifies a rejected mapping that must be corrected centrally. 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. This check is decisive because 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.

B.

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

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. That would help test “Distinguish a FortiManager copy failure from an installation failure”, not the outcome required in this scenario. The relevant acceptance check is: 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.

D.

The question is set in this situation: A hospital's replacement FortiGate has a different interface schema and its install log identifies a rejected mapping that must be corrected centrally. 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: 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.

Question 709

A hospital's replacement FortiGate has a different interface schema and its install log identifies a rejected mapping that must be corrected centrally. Which proposed shortcut most directly risks continued policy installation failure and unnecessary exposure after treating device syntax rejection as a network problem 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. Reboot all branch FortiGates after every FortiManager copy-failed message because every error must be caused by a network timeout during firewall installation.
  3. Disable all branch firewall filtering whenever FortiManager logs a command syntax error and assume unrestricted network access will make the invalid command acceptable.
  4. Dismiss a FortiManager database reload failure and repeatedly install the same policy to production gateways without inspecting management storage or backup integrity.

Answer & Explanations

Correct answer: C

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: Disable all branch firewall filtering whenever FortiManager logs a command syntax error and assume unrestricted network access will make the invalid command acceptable.

B.

Reboot all branch FortiGates after every FortiManager copy-failed message because every error must be caused by a network timeout during firewall installation. That shortcut risks unnecessary branch downtime and persistent policy build errors after misclassifying an internal copy failure. Here the specific shortcut is: Disable all branch firewall filtering whenever FortiManager logs a command syntax error and assume unrestricted network access will make the invalid command acceptable.

C.

The question is set in this situation: A hospital's replacement FortiGate has a different interface schema and its install log identifies a rejected mapping that must be corrected centrally. Disable all branch firewall filtering whenever FortiManager logs a command syntax error and assume unrestricted network access will make the invalid command acceptable. The foreseeable failure is continued policy installation failure and unnecessary exposure after treating device syntax rejection as a network problem. The safer response is: 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.

D.

The question is set in this situation: A hospital's replacement FortiGate has a different interface schema and its install log identifies a rejected mapping that must be corrected centrally. 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: Disable all branch firewall filtering whenever FortiManager logs a command syntax error and assume unrestricted network access will make the invalid command acceptable.

Question 710

A hospital's replacement FortiGate has a different interface schema and its install log identifies a rejected mapping that must be corrected centrally. 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: 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: 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. 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: 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: 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.

Answer & Explanations

Correct answer: D

A.

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

B.

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

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

D.

The question is set in this situation: A hospital's replacement FortiGate has a different interface schema and its install log identifies a rejected mapping that must be corrected centrally. 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. Confirm it through this 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. 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.

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