Practice Exams:

Fortinet FCP_FMG_AD-7.6 Dumps

EXAM: Fortinet NSE 5 - FortiManager 7.6 Administrator
Verified By Experts
Premium Bundle
$49.99

FCP_FMG_AD-7.6 Premium ETE File


  • Premium File 62 Questions & Answers
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Fortinet FCP_FMG_AD-7.6 Practice Test 57

Question 560

A retail chain is moving toward central change control but some field engineers still make local FortiGate edits that must be reviewed rather than silently erased. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Compare FortiManager's intended package and device database with recent approved local FortiGate changes, retrieve or reconcile legitimate differences, and preview the installation impact before pushing central configuration. Verify: Add a harmless approved local rule in a staging firewall, compare central package and device revisions, import or translate it to managed policy, then install and confirm the exception is preserved.
  2. Implement: Compare FortiManager's intended package and device database with recent approved local FortiGate changes, retrieve or reconcile legitimate differences, and preview the installation impact before pushing central configuration. Verify: Bind a staged replacement FortiGate to its intended FortiManager device entry, preview the existing approved package and install it while testing both permitted and denied representative flows.
  3. Implement: After a managed FortiGate is replaced or recovered, verify the new device identity, supported firmware and interface mappings, then perform an approved policy package reinstall and validate actual enforcement. Verify: Add a harmless approved local rule in a staging firewall, compare central package and device revisions, import or translate it to managed policy, then install and confirm the exception is preserved.
  4. Implement: Inspect FortiManager's package status, installation logs and managed FortiGate revision to confirm the intended policy actually reached the correct target, and investigate any out-of-sync status before closing the change ticket. Verify: Install a harmless lab policy to two gateways, disconnect one during the task, verify only one successful result and reconcile the failed target after connectivity returns.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: A retail chain is moving toward central change control but some field engineers still make local FortiGate edits that must be reviewed rather than silently erased. Compare FortiManager's intended package and device database with recent approved local FortiGate changes, retrieve or reconcile legitimate differences, and preview the installation impact before pushing central configuration. Confirm it through this test: Add a harmless approved local rule in a staging firewall, compare central package and device revisions, import or translate it to managed policy, then install and confirm the exception is preserved. A FortiManager install can replace selected device-side settings with centrally managed intended state; ignoring authorized emergency local edits can make a later normal installation undo critical recovery changes.

B.

The action is applicable: Compare FortiManager's intended package and device database with recent approved local FortiGate changes, retrieve or reconcile legitimate differences, and preview the installation impact before pushing central configuration. But its proposed test—Bind a staged replacement FortiGate to its intended FortiManager device entry, preview the existing approved package and install it while testing both permitted and denied representative flows.—addresses “Reinstall a known approved FortiManager policy package after device replacement”. This requirement is confirmed instead by: Add a harmless approved local rule in a staging firewall, compare central package and device revisions, import or translate it to managed policy, then install and confirm the exception is preserved.

C.

The test would be relevant: Add a harmless approved local rule in a staging firewall, compare central package and device revisions, import or translate it to managed policy, then install and confirm the exception is preserved. But the offered implementation—After a managed FortiGate is replaced or recovered, verify the new device identity, supported firmware and interface mappings, then perform an approved policy package reinstall and validate actual enforcement.—addresses “Reinstall a known approved FortiManager policy package after device replacement”. The action needed here is: Compare FortiManager's intended package and device database with recent approved local FortiGate changes, retrieve or reconcile legitimate differences, and preview the installation impact before pushing central configuration.

D.

This action/test pair addresses “Confirm FortiManager package status after a successful installation”. Inspect FortiManager's package status, installation logs and managed FortiGate revision to confirm the intended policy actually reached the correct target, and investigate any out-of-sync status before closing the change ticket. Install a harmless lab policy to two gateways, disconnect one during the task, verify only one successful result and reconcile the failed target after connectivity returns. The case instead calls for: Compare FortiManager's intended package and device database with recent approved local FortiGate changes, retrieve or reconcile legitimate differences, and preview the installation impact before pushing central configuration.

Question 561

A municipal agency has a FortiManager appliance pair and wants to explain why its single branch firewall remains a data-plane single point of failure. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. 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.
  2. Choose a supported local FortiGuard cache or distribution configuration according to the firewall estate's connected and disconnected requirements, and verify whether clients query or receive updated content from the intended service.
  3. 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.
  4. 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.

