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 77

Question 760

A university's branch firewall has a local DNS misconfiguration and the central team needs to restore it without resetting the ADOM's recent shared object changes. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Compare the managed device's target-specific database and retrieved FortiGate configuration with shared ADOM policy objects, identifying which layer diverges before selecting retrieve, import or install operations. Verify: Take a staged device revision, make a local interface setting error, restore the target configuration and confirm an unrelated ADOM service object and second firewall package remain unchanged.
  2. Implement: Use device-level revision comparison to restore an approved local configuration baseline when appropriate and separately validate that the current ADOM package remains correct before installing it. Verify: Take a staged device revision, make a local interface setting error, restore the target configuration and confirm an unrelated ADOM service object and second firewall package remain unchanged.
  3. Implement: Inspect the FortiManager configuration comparison and revision history for a managed firewall, determine whether an unapproved local change or an uninstalled central object update explains the difference, and choose a scoped remedy. Verify: Modify one staged FortiGate locally and separately edit an ADOM address object without installation, compare status and history, then demonstrate the correct action for each case.
  4. Implement: Use device-level revision comparison to restore an approved local configuration baseline when appropriate and separately validate that the current ADOM package remains correct before installing it. Verify: Create a harmless shared ADOM service edit and a separate local device change, inspect both database views, classify each drift and reconcile them independently through approved operations.

Answer & Explanations

Correct answer: B

A.

The question is set in this situation: A university's branch firewall has a local DNS misconfiguration and the central team needs to restore it without resetting the ADOM's recent shared object changes. The test would be relevant: Take a staged device revision, make a local interface setting error, restore the target configuration and confirm an unrelated ADOM service object and second firewall package remain unchanged. But the offered implementation—Compare the managed device's target-specific database and retrieved FortiGate configuration with shared ADOM policy objects, identifying which layer diverges before selecting retrieve, import or install operations.—addresses “Compare FortiManager device-level database against ADOM-level policy objects to locate drift”. The action needed here is: Use device-level revision comparison to restore an approved local configuration baseline when appropriate and separately validate that the current ADOM package remains correct before installing it.

B.

The question is set in this situation: A university's branch firewall has a local DNS misconfiguration and the central team needs to restore it without resetting the ADOM's recent shared object changes. Use device-level revision comparison to restore an approved local configuration baseline when appropriate and separately validate that the current ADOM package remains correct before installing it. Confirm it through this test: Take a staged device revision, make a local interface setting error, restore the target configuration and confirm an unrelated ADOM service object and second firewall package remain unchanged. Device revisions are narrower than an ADOM-wide object revision; restoring a gateway configuration should not silently reverse unrelated centrally reviewed changes for other devices.

C.

The question is set in this situation: A university's branch firewall has a local DNS misconfiguration and the central team needs to restore it without resetting the ADOM's recent shared object changes. This action/test pair addresses “Distinguish local FortiGate edits from ADOM object changes in a configuration mismatch”. Inspect the FortiManager configuration comparison and revision history for a managed firewall, determine whether an unapproved local change or an uninstalled central object update explains the difference, and choose a scoped remedy. Modify one staged FortiGate locally and separately edit an ADOM address object without installation, compare status and history, then demonstrate the correct action for each case. The case instead calls for: Use device-level revision comparison to restore an approved local configuration baseline when appropriate and separately validate that the current ADOM package remains correct before installing it.

D.

The question is set in this situation: A university's branch firewall has a local DNS misconfiguration and the central team needs to restore it without resetting the ADOM's recent shared object changes. The action is applicable: Use device-level revision comparison to restore an approved local configuration baseline when appropriate and separately validate that the current ADOM package remains correct before installing it. But its proposed test—Create a harmless shared ADOM service edit and a separate local device change, inspect both database views, classify each drift and reconcile them independently through approved operations.—addresses “Compare FortiManager device-level database against ADOM-level policy objects to locate drift”. This requirement is confirmed instead by: Take a staged device revision, make a local interface setting error, restore the target configuration and confirm an unrelated ADOM service object and second firewall package remain unchanged.

Question 761

