Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 58
Question 570
A bank is designing management disaster recovery and must independently evaluate FortiManager database continuity and branch FortiGate HA availability. 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 bank is designing management disaster recovery and must independently evaluate FortiManager database continuity and branch FortiGate HA availability. Deploy a supported FortiManager high-availability management pair with compatible software, defined primary and secondary management roles, tested synchronization and documented operator recovery procedures separate from managed FortiGate HA. Confirm it through this test: In a staging topology confirm FortiManager peer synchronization and management service recovery while separately testing FortiGate forwarding under its installed policy and recording which component failed. FortiManager HA protects the central configuration management service and databases; it is not the same as FortiGate gateway clustering, so it does not automatically preserve data-plane packet forwarding for a single gateway.
The action is applicable: Deploy a supported FortiManager high-availability management pair with compatible software, defined primary and secondary management roles, tested synchronization and documented operator recovery procedures separate from managed FortiGate HA. But its proposed test—In an isolated lab fail the active management peer under a supported procedure, verify the expected surviving peer takes the correct role and demonstrate a harmless controlled policy installation to one test gateway.—addresses “Rehearse supported FortiManager HA failover and operator access recovery”. This requirement is confirmed instead by: In a staging topology confirm FortiManager peer synchronization and management service recovery while separately testing FortiGate forwarding under its installed policy and recording which component failed.
The test would be relevant: In a staging topology confirm FortiManager peer synchronization and management service recovery while separately testing FortiGate forwarding under its installed policy and recording which component failed. But the offered implementation—Plan a supported FortiManager HA failover test including management endpoint reachability, administrator login, database state and FGFM recovery for a pilot FortiGate, then document the observed behavior and required operator actions.—addresses “Rehearse supported FortiManager HA failover and operator access recovery”. The action needed here is: Deploy a supported FortiManager high-availability management pair with compatible software, defined primary and secondary management roles, tested synchronization and documented operator recovery procedures separate from managed FortiGate HA.
This action/test pair addresses “Monitor FortiManager HA synchronization and correctly interpret peer health”. Check supported FortiManager HA synchronization status, software compatibility and management peer communication before approving failover, and investigate replication errors rather than assuming a reachable secondary has current databases. Publish a harmless ADOM object on a lab primary, inspect synchronization completion on the secondary, then interrupt a test management link and verify the HA health alarm reflects the fault. The case instead calls for: Deploy a supported FortiManager high-availability management pair with compatible software, defined primary and secondary management roles, tested synchronization and documented operator recovery procedures separate from managed FortiGate HA.
Question 571
A nationwide insurer checks whether its FortiManager standby contains recent policy and object approvals before a planned primary appliance upgrade. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: D
Plan a supported FortiManager HA failover test including management endpoint reachability, administrator login, database state and FGFM recovery for a pilot FortiGate, then document the observed behavior and required operator actions. This addresses “Rehearse supported FortiManager HA failover and operator access recovery”, where the governing principle is: An HA transition may involve changes in which management peer owns connections; successful web access alone does not demonstrate managed gateways reconnect and policy installs work under the new management authority. The stated case instead calls for: Check supported FortiManager HA synchronization status, software compatibility and management peer communication before approving failover, and investigate replication errors rather than assuming a reachable secondary has current databases.
Inspect FortiManager's managed FortiGate contract state, local available FortiGuard content and supported firmware cache before scheduling security signature or firmware rollout, and correct missing entitlements or version compatibility first. This addresses “Validate FortiGuard license status and firmware cache before a central update”, where the governing principle is: A centrally cached package cannot grant a missing FortiGuard license or make an unsupported FortiOS image installable; device contract and target-version prerequisites remain separate gates. The stated case instead calls for: Check supported FortiManager HA synchronization status, software compatibility and management peer communication before approving failover, and investigate replication errors rather than assuming a reachable secondary has current databases.
Deploy a supported FortiManager high-availability management pair with compatible software, defined primary and secondary management roles, tested synchronization and documented operator recovery procedures separate from managed FortiGate HA. This addresses “Configure FortiManager high availability independently of FortiGate cluster HA”, where the governing principle is: FortiManager HA protects the central configuration management service and databases; it is not the same as FortiGate gateway clustering, so it does not automatically preserve data-plane packet forwarding for a single gateway. The stated case instead calls for: Check supported FortiManager HA synchronization status, software compatibility and management peer communication before approving failover, and investigate replication errors rather than assuming a reachable secondary has current databases.
Check supported FortiManager HA synchronization status, software compatibility and management peer communication before approving failover, and investigate replication errors rather than assuming a reachable secondary has current databases. A standby management server may be powered on while holding stale configuration or revisions; application and HA synchronization checks are required to establish that a recovery peer can manage recent policy packages. Verify the result with this test: Publish a harmless ADOM object on a lab primary, inspect synchronization completion on the secondary, then interrupt a test management link and verify the HA health alarm reflects the fault.
Question 572
A nationwide insurer checks whether its FortiManager standby contains recent policy and object approvals before a planned primary appliance upgrade. The engineer proposes the following change: Check supported FortiManager HA synchronization status, software compatibility and management peer communication before approving failover, and investigate replication errors rather than assuming a reachable secondary has current databases. Which mechanism explains why it works?
Answer & Explanations
Correct answer: B
A centrally cached package cannot grant a missing FortiGuard license or make an unsupported FortiOS image installable; device contract and target-version prerequisites remain separate gates. That explains “Validate FortiGuard license status and firmware cache before a central update”, not the mechanism behind the described change. The relevant principle is: A standby management server may be powered on while holding stale configuration or revisions; application and HA synchronization checks are required to establish that a recovery peer can manage recent policy packages.
A standby management server may be powered on while holding stale configuration or revisions; application and HA synchronization checks are required to establish that a recovery peer can manage recent policy packages. The corresponding implementation is: Check supported FortiManager HA synchronization status, software compatibility and management peer communication before approving failover, and investigate replication errors rather than assuming a reachable secondary has current databases.
An HA transition may involve changes in which management peer owns connections; successful web access alone does not demonstrate managed gateways reconnect and policy installs work under the new management authority. That explains “Rehearse supported FortiManager HA failover and operator access recovery”, not the mechanism behind the described change. The relevant principle is: A standby management server may be powered on while holding stale configuration or revisions; application and HA synchronization checks are required to establish that a recovery peer can manage recent policy packages.
FortiManager HA protects the central configuration management service and databases; it is not the same as FortiGate gateway clustering, so it does not automatically preserve data-plane packet forwarding for a single gateway. That explains “Configure FortiManager high availability independently of FortiGate cluster HA”, not the mechanism behind the described change. The relevant principle is: A standby management server may be powered on while holding stale configuration or revisions; application and HA synchronization checks are required to establish that a recovery peer can manage recent policy packages.
Question 573
A nationwide insurer checks whether its FortiManager standby contains recent policy and object approvals before a planned primary appliance upgrade. After implementing this change—Check supported FortiManager HA synchronization status, software compatibility and management peer communication before approving failover, and investigate replication errors rather than assuming a reachable secondary has current databases.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: C
In a staging topology confirm FortiManager peer synchronization and management service recovery while separately testing FortiGate forwarding under its installed policy and recording which component failed. That would help test “Configure FortiManager high availability independently of FortiGate cluster HA”, not the outcome required in this scenario. The relevant acceptance check is: Publish a harmless ADOM object on a lab primary, inspect synchronization completion on the secondary, then interrupt a test management link and verify the HA health alarm reflects the fault.
For a staging FortiGate confirm displayed contract status and currently available package version, prepare a compatible firmware image, and verify the authorized update completes with correct post-update status. That would help test “Validate FortiGuard license status and firmware cache before a central update”, not the outcome required in this scenario. The relevant acceptance check is: Publish a harmless ADOM object on a lab primary, inspect synchronization completion on the secondary, then interrupt a test management link and verify the HA health alarm reflects the fault.
Publish a harmless ADOM object on a lab primary, inspect synchronization completion on the secondary, then interrupt a test management link and verify the HA health alarm reflects the fault. This check is decisive because a standby management server may be powered on while holding stale configuration or revisions; application and HA synchronization checks are required to establish that a recovery peer can manage recent policy packages.
In an isolated lab fail the active management peer under a supported procedure, verify the expected surviving peer takes the correct role and demonstrate a harmless controlled policy installation to one test gateway. That would help test “Rehearse supported FortiManager HA failover and operator access recovery”, not the outcome required in this scenario. The relevant acceptance check is: Publish a harmless ADOM object on a lab primary, inspect synchronization completion on the secondary, then interrupt a test management link and verify the HA health alarm reflects the fault.
Question 574
A nationwide insurer checks whether its FortiManager standby contains recent policy and object approvals before a planned primary appliance upgrade. Which proposed shortcut most directly risks outdated central policy and inability to administer gateways after management recovery from an unsynchronized peer and should therefore be rejected?
Answer & Explanations
Correct answer: B
Purchase a secondary FortiManager and claim that a lone FortiGate on the network now has redundant packet-processing hardware without configuring gateway HA. That shortcut risks unprotected network data path when management-server redundancy is mistaken for firewall gateway clustering. Here the specific shortcut is: Accept a secondary FortiManager as fully protected merely because its management web login opens, without checking that recent package and device database revisions were synchronized.
Accept a secondary FortiManager as fully protected merely because its management web login opens, without checking that recent package and device database revisions were synchronized. The foreseeable failure is outdated central policy and inability to administer gateways after management recovery from an unsynchronized peer. The safer response is: Check supported FortiManager HA synchronization status, software compatibility and management peer communication before approving failover, and investigate replication errors rather than assuming a reachable secondary has current databases.
After an HA alarm assume all FortiGate traffic and FortiManager control functions have recovered without testing device reconnection, administrator permissions or a policy operation. That shortcut risks prolonged central management outage because failover was declared healthy from a single reachability check. Here the specific shortcut is: Accept a secondary FortiManager as fully protected merely because its management web login opens, without checking that recent package and device database revisions were synchronized.
Download an arbitrary firmware image into FortiManager and claim every managed FortiGate now has valid security service subscriptions and is updated without device-specific checks. That shortcut risks failed update rollout and overstated signature protection after ignoring licensing, package availability and firmware compatibility. Here the specific shortcut is: Accept a secondary FortiManager as fully protected merely because its management web login opens, without checking that recent package and device database revisions were synchronized.
Question 575
A nationwide insurer checks whether its FortiManager standby contains recent policy and object approvals before a planned primary appliance upgrade. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: D
The action is applicable: Check supported FortiManager HA synchronization status, software compatibility and management peer communication before approving failover, and investigate replication errors rather than assuming a reachable secondary has current databases. But its proposed test—In an isolated lab fail the active management peer under a supported procedure, verify the expected surviving peer takes the correct role and demonstrate a harmless controlled policy installation to one test gateway.—addresses “Rehearse supported FortiManager HA failover and operator access recovery”. This requirement is confirmed instead by: Publish a harmless ADOM object on a lab primary, inspect synchronization completion on the secondary, then interrupt a test management link and verify the HA health alarm reflects the fault.
The test would be relevant: Publish a harmless ADOM object on a lab primary, inspect synchronization completion on the secondary, then interrupt a test management link and verify the HA health alarm reflects the fault. But the offered implementation—Plan a supported FortiManager HA failover test including management endpoint reachability, administrator login, database state and FGFM recovery for a pilot FortiGate, then document the observed behavior and required operator actions.—addresses “Rehearse supported FortiManager HA failover and operator access recovery”. The action needed here is: Check supported FortiManager HA synchronization status, software compatibility and management peer communication before approving failover, and investigate replication errors rather than assuming a reachable secondary has current databases.
This action/test pair addresses “Configure FortiManager high availability independently of FortiGate cluster HA”. Deploy a supported FortiManager high-availability management pair with compatible software, defined primary and secondary management roles, tested synchronization and documented operator recovery procedures separate from managed FortiGate HA. In a staging topology confirm FortiManager peer synchronization and management service recovery while separately testing FortiGate forwarding under its installed policy and recording which component failed. The case instead calls for: Check supported FortiManager HA synchronization status, software compatibility and management peer communication before approving failover, and investigate replication errors rather than assuming a reachable secondary has current databases.
Check supported FortiManager HA synchronization status, software compatibility and management peer communication before approving failover, and investigate replication errors rather than assuming a reachable secondary has current databases. Confirm it through this test: Publish a harmless ADOM object on a lab primary, inspect synchronization completion on the secondary, then interrupt a test management link and verify the HA health alarm reflects the fault. A standby management server may be powered on while holding stale configuration or revisions; application and HA synchronization checks are required to establish that a recovery peer can manage recent policy packages.
Question 576
A university discovers its secondary FortiManager is reachable but may lack a recent ADOM revision and needs proof of database synchronization. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: A
The question is set in this situation: A university discovers its secondary FortiManager is reachable but may lack a recent ADOM revision and needs proof of database synchronization. Check supported FortiManager HA synchronization status, software compatibility and management peer communication before approving failover, and investigate replication errors rather than assuming a reachable secondary has current databases. A standby management server may be powered on while holding stale configuration or revisions; application and HA synchronization checks are required to establish that a recovery peer can manage recent policy packages. Verify the result with this test: Publish a harmless ADOM object on a lab primary, inspect synchronization completion on the secondary, then interrupt a test management link and verify the HA health alarm reflects the fault.
The question is set in this situation: A university discovers its secondary FortiManager is reachable but may lack a recent ADOM revision and needs proof of database synchronization. Inspect FortiManager's managed FortiGate contract state, local available FortiGuard content and supported firmware cache before scheduling security signature or firmware rollout, and correct missing entitlements or version compatibility first. This addresses “Validate FortiGuard license status and firmware cache before a central update”, where the governing principle is: A centrally cached package cannot grant a missing FortiGuard license or make an unsupported FortiOS image installable; device contract and target-version prerequisites remain separate gates. The stated case instead calls for: Check supported FortiManager HA synchronization status, software compatibility and management peer communication before approving failover, and investigate replication errors rather than assuming a reachable secondary has current databases.
The question is set in this situation: A university discovers its secondary FortiManager is reachable but may lack a recent ADOM revision and needs proof of database synchronization. Plan a supported FortiManager HA failover test including management endpoint reachability, administrator login, database state and FGFM recovery for a pilot FortiGate, then document the observed behavior and required operator actions. This addresses “Rehearse supported FortiManager HA failover and operator access recovery”, where the governing principle is: An HA transition may involve changes in which management peer owns connections; successful web access alone does not demonstrate managed gateways reconnect and policy installs work under the new management authority. The stated case instead calls for: Check supported FortiManager HA synchronization status, software compatibility and management peer communication before approving failover, and investigate replication errors rather than assuming a reachable secondary has current databases.
The question is set in this situation: A university discovers its secondary FortiManager is reachable but may lack a recent ADOM revision and needs proof of database synchronization. Deploy a supported FortiManager high-availability management pair with compatible software, defined primary and secondary management roles, tested synchronization and documented operator recovery procedures separate from managed FortiGate HA. This addresses “Configure FortiManager high availability independently of FortiGate cluster HA”, where the governing principle is: FortiManager HA protects the central configuration management service and databases; it is not the same as FortiGate gateway clustering, so it does not automatically preserve data-plane packet forwarding for a single gateway. The stated case instead calls for: Check supported FortiManager HA synchronization status, software compatibility and management peer communication before approving failover, and investigate replication errors rather than assuming a reachable secondary has current databases.
Question 577
A university discovers its secondary FortiManager is reachable but may lack a recent ADOM revision and needs proof of database synchronization. The engineer proposes the following change: Check supported FortiManager HA synchronization status, software compatibility and management peer communication before approving failover, and investigate replication errors rather than assuming a reachable secondary has current databases. Which mechanism explains why it works?
Answer & Explanations
Correct answer: C
The question is set in this situation: A university discovers its secondary FortiManager is reachable but may lack a recent ADOM revision and needs proof of database synchronization. An HA transition may involve changes in which management peer owns connections; successful web access alone does not demonstrate managed gateways reconnect and policy installs work under the new management authority. That explains “Rehearse supported FortiManager HA failover and operator access recovery”, not the mechanism behind the described change. The relevant principle is: A standby management server may be powered on while holding stale configuration or revisions; application and HA synchronization checks are required to establish that a recovery peer can manage recent policy packages.
The question is set in this situation: A university discovers its secondary FortiManager is reachable but may lack a recent ADOM revision and needs proof of database synchronization. FortiManager HA protects the central configuration management service and databases; it is not the same as FortiGate gateway clustering, so it does not automatically preserve data-plane packet forwarding for a single gateway. That explains “Configure FortiManager high availability independently of FortiGate cluster HA”, not the mechanism behind the described change. The relevant principle is: A standby management server may be powered on while holding stale configuration or revisions; application and HA synchronization checks are required to establish that a recovery peer can manage recent policy packages.
The question is set in this situation: A university discovers its secondary FortiManager is reachable but may lack a recent ADOM revision and needs proof of database synchronization. A standby management server may be powered on while holding stale configuration or revisions; application and HA synchronization checks are required to establish that a recovery peer can manage recent policy packages. The corresponding implementation is: Check supported FortiManager HA synchronization status, software compatibility and management peer communication before approving failover, and investigate replication errors rather than assuming a reachable secondary has current databases.
The question is set in this situation: A university discovers its secondary FortiManager is reachable but may lack a recent ADOM revision and needs proof of database synchronization. A centrally cached package cannot grant a missing FortiGuard license or make an unsupported FortiOS image installable; device contract and target-version prerequisites remain separate gates. That explains “Validate FortiGuard license status and firmware cache before a central update”, not the mechanism behind the described change. The relevant principle is: A standby management server may be powered on while holding stale configuration or revisions; application and HA synchronization checks are required to establish that a recovery peer can manage recent policy packages.
Question 578
A university discovers its secondary FortiManager is reachable but may lack a recent ADOM revision and needs proof of database synchronization. After implementing this change—Check supported FortiManager HA synchronization status, software compatibility and management peer communication before approving failover, and investigate replication errors rather than assuming a reachable secondary has current databases.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: B
The question is set in this situation: A university discovers its secondary FortiManager is reachable but may lack a recent ADOM revision and needs proof of database synchronization. In a staging topology confirm FortiManager peer synchronization and management service recovery while separately testing FortiGate forwarding under its installed policy and recording which component failed. That would help test “Configure FortiManager high availability independently of FortiGate cluster HA”, not the outcome required in this scenario. The relevant acceptance check is: Publish a harmless ADOM object on a lab primary, inspect synchronization completion on the secondary, then interrupt a test management link and verify the HA health alarm reflects the fault.
The question is set in this situation: A university discovers its secondary FortiManager is reachable but may lack a recent ADOM revision and needs proof of database synchronization. Publish a harmless ADOM object on a lab primary, inspect synchronization completion on the secondary, then interrupt a test management link and verify the HA health alarm reflects the fault. This check is decisive because a standby management server may be powered on while holding stale configuration or revisions; application and HA synchronization checks are required to establish that a recovery peer can manage recent policy packages.
The question is set in this situation: A university discovers its secondary FortiManager is reachable but may lack a recent ADOM revision and needs proof of database synchronization. For a staging FortiGate confirm displayed contract status and currently available package version, prepare a compatible firmware image, and verify the authorized update completes with correct post-update status. That would help test “Validate FortiGuard license status and firmware cache before a central update”, not the outcome required in this scenario. The relevant acceptance check is: Publish a harmless ADOM object on a lab primary, inspect synchronization completion on the secondary, then interrupt a test management link and verify the HA health alarm reflects the fault.
The question is set in this situation: A university discovers its secondary FortiManager is reachable but may lack a recent ADOM revision and needs proof of database synchronization. In an isolated lab fail the active management peer under a supported procedure, verify the expected surviving peer takes the correct role and demonstrate a harmless controlled policy installation to one test gateway. That would help test “Rehearse supported FortiManager HA failover and operator access recovery”, not the outcome required in this scenario. The relevant acceptance check is: Publish a harmless ADOM object on a lab primary, inspect synchronization completion on the secondary, then interrupt a test management link and verify the HA health alarm reflects the fault.
Question 579
A university discovers its secondary FortiManager is reachable but may lack a recent ADOM revision and needs proof of database synchronization. Which proposed shortcut most directly risks outdated central policy and inability to administer gateways after management recovery from an unsynchronized peer and should therefore be rejected?
Answer & Explanations
Correct answer: D
The question is set in this situation: A university discovers its secondary FortiManager is reachable but may lack a recent ADOM revision and needs proof of database synchronization. Purchase a secondary FortiManager and claim that a lone FortiGate on the network now has redundant packet-processing hardware without configuring gateway HA. That shortcut risks unprotected network data path when management-server redundancy is mistaken for firewall gateway clustering. Here the specific shortcut is: Accept a secondary FortiManager as fully protected merely because its management web login opens, without checking that recent package and device database revisions were synchronized.
The question is set in this situation: A university discovers its secondary FortiManager is reachable but may lack a recent ADOM revision and needs proof of database synchronization. Download an arbitrary firmware image into FortiManager and claim every managed FortiGate now has valid security service subscriptions and is updated without device-specific checks. That shortcut risks failed update rollout and overstated signature protection after ignoring licensing, package availability and firmware compatibility. Here the specific shortcut is: Accept a secondary FortiManager as fully protected merely because its management web login opens, without checking that recent package and device database revisions were synchronized.
The question is set in this situation: A university discovers its secondary FortiManager is reachable but may lack a recent ADOM revision and needs proof of database synchronization. After an HA alarm assume all FortiGate traffic and FortiManager control functions have recovered without testing device reconnection, administrator permissions or a policy operation. That shortcut risks prolonged central management outage because failover was declared healthy from a single reachability check. Here the specific shortcut is: Accept a secondary FortiManager as fully protected merely because its management web login opens, without checking that recent package and device database revisions were synchronized.
The question is set in this situation: A university discovers its secondary FortiManager is reachable but may lack a recent ADOM revision and needs proof of database synchronization. Accept a secondary FortiManager as fully protected merely because its management web login opens, without checking that recent package and device database revisions were synchronized. The foreseeable failure is outdated central policy and inability to administer gateways after management recovery from an unsynchronized peer. The safer response is: Check supported FortiManager HA synchronization status, software compatibility and management peer communication before approving failover, and investigate replication errors rather than assuming a reachable secondary has current databases.
Question 580
A university discovers its secondary FortiManager is reachable but may lack a recent ADOM revision and needs proof of database synchronization. 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 discovers its secondary FortiManager is reachable but may lack a recent ADOM revision and needs proof of database synchronization. Check supported FortiManager HA synchronization status, software compatibility and management peer communication before approving failover, and investigate replication errors rather than assuming a reachable secondary has current databases. Confirm it through this test: Publish a harmless ADOM object on a lab primary, inspect synchronization completion on the secondary, then interrupt a test management link and verify the HA health alarm reflects the fault. A standby management server may be powered on while holding stale configuration or revisions; application and HA synchronization checks are required to establish that a recovery peer can manage recent policy packages.
The action is applicable: Check supported FortiManager HA synchronization status, software compatibility and management peer communication before approving failover, and investigate replication errors rather than assuming a reachable secondary has current databases. But its proposed test—In a staging topology confirm FortiManager peer synchronization and management service recovery while separately testing FortiGate forwarding under its installed policy and recording which component failed.—addresses “Configure FortiManager high availability independently of FortiGate cluster HA”. This requirement is confirmed instead by: Publish a harmless ADOM object on a lab primary, inspect synchronization completion on the secondary, then interrupt a test management link and verify the HA health alarm reflects the fault.
The test would be relevant: Publish a harmless ADOM object on a lab primary, inspect synchronization completion on the secondary, then interrupt a test management link and verify the HA health alarm reflects the fault. But the offered implementation—Deploy a supported FortiManager high-availability management pair with compatible software, defined primary and secondary management roles, tested synchronization and documented operator recovery procedures separate from managed FortiGate HA.—addresses “Configure FortiManager high availability independently of FortiGate cluster HA”. The action needed here is: Check supported FortiManager HA synchronization status, software compatibility and management peer communication before approving failover, and investigate replication errors rather than assuming a reachable secondary has current databases.
This action/test pair addresses “Rehearse supported FortiManager HA failover and operator access recovery”. Plan a supported FortiManager HA failover test including management endpoint reachability, administrator login, database state and FGFM recovery for a pilot FortiGate, then document the observed behavior and required operator actions. In an isolated lab fail the active management peer under a supported procedure, verify the expected surviving peer takes the correct role and demonstrate a harmless controlled policy installation to one test gateway. The case instead calls for: Check supported FortiManager HA synchronization status, software compatibility and management peer communication before approving failover, and investigate replication errors rather than assuming a reachable secondary has current databases.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- Fortinet FCP_FMG_AD-7.6 Practice Test 56 - 10 Questions (Last Reviewed 26-Sep-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 57 - 10 Questions (Last Reviewed 21-Nov-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 58 - 10 Questions (Last Reviewed 20-Nov-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 59 - 10 Questions (Last Reviewed 19-Nov-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 60 - 10 Questions (Last Reviewed 18-Nov-2026)