Answer & Explanations

Correct answer: C

A.

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: 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.

B.

Choose a supported local FortiGuard cache or distribution configuration according to the firewall estate's connected and disconnected requirements, and verify whether clients query or receive updated content from the intended service. This addresses “Distinguish FortiManager FortiGuard cache from managed update distribution”, where the governing principle is: Caching previously fetched security data and actively distributing verified update packages serve different operational paths; a valid cached response does not mean disconnected gateways always have a current full signature library. The stated 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.

C.

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. 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. Verify the result with 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.

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: 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 562

A municipal agency has a FortiManager appliance pair and wants to explain why its single branch firewall remains a data-plane single point of failure. The engineer proposes the following change: 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. Which mechanism explains why it works?

  1. 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.
  2. 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.
  3. 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.
  4. Caching previously fetched security data and actively distributing verified update packages serve different operational paths; a valid cached response does not mean disconnected gateways always have a current full signature library.

Answer & Explanations

Correct answer: B

A.

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: 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.

B.

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 corresponding implementation 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.

C.

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: 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.

D.

Caching previously fetched security data and actively distributing verified update packages serve different operational paths; a valid cached response does not mean disconnected gateways always have a current full signature library. That explains “Distinguish FortiManager FortiGuard cache from managed update distribution”, not the mechanism behind the described change. The relevant 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.

Question 563

A municipal agency has a FortiManager appliance pair and wants to explain why its single branch firewall remains a data-plane single point of failure. After implementing this change—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.—which test most directly validates its intended outcome?

  1. Stage an approved FortiGate update query through FortiManager, inspect cache or distribution state and corresponding package versions, and confirm a deliberately outdated test package is detected.
  2. 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.
  3. 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.
  4. 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.

Answer & Explanations

Correct answer: D

A.

Stage an approved FortiGate update query through FortiManager, inspect cache or distribution state and corresponding package versions, and confirm a deliberately outdated test package is detected. That would help test “Distinguish FortiManager FortiGuard cache from managed update distribution”, not the outcome required in this scenario. The relevant acceptance check is: 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.

B.

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 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.

C.

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: 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.

D.

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. This check is decisive because 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.

Question 564

A municipal agency has a FortiManager appliance pair and wants to explain why its single branch firewall remains a data-plane single point of failure. Which proposed shortcut most directly risks unprotected network data path when management-server redundancy is mistaken for firewall gateway clustering and should therefore be rejected?

  1. Purchase a secondary FortiManager and claim that a lone FortiGate on the network now has redundant packet-processing hardware without configuring gateway HA.
  2. Use the words FortiGuard cache and FDS interchangeably and claim a gateway has current IPS signatures without checking the actual downloaded package version.
  3. 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.
  4. After an HA alarm assume all FortiGate traffic and FortiManager control functions have recovered without testing device reconnection, administrator permissions or a policy operation.

Answer & Explanations

Correct answer: A

A.

Purchase a secondary FortiManager and claim that a lone FortiGate on the network now has redundant packet-processing hardware without configuring gateway HA. The foreseeable failure is unprotected network data path when management-server redundancy is mistaken for firewall gateway clustering. The safer response 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.

B.

Use the words FortiGuard cache and FDS interchangeably and claim a gateway has current IPS signatures without checking the actual downloaded package version. That shortcut risks misleading patch and signature status when update-service roles are confused. Here the specific shortcut is: Purchase a secondary FortiManager and claim that a lone FortiGate on the network now has redundant packet-processing hardware without configuring gateway HA.

C.

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: Purchase a secondary FortiManager and claim that a lone FortiGate on the network now has redundant packet-processing hardware without configuring gateway HA.

D.

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: Purchase a secondary FortiManager and claim that a lone FortiGate on the network now has redundant packet-processing hardware without configuring gateway HA.

Question 565

A municipal agency has a FortiManager appliance pair and wants to explain why its single branch firewall remains a data-plane single point of failure. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: 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. Verify: 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.
  2. Implement: 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. Verify: 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.
  3. Implement: 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. Verify: 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.
  4. Implement: 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. Verify: 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.

Answer & Explanations

Correct answer: C

A.

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—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 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.

B.

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—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: 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.

C.

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.

D.

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: 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 566

