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 60

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?

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

A.

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.

B.

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.

C.

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.

D.

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.

Question 591

A defense-sector network has restricted internet egress and wants FortiManager to distribute approved signatures to managed branch FortiGates. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. Use supported FortiManager FortiGuard service or FDS configuration to provide approved security update content to eligible managed or unmanaged FortiGates, preserving valid contracts and a verified update path.
  2. 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.
  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. Preview how a Global ADOM header or footer policy combines with a local ADOM package, inspect applicable object mappings and rule order, and authorize the resulting configuration before installing it.

Answer & Explanations

Correct answer: A

A.

Use supported FortiManager FortiGuard service or FDS configuration to provide approved security update content to eligible managed or unmanaged FortiGates, preserving valid contracts and a verified update path. A local FortiGuard distribution role can supply cached or distributed signature content where appropriate, but a server address override alone does not guarantee the update packages are present, licensed or compatible. Verify the result with this test: In a test environment verify FortiManager has current permitted IPS and antivirus update packages, configure one FortiGate to reach its approved FDS endpoint and confirm the gateway receives an updated database.

B.

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: Use supported FortiManager FortiGuard service or FDS configuration to provide approved security update content to eligible managed or unmanaged FortiGates, preserving valid contracts and a verified update path.

C.

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: Use supported FortiManager FortiGuard service or FDS configuration to provide approved security update content to eligible managed or unmanaged FortiGates, preserving valid contracts and a verified update path.

D.

Preview how a Global ADOM header or footer policy combines with a local ADOM package, inspect applicable object mappings and rule order, and authorize the resulting configuration before installing it. This addresses “Validate the effect of a Global ADOM package on downstream policy order”, where the governing principle is: A global policy section can alter effective rule evaluation order relative to local ADOM rules; merely reviewing the global rule in isolation may miss unintended permitted or denied traffic when the package is installed. The stated case instead calls for: Use supported FortiManager FortiGuard service or FDS configuration to provide approved security update content to eligible managed or unmanaged FortiGates, preserving valid contracts and a verified update path.

Question 592

A defense-sector network has restricted internet egress and wants FortiManager to distribute approved signatures to managed branch FortiGates. The engineer proposes the following change: Use supported FortiManager FortiGuard service or FDS configuration to provide approved security update content to eligible managed or unmanaged FortiGates, preserving valid contracts and a verified update path. Which mechanism explains why it works?

  1. 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.
  2. A local FortiGuard distribution role can supply cached or distributed signature content where appropriate, but a server address override alone does not guarantee the update packages are present, licensed or compatible.
  3. A global policy section can alter effective rule evaluation order relative to local ADOM rules; merely reviewing the global rule in isolation may miss unintended permitted or denied traffic when the package is installed.
  4. 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.

Answer & Explanations

Correct answer: B

A.

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: A local FortiGuard distribution role can supply cached or distributed signature content where appropriate, but a server address override alone does not guarantee the update packages are present, licensed or compatible.

B.

A local FortiGuard distribution role can supply cached or distributed signature content where appropriate, but a server address override alone does not guarantee the update packages are present, licensed or compatible. The corresponding implementation is: Use supported FortiManager FortiGuard service or FDS configuration to provide approved security update content to eligible managed or unmanaged FortiGates, preserving valid contracts and a verified update path.

C.

A global policy section can alter effective rule evaluation order relative to local ADOM rules; merely reviewing the global rule in isolation may miss unintended permitted or denied traffic when the package is installed. That explains “Validate the effect of a Global ADOM package on downstream policy order”, not the mechanism behind the described change. The relevant principle is: A local FortiGuard distribution role can supply cached or distributed signature content where appropriate, but a server address override alone does not guarantee the update packages are present, licensed or compatible.

D.

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 local FortiGuard distribution role can supply cached or distributed signature content where appropriate, but a server address override alone does not guarantee the update packages are present, licensed or compatible.

Question 593

A defense-sector network has restricted internet egress and wants FortiManager to distribute approved signatures to managed branch FortiGates. After implementing this change—Use supported FortiManager FortiGuard service or FDS configuration to provide approved security update content to eligible managed or unmanaged FortiGates, preserving valid contracts and a verified update path.—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. Build a lab package with a global header deny and local permit for the same test service, preview final ordering, install to a designated gateway and verify the intended deny takes precedence.
  3. 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.
  4. In a test environment verify FortiManager has current permitted IPS and antivirus update packages, configure one FortiGate to reach its approved FDS endpoint and confirm the gateway receives an updated database.

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 test environment verify FortiManager has current permitted IPS and antivirus update packages, configure one FortiGate to reach its approved FDS endpoint and confirm the gateway receives an updated database.

B.

Build a lab package with a global header deny and local permit for the same test service, preview final ordering, install to a designated gateway and verify the intended deny takes precedence. That would help test “Validate the effect of a Global ADOM package on downstream policy order”, not the outcome required in this scenario. The relevant acceptance check is: In a test environment verify FortiManager has current permitted IPS and antivirus update packages, configure one FortiGate to reach its approved FDS endpoint and confirm the gateway receives an updated database.

C.

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: In a test environment verify FortiManager has current permitted IPS and antivirus update packages, configure one FortiGate to reach its approved FDS endpoint and confirm the gateway receives an updated database.

D.

In a test environment verify FortiManager has current permitted IPS and antivirus update packages, configure one FortiGate to reach its approved FDS endpoint and confirm the gateway receives an updated database. This check is decisive because a local FortiGuard distribution role can supply cached or distributed signature content where appropriate, but a server address override alone does not guarantee the update packages are present, licensed or compatible.

Question 594

A defense-sector network has restricted internet egress and wants FortiManager to distribute approved signatures to managed branch FortiGates. Which proposed shortcut most directly risks stale security protection after a local FortiGuard update path is configured without valid content distribution and should therefore be rejected?

  1. Use the words FortiGuard cache and FDS interchangeably and claim a gateway has current IPS signatures without checking the actual downloaded package version.
  2. Assign a global rule to a local ADOM and assume that rule is always evaluated last regardless of header or footer placement and the generated installed policy.
  3. Point every firewall to an empty FortiManager update endpoint and assume fresh FortiGuard IPS signatures arrive automatically with no distribution service, content synchronization or contract check.
  4. 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.

Answer & Explanations

Correct answer: C

A.

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: Point every firewall to an empty FortiManager update endpoint and assume fresh FortiGuard IPS signatures arrive automatically with no distribution service, content synchronization or contract check.

B.

Assign a global rule to a local ADOM and assume that rule is always evaluated last regardless of header or footer placement and the generated installed policy. That shortcut risks security policy shadowing or unexpected blocked traffic after global-to-local rule order is not validated. Here the specific shortcut is: Point every firewall to an empty FortiManager update endpoint and assume fresh FortiGuard IPS signatures arrive automatically with no distribution service, content synchronization or contract check.

C.

Point every firewall to an empty FortiManager update endpoint and assume fresh FortiGuard IPS signatures arrive automatically with no distribution service, content synchronization or contract check. The foreseeable failure is stale security protection after a local FortiGuard update path is configured without valid content distribution. The safer response is: Use supported FortiManager FortiGuard service or FDS configuration to provide approved security update content to eligible managed or unmanaged FortiGates, preserving valid contracts and a verified update path.

D.

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: Point every firewall to an empty FortiManager update endpoint and assume fresh FortiGuard IPS signatures arrive automatically with no distribution service, content synchronization or contract check.

Question 595

A defense-sector network has restricted internet egress and wants FortiManager to distribute approved signatures to managed branch FortiGates. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Use supported FortiManager FortiGuard service or FDS configuration to provide approved security update content to eligible managed or unmanaged FortiGates, preserving valid contracts and a verified update path. Verify: In a test environment verify FortiManager has current permitted IPS and antivirus update packages, configure one FortiGate to reach its approved FDS endpoint and confirm the gateway receives an updated database.
  2. Implement: 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. Verify: In a test environment verify FortiManager has current permitted IPS and antivirus update packages, configure one FortiGate to reach its approved FDS endpoint and confirm the gateway receives an updated database.
  3. Implement: 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. Verify: 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.
  4. Implement: Use supported FortiManager FortiGuard service or FDS configuration to provide approved security update content to eligible managed or unmanaged FortiGates, preserving valid contracts and a verified update path. Verify: 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.

Answer & Explanations

Correct answer: A

A.

Use supported FortiManager FortiGuard service or FDS configuration to provide approved security update content to eligible managed or unmanaged FortiGates, preserving valid contracts and a verified update path. Confirm it through this test: In a test environment verify FortiManager has current permitted IPS and antivirus update packages, configure one FortiGate to reach its approved FDS endpoint and confirm the gateway receives an updated database. A local FortiGuard distribution role can supply cached or distributed signature content where appropriate, but a server address override alone does not guarantee the update packages are present, licensed or compatible.

B.

The test would be relevant: In a test environment verify FortiManager has current permitted IPS and antivirus update packages, configure one FortiGate to reach its approved FDS endpoint and confirm the gateway receives an updated database. But the offered implementation—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.—addresses “Validate FortiGuard license status and firmware cache before a central update”. The action needed here is: Use supported FortiManager FortiGuard service or FDS configuration to provide approved security update content to eligible managed or unmanaged FortiGates, preserving valid contracts and a verified update path.

C.

This action/test pair addresses “Distinguish FortiManager FortiGuard cache from managed update distribution”. 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. 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. The case instead calls for: Use supported FortiManager FortiGuard service or FDS configuration to provide approved security update content to eligible managed or unmanaged FortiGates, preserving valid contracts and a verified update path.

D.

The action is applicable: Use supported FortiManager FortiGuard service or FDS configuration to provide approved security update content to eligible managed or unmanaged FortiGates, preserving valid contracts and a verified update path. But its proposed test—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.—addresses “Validate FortiGuard license status and firmware cache before a central update”. This requirement is confirmed instead by: In a test environment verify FortiManager has current permitted IPS and antivirus update packages, configure one FortiGate to reach its approved FDS endpoint and confirm the gateway receives an updated database.

Question 596

A manufacturer uses FortiManager as an update source and needs evidence that a remote gateway recognizes the intended current intrusion-prevention package. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. 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.
  2. Use supported FortiManager FortiGuard service or FDS configuration to provide approved security update content to eligible managed or unmanaged FortiGates, preserving valid contracts and a verified update path.
  3. 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.
  4. Preview how a Global ADOM header or footer policy combines with a local ADOM package, inspect applicable object mappings and rule order, and authorize the resulting configuration before installing it.

Answer & Explanations

Correct answer: B

A.

The question is set in this situation: A manufacturer uses FortiManager as an update source and needs evidence that a remote gateway recognizes the intended current intrusion-prevention package. 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: Use supported FortiManager FortiGuard service or FDS configuration to provide approved security update content to eligible managed or unmanaged FortiGates, preserving valid contracts and a verified update path.

B.

The question is set in this situation: A manufacturer uses FortiManager as an update source and needs evidence that a remote gateway recognizes the intended current intrusion-prevention package. Use supported FortiManager FortiGuard service or FDS configuration to provide approved security update content to eligible managed or unmanaged FortiGates, preserving valid contracts and a verified update path. A local FortiGuard distribution role can supply cached or distributed signature content where appropriate, but a server address override alone does not guarantee the update packages are present, licensed or compatible. Verify the result with this test: In a test environment verify FortiManager has current permitted IPS and antivirus update packages, configure one FortiGate to reach its approved FDS endpoint and confirm the gateway receives an updated database.

C.

The question is set in this situation: A manufacturer uses FortiManager as an update source and needs evidence that a remote gateway recognizes the intended current intrusion-prevention package. 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: Use supported FortiManager FortiGuard service or FDS configuration to provide approved security update content to eligible managed or unmanaged FortiGates, preserving valid contracts and a verified update path.

D.

The question is set in this situation: A manufacturer uses FortiManager as an update source and needs evidence that a remote gateway recognizes the intended current intrusion-prevention package. Preview how a Global ADOM header or footer policy combines with a local ADOM package, inspect applicable object mappings and rule order, and authorize the resulting configuration before installing it. This addresses “Validate the effect of a Global ADOM package on downstream policy order”, where the governing principle is: A global policy section can alter effective rule evaluation order relative to local ADOM rules; merely reviewing the global rule in isolation may miss unintended permitted or denied traffic when the package is installed. The stated case instead calls for: Use supported FortiManager FortiGuard service or FDS configuration to provide approved security update content to eligible managed or unmanaged FortiGates, preserving valid contracts and a verified update path.

Question 597

A manufacturer uses FortiManager as an update source and needs evidence that a remote gateway recognizes the intended current intrusion-prevention package. The engineer proposes the following change: Use supported FortiManager FortiGuard service or FDS configuration to provide approved security update content to eligible managed or unmanaged FortiGates, preserving valid contracts and a verified update path. Which mechanism explains why it works?

  1. 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.
  2. A local FortiGuard distribution role can supply cached or distributed signature content where appropriate, but a server address override alone does not guarantee the update packages are present, licensed or compatible.
  3. 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.
  4. A global policy section can alter effective rule evaluation order relative to local ADOM rules; merely reviewing the global rule in isolation may miss unintended permitted or denied traffic when the package is installed.

Answer & Explanations

Correct answer: B

A.

The question is set in this situation: A manufacturer uses FortiManager as an update source and needs evidence that a remote gateway recognizes the intended current intrusion-prevention package. 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: A local FortiGuard distribution role can supply cached or distributed signature content where appropriate, but a server address override alone does not guarantee the update packages are present, licensed or compatible.

B.

The question is set in this situation: A manufacturer uses FortiManager as an update source and needs evidence that a remote gateway recognizes the intended current intrusion-prevention package. A local FortiGuard distribution role can supply cached or distributed signature content where appropriate, but a server address override alone does not guarantee the update packages are present, licensed or compatible. The corresponding implementation is: Use supported FortiManager FortiGuard service or FDS configuration to provide approved security update content to eligible managed or unmanaged FortiGates, preserving valid contracts and a verified update path.

C.

The question is set in this situation: A manufacturer uses FortiManager as an update source and needs evidence that a remote gateway recognizes the intended current intrusion-prevention package. 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 local FortiGuard distribution role can supply cached or distributed signature content where appropriate, but a server address override alone does not guarantee the update packages are present, licensed or compatible.

D.

The question is set in this situation: A manufacturer uses FortiManager as an update source and needs evidence that a remote gateway recognizes the intended current intrusion-prevention package. A global policy section can alter effective rule evaluation order relative to local ADOM rules; merely reviewing the global rule in isolation may miss unintended permitted or denied traffic when the package is installed. That explains “Validate the effect of a Global ADOM package on downstream policy order”, not the mechanism behind the described change. The relevant principle is: A local FortiGuard distribution role can supply cached or distributed signature content where appropriate, but a server address override alone does not guarantee the update packages are present, licensed or compatible.

Question 598

A manufacturer uses FortiManager as an update source and needs evidence that a remote gateway recognizes the intended current intrusion-prevention package. After implementing this change—Use supported FortiManager FortiGuard service or FDS configuration to provide approved security update content to eligible managed or unmanaged FortiGates, preserving valid contracts and a verified update path.—which test most directly validates its intended outcome?

  1. In a test environment verify FortiManager has current permitted IPS and antivirus update packages, configure one FortiGate to reach its approved FDS endpoint and confirm the gateway receives an updated database.
  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. Build a lab package with a global header deny and local permit for the same test service, preview final ordering, install to a designated gateway and verify the intended deny takes precedence.
  4. 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.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: A manufacturer uses FortiManager as an update source and needs evidence that a remote gateway recognizes the intended current intrusion-prevention package. In a test environment verify FortiManager has current permitted IPS and antivirus update packages, configure one FortiGate to reach its approved FDS endpoint and confirm the gateway receives an updated database. This check is decisive because a local FortiGuard distribution role can supply cached or distributed signature content where appropriate, but a server address override alone does not guarantee the update packages are present, licensed or compatible.

B.

The question is set in this situation: A manufacturer uses FortiManager as an update source and needs evidence that a remote gateway recognizes the intended current intrusion-prevention package. 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 test environment verify FortiManager has current permitted IPS and antivirus update packages, configure one FortiGate to reach its approved FDS endpoint and confirm the gateway receives an updated database.

C.

The question is set in this situation: A manufacturer uses FortiManager as an update source and needs evidence that a remote gateway recognizes the intended current intrusion-prevention package. Build a lab package with a global header deny and local permit for the same test service, preview final ordering, install to a designated gateway and verify the intended deny takes precedence. That would help test “Validate the effect of a Global ADOM package on downstream policy order”, not the outcome required in this scenario. The relevant acceptance check is: In a test environment verify FortiManager has current permitted IPS and antivirus update packages, configure one FortiGate to reach its approved FDS endpoint and confirm the gateway receives an updated database.

D.

The question is set in this situation: A manufacturer uses FortiManager as an update source and needs evidence that a remote gateway recognizes the intended current intrusion-prevention package. 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: In a test environment verify FortiManager has current permitted IPS and antivirus update packages, configure one FortiGate to reach its approved FDS endpoint and confirm the gateway receives an updated database.

Question 599

A manufacturer uses FortiManager as an update source and needs evidence that a remote gateway recognizes the intended current intrusion-prevention package. Which proposed shortcut most directly risks stale security protection after a local FortiGuard update path is configured without valid content distribution and should therefore be rejected?

  1. 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.
  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. Assign a global rule to a local ADOM and assume that rule is always evaluated last regardless of header or footer placement and the generated installed policy.
  4. Point every firewall to an empty FortiManager update endpoint and assume fresh FortiGuard IPS signatures arrive automatically with no distribution service, content synchronization or contract check.

Answer & Explanations

Correct answer: D

A.

The question is set in this situation: A manufacturer uses FortiManager as an update source and needs evidence that a remote gateway recognizes the intended current intrusion-prevention package. 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: Point every firewall to an empty FortiManager update endpoint and assume fresh FortiGuard IPS signatures arrive automatically with no distribution service, content synchronization or contract check.

B.

The question is set in this situation: A manufacturer uses FortiManager as an update source and needs evidence that a remote gateway recognizes the intended current intrusion-prevention package. 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: Point every firewall to an empty FortiManager update endpoint and assume fresh FortiGuard IPS signatures arrive automatically with no distribution service, content synchronization or contract check.

C.

The question is set in this situation: A manufacturer uses FortiManager as an update source and needs evidence that a remote gateway recognizes the intended current intrusion-prevention package. Assign a global rule to a local ADOM and assume that rule is always evaluated last regardless of header or footer placement and the generated installed policy. That shortcut risks security policy shadowing or unexpected blocked traffic after global-to-local rule order is not validated. Here the specific shortcut is: Point every firewall to an empty FortiManager update endpoint and assume fresh FortiGuard IPS signatures arrive automatically with no distribution service, content synchronization or contract check.

D.

The question is set in this situation: A manufacturer uses FortiManager as an update source and needs evidence that a remote gateway recognizes the intended current intrusion-prevention package. Point every firewall to an empty FortiManager update endpoint and assume fresh FortiGuard IPS signatures arrive automatically with no distribution service, content synchronization or contract check. The foreseeable failure is stale security protection after a local FortiGuard update path is configured without valid content distribution. The safer response is: Use supported FortiManager FortiGuard service or FDS configuration to provide approved security update content to eligible managed or unmanaged FortiGates, preserving valid contracts and a verified update path.

Question 600

A manufacturer uses FortiManager as an update source and needs evidence that a remote gateway recognizes the intended current intrusion-prevention package. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Use supported FortiManager FortiGuard service or FDS configuration to provide approved security update content to eligible managed or unmanaged FortiGates, preserving valid contracts and a verified update path. Verify: 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. Implement: 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. Verify: 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.
  3. Implement: Use supported FortiManager FortiGuard service or FDS configuration to provide approved security update content to eligible managed or unmanaged FortiGates, preserving valid contracts and a verified update path. Verify: In a test environment verify FortiManager has current permitted IPS and antivirus update packages, configure one FortiGate to reach its approved FDS endpoint and confirm the gateway receives an updated database.
  4. Implement: 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. Verify: In a test environment verify FortiManager has current permitted IPS and antivirus update packages, configure one FortiGate to reach its approved FDS endpoint and confirm the gateway receives an updated database.

Answer & Explanations

Correct answer: C

A.

The action is applicable: Use supported FortiManager FortiGuard service or FDS configuration to provide approved security update content to eligible managed or unmanaged FortiGates, preserving valid contracts and a verified update path. But its proposed test—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.—addresses “Distinguish FortiManager FortiGuard cache from managed update distribution”. This requirement is confirmed instead by: In a test environment verify FortiManager has current permitted IPS and antivirus update packages, configure one FortiGate to reach its approved FDS endpoint and confirm the gateway receives an updated database.

B.

This action/test pair addresses “Validate FortiGuard license status and firmware cache before a central update”. 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. 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. The case instead calls for: Use supported FortiManager FortiGuard service or FDS configuration to provide approved security update content to eligible managed or unmanaged FortiGates, preserving valid contracts and a verified update path.

C.

The question is set in this situation: A manufacturer uses FortiManager as an update source and needs evidence that a remote gateway recognizes the intended current intrusion-prevention package. Use supported FortiManager FortiGuard service or FDS configuration to provide approved security update content to eligible managed or unmanaged FortiGates, preserving valid contracts and a verified update path. Confirm it through this test: In a test environment verify FortiManager has current permitted IPS and antivirus update packages, configure one FortiGate to reach its approved FDS endpoint and confirm the gateway receives an updated database. A local FortiGuard distribution role can supply cached or distributed signature content where appropriate, but a server address override alone does not guarantee the update packages are present, licensed or compatible.

D.

The test would be relevant: In a test environment verify FortiManager has current permitted IPS and antivirus update packages, configure one FortiGate to reach its approved FDS endpoint and confirm the gateway receives an updated database. But the offered implementation—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.—addresses “Distinguish FortiManager FortiGuard cache from managed update distribution”. The action needed here is: Use supported FortiManager FortiGuard service or FDS configuration to provide approved security update content to eligible managed or unmanaged FortiGates, preserving valid contracts and a verified update path.

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