Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 59
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.
Question 581
A financial company needs to demonstrate that a secondary FortiManager can resume authorized branch policy operations after primary maintenance. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: A
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. 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. Verify the result with this 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.
Create reviewed shared policy and object definitions in the supported Global ADOM, assign appropriate global policy packages to selected customer ADOMs and validate generated header or footer behavior. This addresses “Use the FortiManager Global ADOM for shared header policy without abandoning tenant isolation”, where the governing principle is: A Global ADOM permits controlled reuse of enterprise-wide policy elements; its assignments do not erase customer ADOM isolation or prove that every tenant accepted and installed the latest global package. The stated case instead calls for: 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.
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: 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.
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 addresses “Monitor FortiManager HA synchronization and correctly interpret peer health”, where the governing 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 stated case instead calls for: 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.
Question 582
A financial company needs to demonstrate that a secondary FortiManager can resume authorized branch policy operations after primary maintenance. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: B
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. That explains “Monitor FortiManager HA synchronization and correctly interpret peer health”, not the mechanism behind the described change. The relevant 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.
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 corresponding implementation is: 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.
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: 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.
A Global ADOM permits controlled reuse of enterprise-wide policy elements; its assignments do not erase customer ADOM isolation or prove that every tenant accepted and installed the latest global package. That explains “Use the FortiManager Global ADOM for shared header policy without abandoning tenant isolation”, not the mechanism behind the described change. The relevant 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.
Question 583
A financial company needs to demonstrate that a secondary FortiManager can resume authorized branch policy operations after primary maintenance. After implementing this change—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.—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: 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.
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. That would help test “Monitor FortiManager HA synchronization and correctly interpret peer health”, not the outcome required in this scenario. The relevant acceptance check is: 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.
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. This check is decisive because 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.
Create a harmless global deny rule for a test environment, assign it only to two permitted ADOMs, preview merged policy output and verify an unselected ADOM stays unchanged. That would help test “Use the FortiManager Global ADOM for shared header policy without abandoning tenant isolation”, not the outcome required in this scenario. The relevant acceptance check is: 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.
Question 584
A financial company needs to demonstrate that a secondary FortiManager can resume authorized branch policy operations after primary maintenance. Which proposed shortcut most directly risks prolonged central management outage because failover was declared healthy from a single reachability check and should therefore be rejected?
Answer & Explanations
Correct answer: D
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: After an HA alarm assume all FortiGate traffic and FortiManager control functions have recovered without testing device reconnection, administrator permissions or a policy operation.
Write one global firewall package and assume all managed customer ADOMs automatically install and enforce it regardless of global package assignment or review. That shortcut risks unapproved cross-tenant filtering changes after global policy scope is assumed rather than explicitly managed. Here the specific shortcut is: After an HA alarm assume all FortiGate traffic and FortiManager control functions have recovered without testing device reconnection, administrator permissions or a policy operation.
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. That shortcut risks outdated central policy and inability to administer gateways after management recovery from an unsynchronized peer. Here the specific shortcut is: After an HA alarm assume all FortiGate traffic and FortiManager control functions have recovered without testing device reconnection, administrator permissions or a policy operation.
After an HA alarm assume all FortiGate traffic and FortiManager control functions have recovered without testing device reconnection, administrator permissions or a policy operation. The foreseeable failure is prolonged central management outage because failover was declared healthy from a single reachability check. The safer response is: 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.
Question 585
A financial company needs to demonstrate that a secondary FortiManager can resume authorized branch policy operations after primary maintenance. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: C
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: 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.
The test would be relevant: 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. 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: 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.
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. Confirm it through this 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. 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 action is applicable: 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. 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: 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.
Question 586
A regional hospital is rehearsing central management recovery and wants evidence of both administrator access and FortiGate device management after peer transition. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: D
The question is set in this situation: A regional hospital is rehearsing central management recovery and wants evidence of both administrator access and FortiGate device management after peer transition. 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: 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.
The question is set in this situation: A regional hospital is rehearsing central management recovery and wants evidence of both administrator access and FortiGate device management after peer transition. 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 addresses “Monitor FortiManager HA synchronization and correctly interpret peer health”, where the governing 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 stated case instead calls for: 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.
The question is set in this situation: A regional hospital is rehearsing central management recovery and wants evidence of both administrator access and FortiGate device management after peer transition. Create reviewed shared policy and object definitions in the supported Global ADOM, assign appropriate global policy packages to selected customer ADOMs and validate generated header or footer behavior. This addresses “Use the FortiManager Global ADOM for shared header policy without abandoning tenant isolation”, where the governing principle is: A Global ADOM permits controlled reuse of enterprise-wide policy elements; its assignments do not erase customer ADOM isolation or prove that every tenant accepted and installed the latest global package. The stated case instead calls for: 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.
The question is set in this situation: A regional hospital is rehearsing central management recovery and wants evidence of both administrator access and FortiGate device management after peer transition. 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. 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. Verify the result with this 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.
Question 587
A regional hospital is rehearsing central management recovery and wants evidence of both administrator access and FortiGate device management after peer transition. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: A
The question is set in this situation: A regional hospital is rehearsing central management recovery and wants evidence of both administrator access and FortiGate device management after peer transition. 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 corresponding implementation is: 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.
The question is set in this situation: A regional hospital is rehearsing central management recovery and wants evidence of both administrator access and FortiGate device management after peer transition. 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. That explains “Monitor FortiManager HA synchronization and correctly interpret peer health”, not the mechanism behind the described change. The relevant 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 question is set in this situation: A regional hospital is rehearsing central management recovery and wants evidence of both administrator access and FortiGate device management after peer transition. 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: 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 question is set in this situation: A regional hospital is rehearsing central management recovery and wants evidence of both administrator access and FortiGate device management after peer transition. A Global ADOM permits controlled reuse of enterprise-wide policy elements; its assignments do not erase customer ADOM isolation or prove that every tenant accepted and installed the latest global package. That explains “Use the FortiManager Global ADOM for shared header policy without abandoning tenant isolation”, not the mechanism behind the described change. The relevant 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.
Question 588
A regional hospital is rehearsing central management recovery and wants evidence of both administrator access and FortiGate device management after peer transition. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: B
The question is set in this situation: A regional hospital is rehearsing central management recovery and wants evidence of both administrator access and FortiGate device management after peer transition. 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. That would help test “Monitor FortiManager HA synchronization and correctly interpret peer health”, not the outcome required in this scenario. The relevant acceptance check is: 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 question is set in this situation: A regional hospital is rehearsing central management recovery and wants evidence of both administrator access and FortiGate device management after peer transition. 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. This check is decisive because 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 question is set in this situation: A regional hospital is rehearsing central management recovery and wants evidence of both administrator access and FortiGate device management after peer transition. Create a harmless global deny rule for a test environment, assign it only to two permitted ADOMs, preview merged policy output and verify an unselected ADOM stays unchanged. That would help test “Use the FortiManager Global ADOM for shared header policy without abandoning tenant isolation”, not the outcome required in this scenario. The relevant acceptance check is: 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 question is set in this situation: A regional hospital is rehearsing central management recovery and wants evidence of both administrator access and FortiGate device management after peer transition. 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: 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.
Question 589
A regional hospital is rehearsing central management recovery and wants evidence of both administrator access and FortiGate device management after peer transition. Which proposed shortcut most directly risks prolonged central management outage because failover was declared healthy from a single reachability check and should therefore be rejected?
Answer & Explanations
Correct answer: D
The question is set in this situation: A regional hospital is rehearsing central management recovery and wants evidence of both administrator access and FortiGate device management after peer transition. 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: After an HA alarm assume all FortiGate traffic and FortiManager control functions have recovered without testing device reconnection, administrator permissions or a policy operation.
The question is set in this situation: A regional hospital is rehearsing central management recovery and wants evidence of both administrator access and FortiGate device management after peer transition. 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. That shortcut risks outdated central policy and inability to administer gateways after management recovery from an unsynchronized peer. Here the specific shortcut is: After an HA alarm assume all FortiGate traffic and FortiManager control functions have recovered without testing device reconnection, administrator permissions or a policy operation.
The question is set in this situation: A regional hospital is rehearsing central management recovery and wants evidence of both administrator access and FortiGate device management after peer transition. Write one global firewall package and assume all managed customer ADOMs automatically install and enforce it regardless of global package assignment or review. That shortcut risks unapproved cross-tenant filtering changes after global policy scope is assumed rather than explicitly managed. Here the specific shortcut is: After an HA alarm assume all FortiGate traffic and FortiManager control functions have recovered without testing device reconnection, administrator permissions or a policy operation.
The question is set in this situation: A regional hospital is rehearsing central management recovery and wants evidence of both administrator access and FortiGate device management after peer transition. After an HA alarm assume all FortiGate traffic and FortiManager control functions have recovered without testing device reconnection, administrator permissions or a policy operation. The foreseeable failure is prolonged central management outage because failover was declared healthy from a single reachability check. The safer response is: 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.
Question 590
A regional hospital is rehearsing central management recovery and wants evidence of both administrator access and FortiGate device management after peer transition. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: C
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: 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.
The test would be relevant: 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. But the offered implementation—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.—addresses “Monitor FortiManager HA synchronization and correctly interpret peer health”. The action needed here is: 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.
The question is set in this situation: A regional hospital is rehearsing central management recovery and wants evidence of both administrator access and FortiGate device management after peer transition. 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. Confirm it through this 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. 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 action is applicable: 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. But its proposed 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.—addresses “Monitor FortiManager HA synchronization and correctly interpret peer health”. This requirement is confirmed instead by: 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.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- 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)
- Fortinet FCP_FMG_AD-7.6 Practice Test 61 - 10 Questions (Last Reviewed 17-Nov-2026)