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 63

Question 620

A managed services provider is auditing a firmware rollout plan and needs to distinguish image cache readiness from client device entitlement and installation success. Which combined implementation and verification plan is the best match for this workload?

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

Answer & Explanations

Correct answer: D

A.

The action is applicable: 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. But its proposed 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.—addresses “Configure FortiManager as an authorized local FortiGuard Distribution Server”. This requirement is confirmed instead by: 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.

B.

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

C.

The test would be relevant: 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. But the offered implementation—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.—addresses “Configure FortiManager as an authorized local FortiGuard Distribution Server”. The action needed here is: 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.

D.

The question is set in this situation: A managed services provider is auditing a firmware rollout plan and needs to distinguish image cache readiness from client device entitlement and installation success. 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. Confirm it through this 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. 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.

Question 621

An MSP wants a common prohibited-service baseline across consenting customers while leaving each customer's local security policy independently administered. 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. 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. 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.

Answer & Explanations

Correct answer: B

A.

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

B.

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

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

D.

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

An MSP wants a common prohibited-service baseline across consenting customers while leaving each customer's local security policy independently administered. The engineer proposes the following change: 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. 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. 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.
  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 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.

Answer & Explanations

Correct answer: D

A.

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

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

C.

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

D.

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

An MSP wants a common prohibited-service baseline across consenting customers while leaving each customer's local security policy independently administered. After implementing this change—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.—which test most directly validates its intended outcome?

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

A.

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

B.

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

C.

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

D.

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

Question 624

An MSP wants a common prohibited-service baseline across consenting customers while leaving each customer's local security policy independently administered. Which proposed shortcut most directly risks unapproved cross-tenant filtering changes after global policy scope is assumed rather than explicitly managed and should therefore be rejected?

  1. Write one global firewall package and assume all managed customer ADOMs automatically install and enforce it regardless of global package assignment or review.
  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. 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.
  4. Use the words FortiGuard cache and FDS interchangeably and claim a gateway has current IPS signatures without checking the actual downloaded package version.

Answer & Explanations

Correct answer: A

A.

Write one global firewall package and assume all managed customer ADOMs automatically install and enforce it regardless of global package assignment or review. The foreseeable failure is unapproved cross-tenant filtering changes after global policy scope is assumed rather than explicitly managed. The safer response 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.

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

C.

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

D.

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

Question 625

An MSP wants a common prohibited-service baseline across consenting customers while leaving each customer's local security policy independently administered. 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: 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.
  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: 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.

Answer & Explanations

Correct answer: A

A.

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.

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.

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

D.

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.

Question 626

A multinational organization needs a globally reviewed access-control header in selected regional ADOMs but cannot change an isolated regulated subsidiary. 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. 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.
  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. 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: D

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

B.

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

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

Question 627

A multinational organization needs a globally reviewed access-control header in selected regional ADOMs but cannot change an isolated regulated subsidiary. The engineer proposes the following change: 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. 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: C

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

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

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

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

Question 628

A multinational organization needs a globally reviewed access-control header in selected regional ADOMs but cannot change an isolated regulated subsidiary. After implementing this change—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.—which test most directly validates its intended outcome?

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

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

B.

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

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

Question 629

A multinational organization needs a globally reviewed access-control header in selected regional ADOMs but cannot change an isolated regulated subsidiary. Which proposed shortcut most directly risks unapproved cross-tenant filtering changes after global policy scope is assumed rather than explicitly managed 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. 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. 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: D

A.

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

B.

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

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

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. Write one global firewall package and assume all managed customer ADOMs automatically install and enforce it regardless of global package assignment or review. The foreseeable failure is unapproved cross-tenant filtering changes after global policy scope is assumed rather than explicitly managed. The safer response 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 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.

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