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 64

Question 630

A multinational organization needs a globally reviewed access-control header in selected regional ADOMs but cannot change an isolated regulated subsidiary. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Create reviewed shared policy and object definitions in the supported Global ADOM, assign appropriate global policy packages to selected customer ADOMs and validate generated header or footer behavior. Verify: Create a harmless global deny rule for a test environment, assign it only to two permitted ADOMs, preview merged policy output and verify an unselected ADOM stays unchanged.
  2. 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.
  3. Implement: Create reviewed shared policy and object definitions in the supported Global ADOM, assign appropriate global policy packages to selected customer ADOMs and validate generated header or footer behavior. Verify: 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. Implement: 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. Verify: Create a harmless global deny rule for a test environment, assign it only to two permitted ADOMs, preview merged policy output and verify an unselected ADOM stays unchanged.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: A multinational organization needs a globally reviewed access-control header in selected regional ADOMs but cannot change an isolated regulated subsidiary. Create reviewed shared policy and object definitions in the supported Global ADOM, assign appropriate global policy packages to selected customer ADOMs and validate generated header or footer behavior. Confirm it through this test: Create a harmless global deny rule for a test environment, assign it only to two permitted ADOMs, preview merged policy output and verify an unselected ADOM stays unchanged. A Global ADOM permits controlled reuse of enterprise-wide policy elements; its assignments do not erase customer ADOM isolation or prove that every tenant accepted and installed the latest global package.

B.

This action/test pair addresses “Configure FortiManager as an authorized local FortiGuard Distribution Server”. 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. 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. The case instead calls for: Create reviewed shared policy and object definitions in the supported Global ADOM, assign appropriate global policy packages to selected customer ADOMs and validate generated header or footer behavior.

C.

The question is set in this situation: A multinational organization needs a globally reviewed access-control header in selected regional ADOMs but cannot change an isolated regulated subsidiary. The action is applicable: Create reviewed shared policy and object definitions in the supported Global ADOM, assign appropriate global policy packages to selected customer ADOMs and validate generated header or footer behavior. But its proposed test—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.—addresses “Validate the effect of a Global ADOM package on downstream policy order”. This requirement is confirmed instead by: Create a harmless global deny rule for a test environment, assign it only to two permitted ADOMs, preview merged policy output and verify an unselected ADOM stays unchanged.

D.

The question is set in this situation: A multinational organization needs a globally reviewed access-control header in selected regional ADOMs but cannot change an isolated regulated subsidiary. The test would be relevant: Create a harmless global deny rule for a test environment, assign it only to two permitted ADOMs, preview merged policy output and verify an unselected ADOM stays unchanged. But the offered implementation—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.—addresses “Validate the effect of a Global ADOM package on downstream policy order”. The action needed here is: Create reviewed shared policy and object definitions in the supported Global ADOM, assign appropriate global policy packages to selected customer ADOMs and validate generated header or footer behavior.

Question 631

A financial enterprise is deploying a global deny baseline while one regional branch has a local application permit that must be evaluated against the new header. 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. 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.
  4. Create reviewed shared policy and object definitions in the supported Global ADOM, assign appropriate global policy packages to selected customer ADOMs and validate generated header or footer behavior.

Answer & Explanations

Correct answer: C

A.

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

B.

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. This addresses “Configure FortiManager as an authorized local FortiGuard Distribution Server”, where the governing 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. The stated case instead calls for: 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.

C.

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

D.

Create reviewed shared policy and object definitions in the supported Global ADOM, assign appropriate global policy packages to selected customer ADOMs and validate generated header or footer behavior. This addresses “Use the FortiManager Global ADOM for shared header policy without abandoning tenant isolation”, where the governing principle is: A Global ADOM permits controlled reuse of enterprise-wide policy elements; its assignments do not erase customer ADOM isolation or prove that every tenant accepted and installed the latest global package. The stated case instead calls for: 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.

Question 632

A financial enterprise is deploying a global deny baseline while one regional branch has a local application permit that must be evaluated against the new header. The engineer proposes the following change: 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. 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 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.
  3. A Global ADOM permits controlled reuse of enterprise-wide policy elements; its assignments do not erase customer ADOM isolation or prove that every tenant accepted and installed the latest global package.
  4. 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.

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

B.

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

C.

A Global ADOM permits controlled reuse of enterprise-wide policy elements; its assignments do not erase customer ADOM isolation or prove that every tenant accepted and installed the latest global package. That explains “Use the FortiManager Global ADOM for shared header policy without abandoning tenant isolation”, not the mechanism behind the described change. The relevant principle is: 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.

D.

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. That explains “Configure FortiManager as an authorized local FortiGuard Distribution Server”, not the mechanism behind the described change. The relevant 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.

Question 633

A financial enterprise is deploying a global deny baseline while one regional branch has a local application permit that must be evaluated against the new header. After implementing this change—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.—which test most directly validates its intended outcome?

  1. Create a harmless global deny rule for a test environment, assign it only to two permitted ADOMs, preview merged policy output and verify an unselected ADOM stays unchanged.
  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. 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. 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.