A bank is designing management disaster recovery and must independently evaluate FortiManager database continuity and branch FortiGate HA availability. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. 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.
  2. 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.
  3. Choose a supported local FortiGuard cache or distribution configuration according to the firewall estate's connected and disconnected requirements, and verify whether clients query or receive updated content from the intended service.
  4. 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.

Answer & Explanations

Correct answer: D

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. 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: 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.

B.

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. 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: 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.

C.

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. Choose a supported local FortiGuard cache or distribution configuration according to the firewall estate's connected and disconnected requirements, and verify whether clients query or receive updated content from the intended service. This addresses “Distinguish FortiManager FortiGuard cache from managed update distribution”, where the governing principle is: Caching previously fetched security data and actively distributing verified update packages serve different operational paths; a valid cached response does not mean disconnected gateways always have a current full signature library. The stated 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.

D.

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. 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. Verify the result with 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.

Question 567

A bank is designing management disaster recovery and must independently evaluate FortiManager database continuity and branch FortiGate HA availability. The engineer proposes the following change: 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. Which mechanism explains why it works?

  1. 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.
  2. 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.
  3. 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.
  4. Caching previously fetched security data and actively distributing verified update packages serve different operational paths; a valid cached response does not mean disconnected gateways always have a current full signature library.

Answer & Explanations

Correct answer: B

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. 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: 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.

B.

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. 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 corresponding implementation 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.

C.

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. 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: 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.

D.

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. Caching previously fetched security data and actively distributing verified update packages serve different operational paths; a valid cached response does not mean disconnected gateways always have a current full signature library. That explains “Distinguish FortiManager FortiGuard cache from managed update distribution”, not the mechanism behind the described change. The relevant 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.

Question 568

A bank is designing management disaster recovery and must independently evaluate FortiManager database continuity and branch FortiGate HA availability. After implementing this change—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.—which test most directly validates its intended outcome?

  1. 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.
  2. Stage an approved FortiGate update query through FortiManager, inspect cache or distribution state and corresponding package versions, and confirm a deliberately outdated test package is detected.
  3. 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.
  4. 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.

Answer & Explanations

Correct answer: A

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. 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. This check is decisive because 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.

B.

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. Stage an approved FortiGate update query through FortiManager, inspect cache or distribution state and corresponding package versions, and confirm a deliberately outdated test package is detected. That would help test “Distinguish FortiManager FortiGuard cache from managed update distribution”, not the outcome required in this scenario. The relevant acceptance check is: 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.

C.

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. 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: 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.

D.

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. 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 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.

Question 569

A bank is designing management disaster recovery and must independently evaluate FortiManager database continuity and branch FortiGate HA availability. Which proposed shortcut most directly risks unprotected network data path when management-server redundancy is mistaken for firewall gateway clustering and should therefore be rejected?

  1. 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.
  2. Use the words FortiGuard cache and FDS interchangeably and claim a gateway has current IPS signatures without checking the actual downloaded package version.
  3. Purchase a secondary FortiManager and claim that a lone FortiGate on the network now has redundant packet-processing hardware without configuring gateway HA.
  4. After an HA alarm assume all FortiGate traffic and FortiManager control functions have recovered without testing device reconnection, administrator permissions or a policy operation.

Answer & Explanations

Correct answer: C

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. 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: Purchase a secondary FortiManager and claim that a lone FortiGate on the network now has redundant packet-processing hardware without configuring gateway HA.

B.

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. Use the words FortiGuard cache and FDS interchangeably and claim a gateway has current IPS signatures without checking the actual downloaded package version. That shortcut risks misleading patch and signature status when update-service roles are confused. Here the specific shortcut is: Purchase a secondary FortiManager and claim that a lone FortiGate on the network now has redundant packet-processing hardware without configuring gateway HA.

C.

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. Purchase a secondary FortiManager and claim that a lone FortiGate on the network now has redundant packet-processing hardware without configuring gateway HA. The foreseeable failure is unprotected network data path when management-server redundancy is mistaken for firewall gateway clustering. The safer response 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.

D.

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. 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: Purchase a secondary FortiManager and claim that a lone FortiGate on the network now has redundant packet-processing hardware without configuring gateway HA.

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?

  1. Implement: 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. Verify: 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.
  2. Implement: 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. Verify: 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.
  3. Implement: 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. Verify: 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.
  4. Implement: 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. Verify: 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.

Answer & Explanations

Correct answer: A

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.

B.

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.

C.

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.

D.

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.

Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests