Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 79
Question 780
A university's FortiManager GUI freezes intermittently while managed FortiGates still pass traffic, requiring central process-level diagnosis. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: A
The question is set in this situation: A university's FortiManager GUI freezes intermittently while managed FortiGates still pass traffic, requiring central process-level diagnosis. Inspect supported FortiManager system resource utilization, current processes and task queue during slow policy edits, identify the actual bottleneck, and plan a targeted approved remediation rather than rebooting unrelated gateways. Confirm it through this test: Generate a safe load on a disposable FortiManager, monitor process and resource counters during a policy task, and show service performance improves after correcting the identified pressure. High manager CPU or memory can delay policy compilation and administrator sessions while FortiGate enforcement remains operational; measuring the management host prevents diagnosing the wrong system.
The question is set in this situation: A university's FortiManager GUI freezes intermittently while managed FortiGates still pass traffic, requiring central process-level diagnosis. The test would be relevant: Generate a safe load on a disposable FortiManager, monitor process and resource counters during a policy task, and show service performance improves after correcting the identified pressure. But the offered implementation—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.—addresses “Use FortiManager process status and debug evidence for a persistent management fault”. The action needed here is: Inspect supported FortiManager system resource utilization, current processes and task queue during slow policy edits, identify the actual bottleneck, and plan a targeted approved remediation rather than rebooting unrelated gateways.
The question is set in this situation: A university's FortiManager GUI freezes intermittently while managed FortiGates still pass traffic, requiring central process-level diagnosis. This action/test pair addresses “Interpret FortiManager FGFM keepalive and recovery events during device reconnect”. 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. 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. The case instead calls for: Inspect supported FortiManager system resource utilization, current processes and task queue during slow policy edits, identify the actual bottleneck, and plan a targeted approved remediation rather than rebooting unrelated gateways.
The question is set in this situation: A university's FortiManager GUI freezes intermittently while managed FortiGates still pass traffic, requiring central process-level diagnosis. The action is applicable: Inspect supported FortiManager system resource utilization, current processes and task queue during slow policy edits, identify the actual bottleneck, and plan a targeted approved remediation rather than rebooting unrelated gateways. But its proposed test—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.—addresses “Use FortiManager process status and debug evidence for a persistent management fault”. This requirement is confirmed instead by: Generate a safe load on a disposable FortiManager, monitor process and resource counters during a policy task, and show service performance improves after correcting the identified pressure.
Question 781
A manufacturing firm sees FortiManager disk utilization approaching capacity and needs to protect its central configuration database during cleanup. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: B
Inspect supported FortiManager system resource utilization, current processes and task queue during slow policy edits, identify the actual bottleneck, and plan a targeted approved remediation rather than rebooting unrelated gateways. This addresses “Use FortiManager CPU and memory diagnostics before restarting management services”, where the governing principle is: High manager CPU or memory can delay policy compilation and administrator sessions while FortiGate enforcement remains operational; measuring the management host prevents diagnosing the wrong system. The stated case instead calls for: 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.
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. 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. Verify the result with this 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.
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. This addresses “Interpret FortiManager FGFM keepalive and recovery events during device reconnect”, where the governing 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. The stated case instead calls for: 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.
Inspect the exact failed installation log, target FortiGate firmware support and generated configuration command, then revise the central object or mapping and rerun a controlled install to only the affected device. This addresses “Use FortiManager failed-install logs to identify a rejected target command”, where the governing principle is: An installation can fail because a generated command is invalid for one firmware or model, even when the management session remains healthy; opening extra management ports does not fix unsupported syntax. The stated case instead calls for: 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.
Question 782
A manufacturing firm sees FortiManager disk utilization approaching capacity and needs to protect its central configuration database during cleanup. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: D
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. That explains “Interpret FortiManager FGFM keepalive and recovery events during device reconnect”, not the mechanism behind the described change. The relevant 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.
An installation can fail because a generated command is invalid for one firmware or model, even when the management session remains healthy; opening extra management ports does not fix unsupported syntax. That explains “Use FortiManager failed-install logs to identify a rejected target command”, not the mechanism behind the described change. The relevant principle is: 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.
High manager CPU or memory can delay policy compilation and administrator sessions while FortiGate enforcement remains operational; measuring the management host prevents diagnosing the wrong system. That explains “Use FortiManager CPU and memory diagnostics before restarting management services”, not the mechanism behind the described change. The relevant 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.
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 corresponding implementation is: 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.
Question 783
A manufacturing firm sees FortiManager disk utilization approaching capacity and needs to protect its central configuration database during cleanup. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: C
Install a harmless test package containing one unsupported setting to a compatible staging target, capture the device rejection and confirm the corrected generated configuration installs cleanly. That would help test “Use FortiManager failed-install logs to identify a rejected target command”, not the outcome required in this scenario. The relevant acceptance check is: 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.
Generate a safe load on a disposable FortiManager, monitor process and resource counters during a policy task, and show service performance improves after correcting the identified pressure. That would help test “Use FortiManager CPU and memory diagnostics before restarting management services”, not the outcome required in this scenario. The relevant acceptance check is: 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.
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. This check is decisive because 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.
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. That would help test “Interpret FortiManager FGFM keepalive and recovery events during device reconnect”, not the outcome required in this scenario. The relevant acceptance check is: 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.
Question 784
A manufacturing firm sees FortiManager disk utilization approaching capacity and needs to protect its central configuration database during cleanup. Which proposed shortcut most directly risks irrecoverable management data loss after an uncontrolled disk cleanup removes critical central records and should therefore be rejected?
Answer & Explanations
Correct answer: A
Delete arbitrary FortiManager database directories and every configuration archive to clear an alarm immediately without checking which files contain active ADOM objects. The foreseeable failure is irrecoverable management data loss after an uncontrolled disk cleanup removes critical central records. The safer response is: 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.
Reinstall the firewall operating system whenever FortiManager misses one keepalive and assume gateway packet forwarding must have stopped during a management network interruption. That shortcut risks unnecessary site outage after a transient FGFM management disconnect is mistaken for a failed firewall. Here the specific shortcut is: Delete arbitrary FortiManager database directories and every configuration archive to clear an alarm immediately without checking which files contain active ADOM objects.
Disable all branch firewall filtering whenever FortiManager logs a command syntax error and assume unrestricted network access will make the invalid command acceptable. That shortcut risks continued policy installation failure and unnecessary exposure after treating device syntax rejection as a network problem. Here the specific shortcut is: Delete arbitrary FortiManager database directories and every configuration archive to clear an alarm immediately without checking which files contain active ADOM objects.
Reboot all customer FortiGates because FortiManager's web interface responds slowly, without checking whether the manager has exhausted CPU or memory. That shortcut risks widespread customer disruption when central management performance problems trigger unrelated firewall restarts. Here the specific shortcut is: Delete arbitrary FortiManager database directories and every configuration archive to clear an alarm immediately without checking which files contain active ADOM objects.
Question 785
A manufacturing firm sees FortiManager disk utilization approaching capacity and needs to protect its central configuration database during cleanup. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: D
The action is applicable: 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. But its proposed 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.—addresses “Interpret FortiManager FGFM keepalive and recovery events during device reconnect”. This requirement is confirmed instead by: 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.
The test would be relevant: 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. But the offered implementation—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.—addresses “Interpret FortiManager FGFM keepalive and recovery events during device reconnect”. The action needed here is: 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 action/test pair addresses “Use FortiManager CPU and memory diagnostics before restarting management services”. Inspect supported FortiManager system resource utilization, current processes and task queue during slow policy edits, identify the actual bottleneck, and plan a targeted approved remediation rather than rebooting unrelated gateways. Generate a safe load on a disposable FortiManager, monitor process and resource counters during a policy task, and show service performance improves after correcting the identified pressure. The case instead calls for: 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.
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. Confirm it through this 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. 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.
Question 786
A managed services provider requires a safe high-disk troubleshooting plan that preserves customer policy revisions and compliance evidence. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: C
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. This addresses “Restore a managed FortiGate's device database without overwriting independent ADOM changes”, where the governing principle is: 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. The stated case instead calls for: 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.
The question is set in this situation: A managed services provider requires a safe high-disk troubleshooting plan that preserves customer policy revisions and compliance evidence. 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. This addresses “Interpret FortiManager FGFM keepalive and recovery events during device reconnect”, where the governing 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. The stated case instead calls for: 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.
The question is set in this situation: A managed services provider requires a safe high-disk troubleshooting plan that preserves customer policy revisions and compliance evidence. 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. 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. Verify the result with this 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.
The question is set in this situation: A managed services provider requires a safe high-disk troubleshooting plan that preserves customer policy revisions and compliance evidence. Inspect supported FortiManager system resource utilization, current processes and task queue during slow policy edits, identify the actual bottleneck, and plan a targeted approved remediation rather than rebooting unrelated gateways. This addresses “Use FortiManager CPU and memory diagnostics before restarting management services”, where the governing principle is: High manager CPU or memory can delay policy compilation and administrator sessions while FortiGate enforcement remains operational; measuring the management host prevents diagnosing the wrong system. The stated case instead calls for: 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.
Question 787
A managed services provider requires a safe high-disk troubleshooting plan that preserves customer policy revisions and compliance evidence. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: B
The question is set in this situation: A managed services provider requires a safe high-disk troubleshooting plan that preserves customer policy revisions and compliance evidence. High manager CPU or memory can delay policy compilation and administrator sessions while FortiGate enforcement remains operational; measuring the management host prevents diagnosing the wrong system. That explains “Use FortiManager CPU and memory diagnostics before restarting management services”, not the mechanism behind the described change. The relevant 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 question is set in this situation: A managed services provider requires a safe high-disk troubleshooting plan that preserves customer policy revisions and compliance evidence. 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 corresponding implementation is: 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.
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. That explains “Restore a managed FortiGate's device database without overwriting independent ADOM changes”, not the mechanism behind the described change. The relevant 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 question is set in this situation: A managed services provider requires a safe high-disk troubleshooting plan that preserves customer policy revisions and compliance evidence. 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. That explains “Interpret FortiManager FGFM keepalive and recovery events during device reconnect”, not the mechanism behind the described change. The relevant 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.
Question 788
A managed services provider requires a safe high-disk troubleshooting plan that preserves customer policy revisions and compliance evidence. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: A
The question is set in this situation: A managed services provider requires a safe high-disk troubleshooting plan that preserves customer policy revisions and compliance evidence. 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. This check is decisive because 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 question is set in this situation: A managed services provider requires a safe high-disk troubleshooting plan that preserves customer policy revisions and compliance evidence. Generate a safe load on a disposable FortiManager, monitor process and resource counters during a policy task, and show service performance improves after correcting the identified pressure. That would help test “Use FortiManager CPU and memory diagnostics before restarting management services”, not the outcome required in this scenario. The relevant acceptance check is: 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.
The question is set in this situation: A managed services provider requires a safe high-disk troubleshooting plan that preserves customer policy revisions and compliance evidence. 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. That would help test “Interpret FortiManager FGFM keepalive and recovery events during device reconnect”, not the outcome required in this scenario. The relevant acceptance check is: 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.
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. That would help test “Restore a managed FortiGate's device database without overwriting independent ADOM changes”, not the outcome required in this scenario. The relevant acceptance check is: 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.
Question 789
A managed services provider requires a safe high-disk troubleshooting plan that preserves customer policy revisions and compliance evidence. Which proposed shortcut most directly risks irrecoverable management data loss after an uncontrolled disk cleanup removes critical central records and should therefore be rejected?
Answer & Explanations
Correct answer: C
The question is set in this situation: A managed services provider requires a safe high-disk troubleshooting plan that preserves customer policy revisions and compliance evidence. Reboot all customer FortiGates because FortiManager's web interface responds slowly, without checking whether the manager has exhausted CPU or memory. That shortcut risks widespread customer disruption when central management performance problems trigger unrelated firewall restarts. Here the specific shortcut is: Delete arbitrary FortiManager database directories and every configuration archive to clear an alarm immediately without checking which files contain active ADOM objects.
Restore the entire FortiManager global database because one branch FortiGate's interface description is incorrect and assume no other tenants or policies can be affected. That shortcut risks unrelated policy rollback and cross-tenant disruption after a device-only problem is treated as global management recovery. Here the specific shortcut is: Delete arbitrary FortiManager database directories and every configuration archive to clear an alarm immediately without checking which files contain active ADOM objects.
The question is set in this situation: A managed services provider requires a safe high-disk troubleshooting plan that preserves customer policy revisions and compliance evidence. Delete arbitrary FortiManager database directories and every configuration archive to clear an alarm immediately without checking which files contain active ADOM objects. The foreseeable failure is irrecoverable management data loss after an uncontrolled disk cleanup removes critical central records. The safer response is: 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.
The question is set in this situation: A managed services provider requires a safe high-disk troubleshooting plan that preserves customer policy revisions and compliance evidence. Reinstall the firewall operating system whenever FortiManager misses one keepalive and assume gateway packet forwarding must have stopped during a management network interruption. That shortcut risks unnecessary site outage after a transient FGFM management disconnect is mistaken for a failed firewall. Here the specific shortcut is: Delete arbitrary FortiManager database directories and every configuration archive to clear an alarm immediately without checking which files contain active ADOM objects.
Question 790
A managed services provider requires a safe high-disk troubleshooting plan that preserves customer policy revisions and compliance evidence. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: D
The question is set in this situation: A managed services provider requires a safe high-disk troubleshooting plan that preserves customer policy revisions and compliance evidence. The test would be relevant: 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. But the offered implementation—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.—addresses “Interpret FortiManager FGFM keepalive and recovery events during device reconnect”. The action needed here is: 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.
The question is set in this situation: A managed services provider requires a safe high-disk troubleshooting plan that preserves customer policy revisions and compliance evidence. This action/test pair addresses “Use FortiManager CPU and memory diagnostics before restarting management services”. Inspect supported FortiManager system resource utilization, current processes and task queue during slow policy edits, identify the actual bottleneck, and plan a targeted approved remediation rather than rebooting unrelated gateways. Generate a safe load on a disposable FortiManager, monitor process and resource counters during a policy task, and show service performance improves after correcting the identified pressure. The case instead calls for: 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.
The question is set in this situation: A managed services provider requires a safe high-disk troubleshooting plan that preserves customer policy revisions and compliance evidence. The action is applicable: 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. But its proposed 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.—addresses “Interpret FortiManager FGFM keepalive and recovery events during device reconnect”. This requirement is confirmed instead by: 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.
The question is set in this situation: A managed services provider requires a safe high-disk troubleshooting plan that preserves customer policy revisions and compliance evidence. 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. Confirm it through this 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. 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.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- Fortinet FCP_FMG_AD-7.6 Practice Test 77 - 10 Questions (Last Reviewed 01-Nov-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 78 - 10 Questions (Last Reviewed 31-Oct-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 79 - 10 Questions (Last Reviewed 30-Oct-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 80 - 10 Questions (Last Reviewed 29-Oct-2026)