Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 80
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.
Question 791
A regional hospital reports intermittent FortiManager policy-task errors and needs a support-ready evidence package that does not expose customer credentials. 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: 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.
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. 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. Verify the result with this 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.
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: 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.
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: 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.
Question 792
A regional hospital reports intermittent FortiManager policy-task errors and needs a support-ready evidence package that does not expose customer credentials. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: A
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 corresponding implementation is: 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.
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: 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.
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: 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.
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: 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.
Question 793
A regional hospital reports intermittent FortiManager policy-task errors and needs a support-ready evidence package that does not expose customer credentials. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: D
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: 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.
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: 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.
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: 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.
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. This check is decisive because 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.
Question 794
A regional hospital reports intermittent FortiManager policy-task errors and needs a support-ready evidence package that does not expose customer credentials. Which proposed shortcut most directly risks lost diagnostic evidence and collateral disruption after uncontrolled debugging and unrelated restarts and should therefore be rejected?
Answer & Explanations
Correct answer: B
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: 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.
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. The foreseeable failure is lost diagnostic evidence and collateral disruption after uncontrolled debugging and unrelated restarts. The safer response is: 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.
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: 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.
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: 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.
Question 795
A regional hospital reports intermittent FortiManager policy-task errors and needs a support-ready evidence package that does not expose customer credentials. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: A
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. Confirm it through this 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. 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 test would be relevant: 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. But the offered implementation—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.—addresses “Use FortiManager CPU and memory diagnostics before restarting management services”. The action needed here is: 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.
The action is applicable: 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. But its proposed 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.—addresses “Use FortiManager CPU and memory diagnostics before restarting management services”. This requirement is confirmed instead by: 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.
This action/test pair addresses “Investigate FortiManager high disk usage and protected log or backup retention”. 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. 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 case instead calls for: 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.
Question 796
A university's FortiManager administrator sees recurring API operation failures and must distinguish service process health from managed FortiGate packet-forwarding status. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: C
The question is set in this situation: A university's FortiManager administrator sees recurring API operation failures and must distinguish service process health from managed FortiGate packet-forwarding status. 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: 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.
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: 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.
The question is set in this situation: A university's FortiManager administrator sees recurring API operation failures and must distinguish service process health from managed FortiGate packet-forwarding status. 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. 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. Verify the result with this 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.
The question is set in this situation: A university's FortiManager administrator sees recurring API operation failures and must distinguish service process health from managed FortiGate packet-forwarding status. 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: 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.
Question 797
A university's FortiManager administrator sees recurring API operation failures and must distinguish service process health from managed FortiGate packet-forwarding status. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: B
The question is set in this situation: A university's FortiManager administrator sees recurring API operation failures and must distinguish service process health from managed FortiGate packet-forwarding status. 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: 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 question is set in this situation: A university's FortiManager administrator sees recurring API operation failures and must distinguish service process health from managed FortiGate packet-forwarding status. 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 corresponding implementation is: 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.
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: 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 question is set in this situation: A university's FortiManager administrator sees recurring API operation failures and must distinguish service process health from managed FortiGate packet-forwarding status. 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: 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.
Question 798
A university's FortiManager administrator sees recurring API operation failures and must distinguish service process health from managed FortiGate packet-forwarding status. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: D
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: 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 question is set in this situation: A university's FortiManager administrator sees recurring API operation failures and must distinguish service process health from managed FortiGate packet-forwarding status. 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: 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 question is set in this situation: A university's FortiManager administrator sees recurring API operation failures and must distinguish service process health from managed FortiGate packet-forwarding status. 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: 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 question is set in this situation: A university's FortiManager administrator sees recurring API operation failures and must distinguish service process health from managed FortiGate packet-forwarding status. 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. This check is decisive because 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.
Question 799
A university's FortiManager administrator sees recurring API operation failures and must distinguish service process health from managed FortiGate packet-forwarding status. Which proposed shortcut most directly risks lost diagnostic evidence and collateral disruption after uncontrolled debugging and unrelated restarts and should therefore be rejected?
Answer & Explanations
Correct answer: C
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: 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.
The question is set in this situation: A university's FortiManager administrator sees recurring API operation failures and must distinguish service process health from managed FortiGate packet-forwarding status. 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: 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.
The question is set in this situation: A university's FortiManager administrator sees recurring API operation failures and must distinguish service process health from managed FortiGate packet-forwarding status. 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. The foreseeable failure is lost diagnostic evidence and collateral disruption after uncontrolled debugging and unrelated restarts. The safer response is: 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.
The question is set in this situation: A university's FortiManager administrator sees recurring API operation failures and must distinguish service process health from managed FortiGate packet-forwarding status. 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: 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.
Question 800
A university's FortiManager administrator sees recurring API operation failures and must distinguish service process health from managed FortiGate packet-forwarding status. 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 administrator sees recurring API operation failures and must distinguish service process health from managed FortiGate packet-forwarding status. 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. Confirm it through this 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. 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 question is set in this situation: A university's FortiManager administrator sees recurring API operation failures and must distinguish service process health from managed FortiGate packet-forwarding status. The action is applicable: 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. But its proposed 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.—addresses “Use FortiManager CPU and memory diagnostics before restarting management services”. This requirement is confirmed instead by: 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 question is set in this situation: A university's FortiManager administrator sees recurring API operation failures and must distinguish service process health from managed FortiGate packet-forwarding status. This action/test pair addresses “Investigate FortiManager high disk usage and protected log or backup retention”. 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. 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 case instead calls for: 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.
The question is set in this situation: A university's FortiManager administrator sees recurring API operation failures and must distinguish service process health from managed FortiGate packet-forwarding status. The test would be relevant: 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. But the offered implementation—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.—addresses “Use FortiManager CPU and memory diagnostics before restarting management services”. The action needed here is: 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.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- 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)