Answer & Explanations

Correct answer: B

A.

Create a harmless global deny rule for a test environment, assign it only to two permitted ADOMs, preview merged policy output and verify an unselected ADOM stays unchanged. That would help test “Use the FortiManager Global ADOM for shared header policy without abandoning tenant isolation”, not the outcome required in this scenario. The relevant acceptance check is: 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.

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

C.

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. That would help test “Configure FortiManager as an authorized local FortiGuard Distribution Server”, not the outcome required in this scenario. The relevant acceptance check is: 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.

D.

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

Question 634

A financial enterprise is deploying a global deny baseline while one regional branch has a local application permit that must be evaluated against the new header. Which proposed shortcut most directly risks security policy shadowing or unexpected blocked traffic after global-to-local rule order is not validated 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. 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.
  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. Write one global firewall package and assume all managed customer ADOMs automatically install and enforce it regardless of global package assignment or review.

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

B.

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. That shortcut risks stale security protection after a local FortiGuard update path is configured without valid content distribution. Here the specific shortcut is: 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.

C.

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. The foreseeable failure is security policy shadowing or unexpected blocked traffic after global-to-local rule order is not validated. The safer response is: 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.

D.

Write one global firewall package and assume all managed customer ADOMs automatically install and enforce it regardless of global package assignment or review. That shortcut risks unapproved cross-tenant filtering changes after global policy scope is assumed rather than explicitly managed. Here the specific shortcut is: 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.

Question 635

A financial enterprise is deploying a global deny baseline while one regional branch has a local application permit that must be evaluated against the new header. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Create reviewed shared policy and object definitions in the supported Global ADOM, assign appropriate global policy packages to selected customer ADOMs and validate generated header or footer behavior. Verify: 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.
  2. 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.
  3. Implement: 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. Verify: Create a harmless global deny rule for a test environment, assign it only to two permitted ADOMs, preview merged policy output and verify an unselected ADOM stays unchanged.
  4. Implement: 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. Verify: 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.

Answer & Explanations

Correct answer: D

A.

The test would be relevant: 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. But the offered implementation—Create reviewed shared policy and object definitions in the supported Global ADOM, assign appropriate global policy packages to selected customer ADOMs and validate generated header or footer behavior.—addresses “Use the FortiManager Global ADOM for shared header policy without abandoning tenant isolation”. The action needed here is: 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.

B.

This action/test pair addresses “Configure FortiManager as an authorized local FortiGuard Distribution Server”. 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. 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. The case instead calls for: 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.

C.

The action is applicable: 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. But its proposed test—Create a harmless global deny rule for a test environment, assign it only to two permitted ADOMs, preview merged policy output and verify an unselected ADOM stays unchanged.—addresses “Use the FortiManager Global ADOM for shared header policy without abandoning tenant isolation”. This requirement is confirmed instead by: 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.

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. Confirm it through this test: 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. 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.

Question 636

A university is testing shared global management rules and needs to show how local package order changes the effective FortiGate policy after installation. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. 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.
  2. Create reviewed shared policy and object definitions in the supported Global ADOM, assign appropriate global policy packages to selected customer ADOMs and validate generated header or footer behavior.
  3. 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.
  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: A

A.

The question is set in this situation: A university is testing shared global management rules and needs to show how local package order changes the effective FortiGate policy after installation. 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. 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. Verify the result with this test: 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.

B.

The question is set in this situation: A university is testing shared global management rules and needs to show how local package order changes the effective FortiGate policy after installation. Create reviewed shared policy and object definitions in the supported Global ADOM, assign appropriate global policy packages to selected customer ADOMs and validate generated header or footer behavior. This addresses “Use the FortiManager Global ADOM for shared header policy without abandoning tenant isolation”, where the governing principle is: A Global ADOM permits controlled reuse of enterprise-wide policy elements; its assignments do not erase customer ADOM isolation or prove that every tenant accepted and installed the latest global package. The stated case instead calls for: 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.

C.

The question is set in this situation: A university is testing shared global management rules and needs to show how local package order changes the effective FortiGate policy after installation. 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. This addresses “Configure FortiManager as an authorized local FortiGuard Distribution Server”, where the governing 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. The stated case instead calls for: 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.

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

Question 637

A university is testing shared global management rules and needs to show how local package order changes the effective FortiGate policy after installation. The engineer proposes the following change: 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. Which mechanism explains why it works?

  1. 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.
  2. 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.
  3. A Global ADOM permits controlled reuse of enterprise-wide policy elements; its assignments do not erase customer ADOM isolation or prove that every tenant accepted and installed the latest global package.
  4. 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.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: A university is testing shared global management rules and needs to show how local package order changes the effective FortiGate policy after installation. 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 corresponding implementation is: 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.

B.