An insurance network has short recurring FortiManager disconnect alerts for one branch but user internet traffic continues operating normally. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. Identify FortiManager partitions, database storage and safe cleanup options when disk usage is high, preserve required configuration backups and audit history, and verify adequate free space before resuming heavy policy tasks.
  2. Collect supported FortiManager process status, system events and narrowly scoped debug output for the affected operation, correlate timestamps and stop temporary diagnostics after identifying a specific service or connectivity issue.
  3. Review FGFM connection and keepalive event history for a disconnected managed FortiGate, correlate it with actual routing and interface reachability, and verify that management reconnection restores device status before pushing changes.
  4. Compare the managed device's target-specific database and retrieved FortiGate configuration with shared ADOM policy objects, identifying which layer diverges before selecting retrieve, import or install operations.

Answer & Explanations

Correct answer: C

A.

Identify FortiManager partitions, database storage and safe cleanup options when disk usage is high, preserve required configuration backups and audit history, and verify adequate free space before resuming heavy policy tasks. This addresses “Investigate FortiManager high disk usage and protected log or backup retention”, where the governing principle is: Insufficient central storage can interfere with management databases and revisions, but indiscriminately deleting backup or database files risks destroying recovery artifacts and making the condition worse. The stated case instead calls for: Review FGFM connection and keepalive event history for a disconnected managed FortiGate, correlate it with actual routing and interface reachability, and verify that management reconnection restores device status before pushing changes.

B.

Collect supported FortiManager process status, system events and narrowly scoped debug output for the affected operation, correlate timestamps and stop temporary diagnostics after identifying a specific service or connectivity issue. This addresses “Use FortiManager process status and debug evidence for a persistent management fault”, where the governing principle is: A generic GUI error can originate from API services, device management processes or database handling; targeted debug evidence is more reliable than resetting the entire environment without identifying the failing component. The stated case instead calls for: Review FGFM connection and keepalive event history for a disconnected managed FortiGate, correlate it with actual routing and interface reachability, and verify that management reconnection restores device status before pushing changes.

C.

Review FGFM connection and keepalive event history for a disconnected managed FortiGate, correlate it with actual routing and interface reachability, and verify that management reconnection restores device status before pushing changes. FGFM keepalives help detect and maintain central device sessions; a lost keepalive can reflect NAT or network instability without meaning the FortiGate itself stopped enforcing traffic. Verify the result with this test: Interrupt only the lab FGFM path, observe keepalive and disconnected status, restore the route and confirm device reconnects and successfully handles a harmless central management request.

D.

Compare the managed device's target-specific database and retrieved FortiGate configuration with shared ADOM policy objects, identifying which layer diverges before selecting retrieve, import or install operations. This addresses “Compare FortiManager device-level database against ADOM-level policy objects to locate drift”, where the governing principle is: Shared policy/object databases and device-specific configuration records serve different purposes; a status mismatch can arise from a local change, an uninstalled ADOM package or a missing interface map. The stated case instead calls for: Review FGFM connection and keepalive event history for a disconnected managed FortiGate, correlate it with actual routing and interface reachability, and verify that management reconnection restores device status before pushing changes.

Question 762

An insurance network has short recurring FortiManager disconnect alerts for one branch but user internet traffic continues operating normally. The engineer proposes the following change: Review FGFM connection and keepalive event history for a disconnected managed FortiGate, correlate it with actual routing and interface reachability, and verify that management reconnection restores device status before pushing changes. Which mechanism explains why it works?

  1. Insufficient central storage can interfere with management databases and revisions, but indiscriminately deleting backup or database files risks destroying recovery artifacts and making the condition worse.
  2. FGFM keepalives help detect and maintain central device sessions; a lost keepalive can reflect NAT or network instability without meaning the FortiGate itself stopped enforcing traffic.
  3. Shared policy/object databases and device-specific configuration records serve different purposes; a status mismatch can arise from a local change, an uninstalled ADOM package or a missing interface map.
  4. A generic GUI error can originate from API services, device management processes or database handling; targeted debug evidence is more reliable than resetting the entire environment without identifying the failing component.

Answer & Explanations

Correct answer: B

A.

Insufficient central storage can interfere with management databases and revisions, but indiscriminately deleting backup or database files risks destroying recovery artifacts and making the condition worse. That explains “Investigate FortiManager high disk usage and protected log or backup retention”, not the mechanism behind the described change. The relevant principle is: FGFM keepalives help detect and maintain central device sessions; a lost keepalive can reflect NAT or network instability without meaning the FortiGate itself stopped enforcing traffic.

B.

FGFM keepalives help detect and maintain central device sessions; a lost keepalive can reflect NAT or network instability without meaning the FortiGate itself stopped enforcing traffic. The corresponding implementation is: Review FGFM connection and keepalive event history for a disconnected managed FortiGate, correlate it with actual routing and interface reachability, and verify that management reconnection restores device status before pushing changes.

