Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 78
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?
Answer & Explanations
Correct answer: 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. 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.
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.
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.
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.
Question 771
A bank's FortiManager policy installation queue is slow during business hours and operations must investigate central CPU and memory before modifying branch firewalls. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: A
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. 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. Verify the result with 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.
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: 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.
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: 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.
Use supported FortiManager filesystem and database status diagnostics after storage or power faults, verify backups and snapshots, and perform documented recovery before trusting policy histories or large-scale install operations. This addresses “Confirm FortiManager database recovery after power failure before rebuilding policies”, where the governing principle is: A central management database can be inconsistent while registered FortiGates continue enforcing old policies; a healthy firewall data plane therefore does not demonstrate the manager's database is safe to use. The stated case instead calls for: Inspect 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.
Question 772
A bank's FortiManager policy installation queue is slow during business hours and operations must investigate central CPU and memory before modifying branch firewalls. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: C
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: 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.
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: 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.
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 corresponding implementation 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.
A central management database can be inconsistent while registered FortiGates continue enforcing old policies; a healthy firewall data plane therefore does not demonstrate the manager's database is safe to use. That explains “Confirm FortiManager database recovery after power failure before rebuilding policies”, not the mechanism behind the described change. The relevant principle is: 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.
Question 773
A bank's FortiManager policy installation queue is slow during business hours and operations must investigate central CPU and memory before modifying branch firewalls. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: A
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. This check is decisive because 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.
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: 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.
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: 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.
In a nonproduction failure rehearsal compare central ADOM revision availability, filesystem checks and backup integrity, restore a known configuration if required and perform one harmless device install. That would help test “Confirm FortiManager database recovery after power failure before rebuilding policies”, not the outcome required in this scenario. The relevant acceptance check is: 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 774
A bank's FortiManager policy installation queue is slow during business hours and operations must investigate central CPU and memory before modifying branch firewalls. Which proposed shortcut most directly risks widespread customer disruption when central management performance problems trigger unrelated firewall restarts and should therefore be rejected?
Answer & Explanations
Correct answer: B
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: Reboot all customer FortiGates because FortiManager's web interface responds slowly, without checking whether the manager has exhausted CPU or memory.
Reboot all customer FortiGates because FortiManager's web interface responds slowly, without checking whether the manager has exhausted CPU or memory. The foreseeable failure is widespread customer disruption when central management performance problems trigger unrelated firewall restarts. The safer response 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.
Delete recent FortiManager backup files to free disk after a crash and assume the device inventory screenshot proves its central object database is fully recoverable. That shortcut risks loss of management revision and policy recovery capability after corruption warning is ignored and backups are removed. Here the specific shortcut is: Reboot all customer FortiGates because FortiManager's web interface responds slowly, without checking whether the manager has exhausted CPU or memory.
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: Reboot all customer FortiGates because FortiManager's web interface responds slowly, without checking whether the manager has exhausted CPU or memory.
Question 775
A bank's FortiManager policy installation queue is slow during business hours and operations must investigate central CPU and memory before modifying branch firewalls. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: C
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.
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.
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.
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.
Question 776
A university's FortiManager GUI freezes intermittently while managed FortiGates still pass traffic, requiring central process-level diagnosis. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: D
When FortiManager is behind an upstream NAT device, plan the correct reachable management endpoint and supported FGFM routing and firewall rules, then test registration and policy delivery from an actual external FortiGate. This addresses “Diagnose FortiManager behind-NAT connectivity for managed remote FortiGates”, where the governing principle is: A private management IP may respond locally while a remote gateway cannot establish FGFM to the translated address; an HTTPS port-forward test alone does not prove management control traffic and identity are correct. The stated case instead calls for: Inspect 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. 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: 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. 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: 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. 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. 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. Verify the result with 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.
Question 777
A university's FortiManager GUI freezes intermittently while managed FortiGates still pass traffic, requiring central process-level diagnosis. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: B
A private management IP may respond locally while a remote gateway cannot establish FGFM to the translated address; an HTTPS port-forward test alone does not prove management control traffic and identity are correct. That explains “Diagnose FortiManager behind-NAT connectivity for managed remote FortiGates”, not the mechanism behind the described change. The relevant principle is: 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. 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 corresponding implementation 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. 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: 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. 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: 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.
Question 778
A university's FortiManager GUI freezes intermittently while managed FortiGates still pass traffic, requiring central process-level diagnosis. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: D
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. 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: 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 question is set in this situation: A university's FortiManager GUI freezes intermittently while managed FortiGates still pass traffic, requiring central process-level diagnosis. 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: 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.
From a branch lab firewall test the intended external manager address, inspect upstream NAT and FGFM session state, authorize registration and complete a harmless policy install. That would help test “Diagnose FortiManager behind-NAT connectivity for managed remote FortiGates”, not the outcome required in this scenario. The relevant acceptance check is: 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 question is set in this situation: A university's FortiManager GUI freezes intermittently while managed FortiGates still pass traffic, requiring central process-level diagnosis. 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. This check is decisive because 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.
Question 779
A university's FortiManager GUI freezes intermittently while managed FortiGates still pass traffic, requiring central process-level diagnosis. Which proposed shortcut most directly risks widespread customer disruption when central management performance problems trigger unrelated firewall restarts and should therefore be rejected?
Answer & Explanations
Correct answer: C
Ping the FortiManager from its own private subnet and declare all remote FortiGates correctly managed through the public NAT path without any branch-side FGFM test. That shortcut risks unreachable central policy control after an address translation hides the actual management server from remote branches. Here the specific shortcut is: Reboot all customer FortiGates because FortiManager's web interface responds slowly, without checking whether the manager has exhausted CPU or memory.
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. 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: Reboot all customer FortiGates because FortiManager's web interface responds slowly, without checking whether the manager has exhausted CPU or memory.
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. Reboot all customer FortiGates because FortiManager's web interface responds slowly, without checking whether the manager has exhausted CPU or memory. The foreseeable failure is widespread customer disruption when central management performance problems trigger unrelated firewall restarts. The safer response 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. 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: Reboot all customer FortiGates because FortiManager's web interface responds slowly, without checking whether the manager has exhausted CPU or memory.
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.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- Fortinet FCP_FMG_AD-7.6 Practice Test 76 - 10 Questions (Last Reviewed 02-Nov-2026)
- 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)