An HA transition may involve changes in which management peer owns connections; successful web access alone does not demonstrate managed gateways reconnect and policy installs work under the new management authority. That explains “Rehearse supported FortiManager HA failover and operator access recovery”, not the mechanism behind the described change. The relevant principle is: A 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.

C.

The question is set in this situation: A university is testing shared global management rules and needs to show how local package order changes the effective FortiGate policy after installation. A Global ADOM permits controlled reuse of enterprise-wide policy elements; its assignments do not erase customer ADOM isolation or prove that every tenant accepted and installed the latest global package. That explains “Use the FortiManager Global ADOM for shared header policy without abandoning tenant isolation”, not the mechanism behind the described change. The relevant principle is: 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.

D.

The question is set in this situation: A university is testing shared global management rules and needs to show how local package order changes the effective FortiGate policy after installation. 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. That explains “Configure FortiManager as an authorized local FortiGuard Distribution Server”, not the mechanism behind the described change. The relevant 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.

Question 638

A university is testing shared global management rules and needs to show how local package order changes the effective FortiGate policy after installation. After implementing this change—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.—which test most directly validates its intended outcome?

  1. Create a harmless global deny rule for a test environment, assign it only to two permitted ADOMs, preview merged policy output and verify an unselected ADOM stays unchanged.
  2. 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. 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. 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.

Answer & Explanations

Correct answer: D

A.

The question is set in this situation: A university is testing shared global management rules and needs to show how local package order changes the effective FortiGate policy after installation. Create a harmless global deny rule for a test environment, assign it only to two permitted ADOMs, preview merged policy output and verify an unselected ADOM stays unchanged. That would help test “Use the FortiManager Global ADOM for shared header policy without abandoning tenant isolation”, not the outcome required in this scenario. The relevant acceptance check is: 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.

B.

The question is set in this situation: A university is testing shared global management rules and needs to show how local package order changes the effective FortiGate policy after installation. 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. That would help test “Configure FortiManager as an authorized local FortiGuard Distribution Server”, not the outcome required in this scenario. The relevant acceptance check is: 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.

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

D.

The question is set in this situation: A university is testing shared global management rules and needs to show how local package order changes the effective FortiGate policy after installation. 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. This check is decisive because 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.

Question 639

A university is testing shared global management rules and needs to show how local package order changes the effective FortiGate policy after installation. Which proposed shortcut most directly risks security policy shadowing or unexpected blocked traffic after global-to-local rule order is not validated and should therefore be rejected?

  1. 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.
  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. Write one global firewall package and assume all managed customer ADOMs automatically install and enforce it regardless of global package assignment or review.
  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: B

A.

The question is set in this situation: A university is testing shared global management rules and needs to show how local package order changes the effective FortiGate policy after installation. 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. That shortcut risks stale security protection after a local FortiGuard update path is configured without valid content distribution. Here the specific shortcut is: 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.

B.

The question is set in this situation: A university is testing shared global management rules and needs to show how local package order changes the effective FortiGate policy after installation. 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. The foreseeable failure is security policy shadowing or unexpected blocked traffic after global-to-local rule order is not validated. The safer response is: 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.

C.

The question is set in this situation: A university is testing shared global management rules and needs to show how local package order changes the effective FortiGate policy after installation. Write one global firewall package and assume all managed customer ADOMs automatically install and enforce it regardless of global package assignment or review. That shortcut risks unapproved cross-tenant filtering changes after global policy scope is assumed rather than explicitly managed. Here the specific shortcut is: 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.

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

Question 640

A university is testing shared global management rules and needs to show how local package order changes the effective FortiGate policy after installation. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: 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. Verify: Create a harmless global deny rule for a test environment, assign it only to two permitted ADOMs, preview merged policy output and verify an unselected ADOM stays unchanged.
  2. Implement: Create reviewed shared policy and object definitions in the supported Global ADOM, assign appropriate global policy packages to selected customer ADOMs and validate generated header or footer behavior. Verify: 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. Implement: 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. Verify: 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. 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 question is set in this situation: A university is testing shared global management rules and needs to show how local package order changes the effective FortiGate policy after installation. The action is applicable: 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. But its proposed test—Create a harmless global deny rule for a test environment, assign it only to two permitted ADOMs, preview merged policy output and verify an unselected ADOM stays unchanged.—addresses “Use the FortiManager Global ADOM for shared header policy without abandoning tenant isolation”. This requirement is confirmed instead by: 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.

B.

The question is set in this situation: A university is testing shared global management rules and needs to show how local package order changes the effective FortiGate policy after installation. The test would be relevant: 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. But the offered implementation—Create reviewed shared policy and object definitions in the supported Global ADOM, assign appropriate global policy packages to selected customer ADOMs and validate generated header or footer behavior.—addresses “Use the FortiManager Global ADOM for shared header policy without abandoning tenant isolation”. The action needed here is: 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.

C.

The question is set in this situation: A university is testing shared global management rules and needs to show how local package order changes the effective FortiGate policy after installation. 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. Confirm it through this test: 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. 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.

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

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