C.

Shared policy/object databases and device-specific configuration records serve different purposes; a status mismatch can arise from a local change, an uninstalled ADOM package or a missing interface map. That explains “Compare FortiManager device-level database against ADOM-level policy objects to locate drift”, not the mechanism behind the described change. The relevant principle is: FGFM keepalives help detect and maintain central device sessions; a lost keepalive can reflect NAT or network instability without meaning the FortiGate itself stopped enforcing traffic.

D.

A generic GUI error can originate from API services, device management processes or database handling; targeted debug evidence is more reliable than resetting the entire environment without identifying the failing component. That explains “Use FortiManager process status and debug evidence for a persistent management fault”, not the mechanism behind the described change. The relevant principle is: FGFM keepalives help detect and maintain central device sessions; a lost keepalive can reflect NAT or network instability without meaning the FortiGate itself stopped enforcing traffic.

Question 763

An insurance network has short recurring FortiManager disconnect alerts for one branch but user internet traffic continues operating normally. After implementing this change—Review FGFM connection and keepalive event history for a disconnected managed FortiGate, correlate it with actual routing and interface reachability, and verify that management reconnection restores device status before pushing changes.—which test most directly validates its intended outcome?

  1. In a lab simulate a storage threshold alarm, inspect supported filesystem and application usage tools, remove only approved disposable data and confirm policy database and backup integrity remain intact.
  2. Create a harmless shared ADOM service edit and a separate local device change, inspect both database views, classify each drift and reconcile them independently through approved operations.
  3. Reproduce a benign stalled policy task on a staging manager, inspect relevant process status and logs, isolate the cause and confirm a targeted correction restores the intended action.
  4. Interrupt only the lab FGFM path, observe keepalive and disconnected status, restore the route and confirm device reconnects and successfully handles a harmless central management request.

Answer & Explanations

Correct answer: D

A.

In a lab simulate a storage threshold alarm, inspect supported filesystem and application usage tools, remove only approved disposable data and confirm policy database and backup integrity remain intact. That would help test “Investigate FortiManager high disk usage and protected log or backup retention”, not the outcome required in this scenario. The relevant acceptance check is: Interrupt only the lab FGFM path, observe keepalive and disconnected status, restore the route and confirm device reconnects and successfully handles a harmless central management request.

B.

Create a harmless shared ADOM service edit and a separate local device change, inspect both database views, classify each drift and reconcile them independently through approved operations. That would help test “Compare FortiManager device-level database against ADOM-level policy objects to locate drift”, not the outcome required in this scenario. The relevant acceptance check is: Interrupt only the lab FGFM path, observe keepalive and disconnected status, restore the route and confirm device reconnects and successfully handles a harmless central management request.

C.

Reproduce a benign stalled policy task on a staging manager, inspect relevant process status and logs, isolate the cause and confirm a targeted correction restores the intended action. That would help test “Use FortiManager process status and debug evidence for a persistent management fault”, not the outcome required in this scenario. The relevant acceptance check is: Interrupt only the lab FGFM path, observe keepalive and disconnected status, restore the route and confirm device reconnects and successfully handles a harmless central management request.

D.

Interrupt only the lab FGFM path, observe keepalive and disconnected status, restore the route and confirm device reconnects and successfully handles a harmless central management request. This check is decisive because fGFM keepalives help detect and maintain central device sessions; a lost keepalive can reflect NAT or network instability without meaning the FortiGate itself stopped enforcing traffic.

Question 764

An insurance network has short recurring FortiManager disconnect alerts for one branch but user internet traffic continues operating normally. Which proposed shortcut most directly risks unnecessary site outage after a transient FGFM management disconnect is mistaken for a failed firewall and should therefore be rejected?

  1. Reinstall the firewall operating system whenever FortiManager misses one keepalive and assume gateway packet forwarding must have stopped during a management network interruption.
  2. Delete arbitrary FortiManager database directories and every configuration archive to clear an alarm immediately without checking which files contain active ADOM objects.
  3. Enable maximum debugging indefinitely on all central processes and reboot every gateway on the first error message without preserving or analyzing the relevant FortiManager logs.
  4. Fix an out-of-sync device by deleting the entire customer ADOM because central and device databases must always be byte-for-byte identical at all times.

Answer & Explanations

Correct answer: A

A.

Reinstall the firewall operating system whenever FortiManager misses one keepalive and assume gateway packet forwarding must have stopped during a management network interruption. The foreseeable failure is unnecessary site outage after a transient FGFM management disconnect is mistaken for a failed firewall. The safer response is: Review FGFM connection and keepalive event history for a disconnected managed FortiGate, correlate it with actual routing and interface reachability, and verify that management reconnection restores device status before pushing changes.

B.

Delete arbitrary FortiManager database directories and every configuration archive to clear an alarm immediately without checking which files contain active ADOM objects. That shortcut risks irrecoverable management data loss after an uncontrolled disk cleanup removes critical central records. Here the specific shortcut is: Reinstall the firewall operating system whenever FortiManager misses one keepalive and assume gateway packet forwarding must have stopped during a management network interruption.

C.

Enable maximum debugging indefinitely on all central processes and reboot every gateway on the first error message without preserving or analyzing the relevant FortiManager logs. That shortcut risks lost diagnostic evidence and collateral disruption after uncontrolled debugging and unrelated restarts. Here the specific shortcut is: Reinstall the firewall operating system whenever FortiManager misses one keepalive and assume gateway packet forwarding must have stopped during a management network interruption.

D.

Fix an out-of-sync device by deleting the entire customer ADOM because central and device databases must always be byte-for-byte identical at all times. That shortcut risks avoidable loss of shared policy state when device-specific drift is mistaken for corruption of the ADOM database. Here the specific shortcut is: Reinstall the firewall operating system whenever FortiManager misses one keepalive and assume gateway packet forwarding must have stopped during a management network interruption.

Question 765

An insurance network has short recurring FortiManager disconnect alerts for one branch but user internet traffic continues operating normally. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Review FGFM connection and keepalive event history for a disconnected managed FortiGate, correlate it with actual routing and interface reachability, and verify that management reconnection restores device status before pushing changes. Verify: In a lab simulate a storage threshold alarm, inspect supported filesystem and application usage tools, remove only approved disposable data and confirm policy database and backup integrity remain intact.
  2. Implement: Collect supported FortiManager process status, system events and narrowly scoped debug output for the affected operation, correlate timestamps and stop temporary diagnostics after identifying a specific service or connectivity issue. Verify: Reproduce a benign stalled policy task on a staging manager, inspect relevant process status and logs, isolate the cause and confirm a targeted correction restores the intended action.
  3. Implement: Review FGFM connection and keepalive event history for a disconnected managed FortiGate, correlate it with actual routing and interface reachability, and verify that management reconnection restores device status before pushing changes. Verify: Interrupt only the lab FGFM path, observe keepalive and disconnected status, restore the route and confirm device reconnects and successfully handles a harmless central management request.
  4. Implement: Identify FortiManager partitions, database storage and safe cleanup options when disk usage is high, preserve required configuration backups and audit history, and verify adequate free space before resuming heavy policy tasks. Verify: Interrupt only the lab FGFM path, observe keepalive and disconnected status, restore the route and confirm device reconnects and successfully handles a harmless central management request.

Answer & Explanations

Correct answer: C

A.

The action is applicable: Review FGFM connection and keepalive event history for a disconnected managed FortiGate, correlate it with actual routing and interface reachability, and verify that management reconnection restores device status before pushing changes. But its proposed test—In a lab simulate a storage threshold alarm, inspect supported filesystem and application usage tools, remove only approved disposable data and confirm policy database and backup integrity remain intact.—addresses “Investigate FortiManager high disk usage and protected log or backup retention”. This requirement is confirmed instead by: Interrupt only the lab FGFM path, observe keepalive and disconnected status, restore the route and confirm device reconnects and successfully handles a harmless central management request.

B.

This action/test pair addresses “Use FortiManager process status and debug evidence for a persistent management fault”. Collect supported FortiManager process status, system events and narrowly scoped debug output for the affected operation, correlate timestamps and stop temporary diagnostics after identifying a specific service or connectivity issue. Reproduce a benign stalled policy task on a staging manager, inspect relevant process status and logs, isolate the cause and confirm a targeted correction restores the intended action. The case instead calls for: Review FGFM connection and keepalive event history for a disconnected managed FortiGate, correlate it with actual routing and interface reachability, and verify that management reconnection restores device status before pushing changes.

C.

Review FGFM connection and keepalive event history for a disconnected managed FortiGate, correlate it with actual routing and interface reachability, and verify that management reconnection restores device status before pushing changes. Confirm it through this test: Interrupt only the lab FGFM path, observe keepalive and disconnected status, restore the route and confirm device reconnects and successfully handles a harmless central management request. FGFM keepalives help detect and maintain central device sessions; a lost keepalive can reflect NAT or network instability without meaning the FortiGate itself stopped enforcing traffic.

D.

The test would be relevant: Interrupt only the lab FGFM path, observe keepalive and disconnected status, restore the route and confirm device reconnects and successfully handles a harmless central management request. But the offered implementation—Identify FortiManager partitions, database storage and safe cleanup options when disk usage is high, preserve required configuration backups and audit history, and verify adequate free space before resuming heavy policy tasks.—addresses “Investigate FortiManager high disk usage and protected log or backup retention”. The action needed here is: Review FGFM connection and keepalive event history for a disconnected managed FortiGate, correlate it with actual routing and interface reachability, and verify that management reconnection restores device status before pushing changes.

Question 766

A logistics company replaced its WAN router and needs to correlate NAT session timeouts with FortiManager FGFM keepalive recovery. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. Collect supported FortiManager process status, system events and narrowly scoped debug output for the affected operation, correlate timestamps and stop temporary diagnostics after identifying a specific service or connectivity issue.
  2. Review which side initiates the supported FGFM management session for a FortiGate behind NAT, configure reachable control-plane addresses and permitted outbound paths, and validate authenticated enrollment before using policy installation.
  3. Identify FortiManager partitions, database storage and safe cleanup options when disk usage is high, preserve required configuration backups and audit history, and verify adequate free space before resuming heavy policy tasks.
  4. Review FGFM connection and keepalive event history for a disconnected managed FortiGate, correlate it with actual routing and interface reachability, and verify that management reconnection restores device status before pushing changes.

Answer & Explanations

Correct answer: D

A.

The question is set in this situation: A logistics company replaced its WAN router and needs to correlate NAT session timeouts with FortiManager FGFM keepalive recovery. Collect supported FortiManager process status, system events and narrowly scoped debug output for the affected operation, correlate timestamps and stop temporary diagnostics after identifying a specific service or connectivity issue. This addresses “Use FortiManager process status and debug evidence for a persistent management fault”, where the governing principle is: A generic GUI error can originate from API services, device management processes or database handling; targeted debug evidence is more reliable than resetting the entire environment without identifying the failing component. The stated case instead calls for: Review FGFM connection and keepalive event history for a disconnected managed FortiGate, correlate it with actual routing and interface reachability, and verify that management reconnection restores device status before pushing changes.

B.

Review which side initiates the supported FGFM management session for a FortiGate behind NAT, configure reachable control-plane addresses and permitted outbound paths, and validate authenticated enrollment before using policy installation. This addresses “Handle FortiGate behind-NAT registration without assuming direct inbound connectivity”, where the governing principle is: Branch firewalls behind address translation may not be directly dialable from FortiManager; the deployment must account for the supported device-initiated management channel and stateful NAT behavior. The stated case instead calls for: Review FGFM connection and keepalive event history for a disconnected managed FortiGate, correlate it with actual routing and interface reachability, and verify that management reconnection restores device status before pushing changes.

C.

The question is set in this situation: A logistics company replaced its WAN router and needs to correlate NAT session timeouts with FortiManager FGFM keepalive recovery. Identify FortiManager partitions, database storage and safe cleanup options when disk usage is high, preserve required configuration backups and audit history, and verify adequate free space before resuming heavy policy tasks. This addresses “Investigate FortiManager high disk usage and protected log or backup retention”, where the governing principle is: Insufficient central storage can interfere with management databases and revisions, but indiscriminately deleting backup or database files risks destroying recovery artifacts and making the condition worse. The stated case instead calls for: Review FGFM connection and keepalive event history for a disconnected managed FortiGate, correlate it with actual routing and interface reachability, and verify that management reconnection restores device status before pushing changes.

D.

The question is set in this situation: A logistics company replaced its WAN router and needs to correlate NAT session timeouts with FortiManager FGFM keepalive recovery. Review FGFM connection and keepalive event history for a disconnected managed FortiGate, correlate it with actual routing and interface reachability, and verify that management reconnection restores device status before pushing changes. FGFM keepalives help detect and maintain central device sessions; a lost keepalive can reflect NAT or network instability without meaning the FortiGate itself stopped enforcing traffic. Verify the result with this test: Interrupt only the lab FGFM path, observe keepalive and disconnected status, restore the route and confirm device reconnects and successfully handles a harmless central management request.

Question 767

A logistics company replaced its WAN router and needs to correlate NAT session timeouts with FortiManager FGFM keepalive recovery. The engineer proposes the following change: Review FGFM connection and keepalive event history for a disconnected managed FortiGate, correlate it with actual routing and interface reachability, and verify that management reconnection restores device status before pushing changes. Which mechanism explains why it works?

  1. FGFM keepalives help detect and maintain central device sessions; a lost keepalive can reflect NAT or network instability without meaning the FortiGate itself stopped enforcing traffic.
  2. Branch firewalls behind address translation may not be directly dialable from FortiManager; the deployment must account for the supported device-initiated management channel and stateful NAT behavior.
  3. A generic GUI error can originate from API services, device management processes or database handling; targeted debug evidence is more reliable than resetting the entire environment without identifying the failing component.
  4. Insufficient central storage can interfere with management databases and revisions, but indiscriminately deleting backup or database files risks destroying recovery artifacts and making the condition worse.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: A logistics company replaced its WAN router and needs to correlate NAT session timeouts with FortiManager FGFM keepalive recovery. FGFM keepalives help detect and maintain central device sessions; a lost keepalive can reflect NAT or network instability without meaning the FortiGate itself stopped enforcing traffic. The corresponding implementation is: Review FGFM connection and keepalive event history for a disconnected managed FortiGate, correlate it with actual routing and interface reachability, and verify that management reconnection restores device status before pushing changes.

B.

Branch firewalls behind address translation may not be directly dialable from FortiManager; the deployment must account for the supported device-initiated management channel and stateful NAT behavior. That explains “Handle FortiGate behind-NAT registration without assuming direct inbound connectivity”, not the mechanism behind the described change. The relevant principle is: FGFM keepalives help detect and maintain central device sessions; a lost keepalive can reflect NAT or network instability without meaning the FortiGate itself stopped enforcing traffic.

C.

The question is set in this situation: A logistics company replaced its WAN router and needs to correlate NAT session timeouts with FortiManager FGFM keepalive recovery. A generic GUI error can originate from API services, device management processes or database handling; targeted debug evidence is more reliable than resetting the entire environment without identifying the failing component. That explains “Use FortiManager process status and debug evidence for a persistent management fault”, not the mechanism behind the described change. The relevant principle is: FGFM keepalives help detect and maintain central device sessions; a lost keepalive can reflect NAT or network instability without meaning the FortiGate itself stopped enforcing traffic.

D.

The question is set in this situation: A logistics company replaced its WAN router and needs to correlate NAT session timeouts with FortiManager FGFM keepalive recovery. Insufficient central storage can interfere with management databases and revisions, but indiscriminately deleting backup or database files risks destroying recovery artifacts and making the condition worse. That explains “Investigate FortiManager high disk usage and protected log or backup retention”, not the mechanism behind the described change. The relevant principle is: FGFM keepalives help detect and maintain central device sessions; a lost keepalive can reflect NAT or network instability without meaning the FortiGate itself stopped enforcing traffic.

Question 768

A logistics company replaced its WAN router and needs to correlate NAT session timeouts with FortiManager FGFM keepalive recovery. After implementing this change—Review FGFM connection and keepalive event history for a disconnected managed FortiGate, correlate it with actual routing and interface reachability, and verify that management reconnection restores device status before pushing changes.—which test most directly validates its intended outcome?

  1. Reproduce a benign stalled policy task on a staging manager, inspect relevant process status and logs, isolate the cause and confirm a targeted correction restores the intended action.
  2. Interrupt only the lab FGFM path, observe keepalive and disconnected status, restore the route and confirm device reconnects and successfully handles a harmless central management request.
  3. In a lab simulate a storage threshold alarm, inspect supported filesystem and application usage tools, remove only approved disposable data and confirm policy database and backup integrity remain intact.
  4. Place a test FortiGate behind a simulated branch NAT device, inspect the management session initiation and return route, and verify a central device status query and policy operation after authorization.

Answer & Explanations

Correct answer: B

A.

The question is set in this situation: A logistics company replaced its WAN router and needs to correlate NAT session timeouts with FortiManager FGFM keepalive recovery. Reproduce a benign stalled policy task on a staging manager, inspect relevant process status and logs, isolate the cause and confirm a targeted correction restores the intended action. That would help test “Use FortiManager process status and debug evidence for a persistent management fault”, not the outcome required in this scenario. The relevant acceptance check is: Interrupt only the lab FGFM path, observe keepalive and disconnected status, restore the route and confirm device reconnects and successfully handles a harmless central management request.

B.

The question is set in this situation: A logistics company replaced its WAN router and needs to correlate NAT session timeouts with FortiManager FGFM keepalive recovery. Interrupt only the lab FGFM path, observe keepalive and disconnected status, restore the route and confirm device reconnects and successfully handles a harmless central management request. This check is decisive because fGFM keepalives help detect and maintain central device sessions; a lost keepalive can reflect NAT or network instability without meaning the FortiGate itself stopped enforcing traffic.

C.

The question is set in this situation: A logistics company replaced its WAN router and needs to correlate NAT session timeouts with FortiManager FGFM keepalive recovery. In a lab simulate a storage threshold alarm, inspect supported filesystem and application usage tools, remove only approved disposable data and confirm policy database and backup integrity remain intact. That would help test “Investigate FortiManager high disk usage and protected log or backup retention”, not the outcome required in this scenario. The relevant acceptance check is: Interrupt only the lab FGFM path, observe keepalive and disconnected status, restore the route and confirm device reconnects and successfully handles a harmless central management request.

D.

Place a test FortiGate behind a simulated branch NAT device, inspect the management session initiation and return route, and verify a central device status query and policy operation after authorization. That would help test “Handle FortiGate behind-NAT registration without assuming direct inbound connectivity”, not the outcome required in this scenario. The relevant acceptance check is: Interrupt only the lab FGFM path, observe keepalive and disconnected status, restore the route and confirm device reconnects and successfully handles a harmless central management request.

Question 769

A logistics company replaced its WAN router and needs to correlate NAT session timeouts with FortiManager FGFM keepalive recovery. Which proposed shortcut most directly risks unnecessary site outage after a transient FGFM management disconnect is mistaken for a failed firewall and should therefore be rejected?

  1. Register a private branch FortiGate using its unroutable internal address from the public internet and assume FortiManager can initiate arbitrary inbound connections through NAT without any session setup.
  2. Delete arbitrary FortiManager database directories and every configuration archive to clear an alarm immediately without checking which files contain active ADOM objects.
  3. Enable maximum debugging indefinitely on all central processes and reboot every gateway on the first error message without preserving or analyzing the relevant FortiManager logs.
  4. Reinstall the firewall operating system whenever FortiManager misses one keepalive and assume gateway packet forwarding must have stopped during a management network interruption.

Answer & Explanations

Correct answer: D

A.

Register a private branch FortiGate using its unroutable internal address from the public internet and assume FortiManager can initiate arbitrary inbound connections through NAT without any session setup. That shortcut risks remote branch management failure after ignoring direction and address reachability of the FGFM channel. Here the specific shortcut is: Reinstall the firewall operating system whenever FortiManager misses one keepalive and assume gateway packet forwarding must have stopped during a management network interruption.

B.

The question is set in this situation: A logistics company replaced its WAN router and needs to correlate NAT session timeouts with FortiManager FGFM keepalive recovery. Delete arbitrary FortiManager database directories and every configuration archive to clear an alarm immediately without checking which files contain active ADOM objects. That shortcut risks irrecoverable management data loss after an uncontrolled disk cleanup removes critical central records. Here the specific shortcut is: Reinstall the firewall operating system whenever FortiManager misses one keepalive and assume gateway packet forwarding must have stopped during a management network interruption.

C.

The question is set in this situation: A logistics company replaced its WAN router and needs to correlate NAT session timeouts with FortiManager FGFM keepalive recovery. Enable maximum debugging indefinitely on all central processes and reboot every gateway on the first error message without preserving or analyzing the relevant FortiManager logs. That shortcut risks lost diagnostic evidence and collateral disruption after uncontrolled debugging and unrelated restarts. Here the specific shortcut is: Reinstall the firewall operating system whenever FortiManager misses one keepalive and assume gateway packet forwarding must have stopped during a management network interruption.

D.

The question is set in this situation: A logistics company replaced its WAN router and needs to correlate NAT session timeouts with FortiManager FGFM keepalive recovery. Reinstall the firewall operating system whenever FortiManager misses one keepalive and assume gateway packet forwarding must have stopped during a management network interruption. The foreseeable failure is unnecessary site outage after a transient FGFM management disconnect is mistaken for a failed firewall. The safer response is: Review FGFM connection and keepalive event history for a disconnected managed FortiGate, correlate it with actual routing and interface reachability, and verify that management reconnection restores device status before pushing changes.

Question 770

A logistics company replaced its WAN router and needs to correlate NAT session timeouts with FortiManager FGFM keepalive recovery. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Review FGFM connection and keepalive event history for a disconnected managed FortiGate, correlate it with actual routing and interface reachability, and verify that management reconnection restores device status before pushing changes. Verify: In a lab simulate a storage threshold alarm, inspect supported filesystem and application usage tools, remove only approved disposable data and confirm policy database and backup integrity remain intact.
  2. Implement: Review FGFM connection and keepalive event history for a disconnected managed FortiGate, correlate it with actual routing and interface reachability, and verify that management reconnection restores device status before pushing changes. Verify: Interrupt only the lab FGFM path, observe keepalive and disconnected status, restore the route and confirm device reconnects and successfully handles a harmless central management request.
  3. Implement: Identify FortiManager partitions, database storage and safe cleanup options when disk usage is high, preserve required configuration backups and audit history, and verify adequate free space before resuming heavy policy tasks. Verify: Interrupt only the lab FGFM path, observe keepalive and disconnected status, restore the route and confirm device reconnects and successfully handles a harmless central management request.
  4. Implement: Collect supported FortiManager process status, system events and narrowly scoped debug output for the affected operation, correlate timestamps and stop temporary diagnostics after identifying a specific service or connectivity issue. Verify: Reproduce a benign stalled policy task on a staging manager, inspect relevant process status and logs, isolate the cause and confirm a targeted correction restores the intended action.

Answer & Explanations

Correct answer: B

A.

The question is set in this situation: A logistics company replaced its WAN router and needs to correlate NAT session timeouts with FortiManager FGFM keepalive recovery. The action is applicable: Review FGFM connection and keepalive event history for a disconnected managed FortiGate, correlate it with actual routing and interface reachability, and verify that management reconnection restores device status before pushing changes. But its proposed test—In a lab simulate a storage threshold alarm, inspect supported filesystem and application usage tools, remove only approved disposable data and confirm policy database and backup integrity remain intact.—addresses “Investigate FortiManager high disk usage and protected log or backup retention”. This requirement is confirmed instead by: Interrupt only the lab FGFM path, observe keepalive and disconnected status, restore the route and confirm device reconnects and successfully handles a harmless central management request.

B.

The question is set in this situation: A logistics company replaced its WAN router and needs to correlate NAT session timeouts with FortiManager FGFM keepalive recovery. Review FGFM connection and keepalive event history for a disconnected managed FortiGate, correlate it with actual routing and interface reachability, and verify that management reconnection restores device status before pushing changes. Confirm it through this test: Interrupt only the lab FGFM path, observe keepalive and disconnected status, restore the route and confirm device reconnects and successfully handles a harmless central management request. FGFM keepalives help detect and maintain central device sessions; a lost keepalive can reflect NAT or network instability without meaning the FortiGate itself stopped enforcing traffic.

C.

The question is set in this situation: A logistics company replaced its WAN router and needs to correlate NAT session timeouts with FortiManager FGFM keepalive recovery. The test would be relevant: Interrupt only the lab FGFM path, observe keepalive and disconnected status, restore the route and confirm device reconnects and successfully handles a harmless central management request. But the offered implementation—Identify FortiManager partitions, database storage and safe cleanup options when disk usage is high, preserve required configuration backups and audit history, and verify adequate free space before resuming heavy policy tasks.—addresses “Investigate FortiManager high disk usage and protected log or backup retention”. The action needed here is: Review FGFM connection and keepalive event history for a disconnected managed FortiGate, correlate it with actual routing and interface reachability, and verify that management reconnection restores device status before pushing changes.

D.

The question is set in this situation: A logistics company replaced its WAN router and needs to correlate NAT session timeouts with FortiManager FGFM keepalive recovery. This action/test pair addresses “Use FortiManager process status and debug evidence for a persistent management fault”. Collect supported FortiManager process status, system events and narrowly scoped debug output for the affected operation, correlate timestamps and stop temporary diagnostics after identifying a specific service or connectivity issue. Reproduce a benign stalled policy task on a staging manager, inspect relevant process status and logs, isolate the cause and confirm a targeted correction restores the intended action. The case instead calls for: Review FGFM connection and keepalive event history for a disconnected managed FortiGate, correlate it with actual routing and interface reachability, and verify that management reconnection restores device status before pushing changes.

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