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 22

Question 210

A bank's new data center has an HA firewall pair and its central team needs policy installation to honor cluster relationships rather than stand-alone device assumptions. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Discover a FortiGate HA cluster using supported FortiManager procedures, verify cluster identity and member status, and use an appropriate cluster target when managing shared policy and device configuration. Verify: Review current managed-device count and licensing on an authorized FortiManager instance, add a lab device within the approved capacity, and document a scale decision before exceeding it.
  2. Implement: Use the supported Add Device workflow with the intended ADOM, correct management IP and authenticated FortiGate authorization, confirm FGFM communication and review the initial import report before declaring it managed. Verify: Register a staging firewall with FortiManager access allowed, inspect the device's serial number and managed status, retrieve its initial configuration and confirm the intended ADOM owns it.
  3. Implement: Discover a FortiGate HA cluster using supported FortiManager procedures, verify cluster identity and member status, and use an appropriate cluster target when managing shared policy and device configuration. Verify: Add a staged two-member FortiGate cluster, inspect primary and secondary member information, install one harmless policy change through the proper managed target, and check both members remain healthy.
  4. Implement: Check FortiManager platform and license device-management capacity against the expected number of registered devices, confirm supported scale and reserve room for HA clusters and planned growth. Verify: Add a staged two-member FortiGate cluster, inspect primary and secondary member information, install one harmless policy change through the proper managed target, and check both members remain healthy.

Answer & Explanations

Correct answer: C

A.

The action is applicable: Discover a FortiGate HA cluster using supported FortiManager procedures, verify cluster identity and member status, and use an appropriate cluster target when managing shared policy and device configuration. But its proposed test—Review current managed-device count and licensing on an authorized FortiManager instance, add a lab device within the approved capacity, and document a scale decision before exceeding it.—addresses “Account for FortiManager managed device capacity and entitlement before expansion”. This requirement is confirmed instead by: Add a staged two-member FortiGate cluster, inspect primary and secondary member information, install one harmless policy change through the proper managed target, and check both members remain healthy.

B.

This action/test pair addresses “Register a reachable FortiGate through the FortiManager Add Device wizard”. Use the supported Add Device workflow with the intended ADOM, correct management IP and authenticated FortiGate authorization, confirm FGFM communication and review the initial import report before declaring it managed. Register a staging firewall with FortiManager access allowed, inspect the device's serial number and managed status, retrieve its initial configuration and confirm the intended ADOM owns it. The case instead calls for: Discover a FortiGate HA cluster using supported FortiManager procedures, verify cluster identity and member status, and use an appropriate cluster target when managing shared policy and device configuration.

C.

The question is set in this situation: A bank's new data center has an HA firewall pair and its central team needs policy installation to honor cluster relationships rather than stand-alone device assumptions. Discover a FortiGate HA cluster using supported FortiManager procedures, verify cluster identity and member status, and use an appropriate cluster target when managing shared policy and device configuration. Confirm it through this test: Add a staged two-member FortiGate cluster, inspect primary and secondary member information, install one harmless policy change through the proper managed target, and check both members remain healthy. Multiple FortiGate HA member serial numbers do not necessarily represent independent production policy targets; a cluster has shared identity, synchronization state and supported installation behavior that must be understood.

D.

The test would be relevant: Add a staged two-member FortiGate cluster, inspect primary and secondary member information, install one harmless policy change through the proper managed target, and check both members remain healthy. But the offered implementation—Check FortiManager platform and license device-management capacity against the expected number of registered devices, confirm supported scale and reserve room for HA clusters and planned growth.—addresses “Account for FortiManager managed device capacity and entitlement before expansion”. The action needed here is: Discover a FortiGate HA cluster using supported FortiManager procedures, verify cluster identity and member status, and use an appropriate cluster target when managing shared policy and device configuration.

Question 211

A chain of retail stores wants to deploy a reviewed policy in regional waves while retaining a single enterprise ADOM. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. Match a FortiManager script's execution environment, command hierarchy and supported FortiOS version to the intended managed devices, and test commands in a compatible staging firewall before scheduling production execution.
  2. Copy a reviewed system template into another supported ADOM while validating version compatibility, referenced interfaces and device-specific variables before assigning it to the destination tenant.
  3. Create a reviewed FortiManager system template for common permitted device settings, associate it with an approved device group, and validate per-device variables before a controlled install.
  4. Create FortiManager device groups for operational rollouts inside an approved ADOM, use them as scheduling or target aids, and maintain ADOM-level access controls separately.

Answer & Explanations

Correct answer: D

A.

Match a FortiManager script's execution environment, command hierarchy and supported FortiOS version to the intended managed devices, and test commands in a compatible staging firewall before scheduling production execution. This addresses “Choose script context and supported FortiOS syntax before bulk execution”, where the governing principle is: Commands accepted on one FortiOS release or config subtree may fail in another context; FortiManager task submission success does not prove every child command was executed correctly. The stated case instead calls for: Create FortiManager device groups for operational rollouts inside an approved ADOM, use them as scheduling or target aids, and maintain ADOM-level access controls separately.

B.

Copy a reviewed system template into another supported ADOM while validating version compatibility, referenced interfaces and device-specific variables before assigning it to the destination tenant. This addresses “Move a FortiManager provisioning template between compatible ADOMs safely”, where the governing principle is: An ADOM copy can preserve template logic while omitting assumptions about destination devices or permissions; identical text can have different effects across firmware versions or interface inventories. The stated case instead calls for: Create FortiManager device groups for operational rollouts inside an approved ADOM, use them as scheduling or target aids, and maintain ADOM-level access controls separately.

C.

Create a reviewed FortiManager system template for common permitted device settings, associate it with an approved device group, and validate per-device variables before a controlled install. This addresses “Apply a system template to standardize appropriate FortiGate device settings”, where the governing principle is: Provisioning templates support consistent settings across many devices, but differing interfaces and regional network addresses still require device-aware mappings rather than blind identical values. The stated case instead calls for: Create FortiManager device groups for operational rollouts inside an approved ADOM, use them as scheduling or target aids, and maintain ADOM-level access controls separately.

D.

Create FortiManager device groups for operational rollouts inside an approved ADOM, use them as scheduling or target aids, and maintain ADOM-level access controls separately. Device groups help administrators organize and select devices but do not replace ADOM database boundaries; a shared group label cannot prevent unauthorized object modification across customers. Verify the result with this test: Build a sample group of three staged branch FortiGates, target a harmless approved update, and show an administrator outside the ADOM remains unable to edit the group's policy package.

Question 212

A chain of retail stores wants to deploy a reviewed policy in regional waves while retaining a single enterprise ADOM. The engineer proposes the following change: Create FortiManager device groups for operational rollouts inside an approved ADOM, use them as scheduling or target aids, and maintain ADOM-level access controls separately. Which mechanism explains why it works?

  1. Device groups help administrators organize and select devices but do not replace ADOM database boundaries; a shared group label cannot prevent unauthorized object modification across customers.
  2. Commands accepted on one FortiOS release or config subtree may fail in another context; FortiManager task submission success does not prove every child command was executed correctly.
  3. An ADOM copy can preserve template logic while omitting assumptions about destination devices or permissions; identical text can have different effects across firmware versions or interface inventories.
  4. Provisioning templates support consistent settings across many devices, but differing interfaces and regional network addresses still require device-aware mappings rather than blind identical values.

Answer & Explanations

Correct answer: A

A.

Device groups help administrators organize and select devices but do not replace ADOM database boundaries; a shared group label cannot prevent unauthorized object modification across customers. The corresponding implementation is: Create FortiManager device groups for operational rollouts inside an approved ADOM, use them as scheduling or target aids, and maintain ADOM-level access controls separately.

B.

Commands accepted on one FortiOS release or config subtree may fail in another context; FortiManager task submission success does not prove every child command was executed correctly. That explains “Choose script context and supported FortiOS syntax before bulk execution”, not the mechanism behind the described change. The relevant principle is: Device groups help administrators organize and select devices but do not replace ADOM database boundaries; a shared group label cannot prevent unauthorized object modification across customers.

C.

An ADOM copy can preserve template logic while omitting assumptions about destination devices or permissions; identical text can have different effects across firmware versions or interface inventories. That explains “Move a FortiManager provisioning template between compatible ADOMs safely”, not the mechanism behind the described change. The relevant principle is: Device groups help administrators organize and select devices but do not replace ADOM database boundaries; a shared group label cannot prevent unauthorized object modification across customers.

D.

Provisioning templates support consistent settings across many devices, but differing interfaces and regional network addresses still require device-aware mappings rather than blind identical values. That explains “Apply a system template to standardize appropriate FortiGate device settings”, not the mechanism behind the described change. The relevant principle is: Device groups help administrators organize and select devices but do not replace ADOM database boundaries; a shared group label cannot prevent unauthorized object modification across customers.

Question 213

A chain of retail stores wants to deploy a reviewed policy in regional waves while retaining a single enterprise ADOM. After implementing this change—Create FortiManager device groups for operational rollouts inside an approved ADOM, use them as scheduling or target aids, and maintain ADOM-level access controls separately.—which test most directly validates its intended outcome?

  1. Copy a sample template from an internal lab ADOM to a separate test tenant, compare object references and target compatibility, and test deployment to one noncritical firewall.
  2. Assign a template to two staging FortiGates with different management addresses, preview intended changes, install only approved settings and confirm each device retains its unique required identity.
  3. Build a sample group of three staged branch FortiGates, target a harmless approved update, and show an administrator outside the ADOM remains unable to edit the group's policy package.
  4. Run a version-appropriate test script on two firmware variants in a lab, inspect per-device output and changed configuration, and revise the script where a command is unsupported.

Answer & Explanations

Correct answer: C

A.

Copy a sample template from an internal lab ADOM to a separate test tenant, compare object references and target compatibility, and test deployment to one noncritical firewall. That would help test “Move a FortiManager provisioning template between compatible ADOMs safely”, not the outcome required in this scenario. The relevant acceptance check is: Build a sample group of three staged branch FortiGates, target a harmless approved update, and show an administrator outside the ADOM remains unable to edit the group's policy package.

B.

Assign a template to two staging FortiGates with different management addresses, preview intended changes, install only approved settings and confirm each device retains its unique required identity. That would help test “Apply a system template to standardize appropriate FortiGate device settings”, not the outcome required in this scenario. The relevant acceptance check is: Build a sample group of three staged branch FortiGates, target a harmless approved update, and show an administrator outside the ADOM remains unable to edit the group's policy package.

C.

Build a sample group of three staged branch FortiGates, target a harmless approved update, and show an administrator outside the ADOM remains unable to edit the group's policy package. This check is decisive because device groups help administrators organize and select devices but do not replace ADOM database boundaries; a shared group label cannot prevent unauthorized object modification across customers.

D.

Run a version-appropriate test script on two firmware variants in a lab, inspect per-device output and changed configuration, and revise the script where a command is unsupported. That would help test “Choose script context and supported FortiOS syntax before bulk execution”, not the outcome required in this scenario. The relevant acceptance check is: Build a sample group of three staged branch FortiGates, target a harmless approved update, and show an administrator outside the ADOM remains unable to edit the group's policy package.

Question 214

A chain of retail stores wants to deploy a reviewed policy in regional waves while retaining a single enterprise ADOM. Which proposed shortcut most directly risks tenant policy exposure after incorrectly treating FortiManager device groups as security boundaries and should therefore be rejected?

  1. Copy one gateway's entire network interface configuration blindly to a fleet of remote branches and assume identical static IP addresses cannot create conflicts.
  2. Assume transferring a template across ADOMs automatically migrates all customer credentials, interface names and version-specific commands without review.
  3. Copy CLI lines from a different Fortinet product and execute them unmodified across mixed FortiOS releases while interpreting a submitted task as complete success.
  4. Place two tenants in a single unrestricted ADOM and claim that creating separate device groups guarantees legal customer data isolation and separate object administration.

Answer & Explanations

Correct answer: D

A.

Copy one gateway's entire network interface configuration blindly to a fleet of remote branches and assume identical static IP addresses cannot create conflicts. That shortcut risks widespread branch management outages after an unparameterized shared template overwrites unique network settings. Here the specific shortcut is: Place two tenants in a single unrestricted ADOM and claim that creating separate device groups guarantees legal customer data isolation and separate object administration.

B.

Assume transferring a template across ADOMs automatically migrates all customer credentials, interface names and version-specific commands without review. That shortcut risks cross-tenant configuration errors after reusing an incompatible shared provisioning template. Here the specific shortcut is: Place two tenants in a single unrestricted ADOM and claim that creating separate device groups guarantees legal customer data isolation and separate object administration.

C.

Copy CLI lines from a different Fortinet product and execute them unmodified across mixed FortiOS releases while interpreting a submitted task as complete success. That shortcut risks partial configuration deployment after script command syntax or context is incompatible with target gateways. Here the specific shortcut is: Place two tenants in a single unrestricted ADOM and claim that creating separate device groups guarantees legal customer data isolation and separate object administration.

D.

Place two tenants in a single unrestricted ADOM and claim that creating separate device groups guarantees legal customer data isolation and separate object administration. The foreseeable failure is tenant policy exposure after incorrectly treating FortiManager device groups as security boundaries. The safer response is: Create FortiManager device groups for operational rollouts inside an approved ADOM, use them as scheduling or target aids, and maintain ADOM-level access controls separately.

Question 215

A chain of retail stores wants to deploy a reviewed policy in regional waves while retaining a single enterprise ADOM. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Create a reviewed FortiManager system template for common permitted device settings, associate it with an approved device group, and validate per-device variables before a controlled install. Verify: Build a sample group of three staged branch FortiGates, target a harmless approved update, and show an administrator outside the ADOM remains unable to edit the group's policy package.
  2. Implement: Create FortiManager device groups for operational rollouts inside an approved ADOM, use them as scheduling or target aids, and maintain ADOM-level access controls separately. Verify: Build a sample group of three staged branch FortiGates, target a harmless approved update, and show an administrator outside the ADOM remains unable to edit the group's policy package.
  3. Implement: Copy a reviewed system template into another supported ADOM while validating version compatibility, referenced interfaces and device-specific variables before assigning it to the destination tenant. Verify: Copy a sample template from an internal lab ADOM to a separate test tenant, compare object references and target compatibility, and test deployment to one noncritical firewall.
  4. Implement: Create FortiManager device groups for operational rollouts inside an approved ADOM, use them as scheduling or target aids, and maintain ADOM-level access controls separately. Verify: Assign a template to two staging FortiGates with different management addresses, preview intended changes, install only approved settings and confirm each device retains its unique required identity.

Answer & Explanations

Correct answer: B

A.

The test would be relevant: Build a sample group of three staged branch FortiGates, target a harmless approved update, and show an administrator outside the ADOM remains unable to edit the group's policy package. But the offered implementation—Create a reviewed FortiManager system template for common permitted device settings, associate it with an approved device group, and validate per-device variables before a controlled install.—addresses “Apply a system template to standardize appropriate FortiGate device settings”. The action needed here is: Create FortiManager device groups for operational rollouts inside an approved ADOM, use them as scheduling or target aids, and maintain ADOM-level access controls separately.

B.

Create FortiManager device groups for operational rollouts inside an approved ADOM, use them as scheduling or target aids, and maintain ADOM-level access controls separately. Confirm it through this test: Build a sample group of three staged branch FortiGates, target a harmless approved update, and show an administrator outside the ADOM remains unable to edit the group's policy package. Device groups help administrators organize and select devices but do not replace ADOM database boundaries; a shared group label cannot prevent unauthorized object modification across customers.

C.

This action/test pair addresses “Move a FortiManager provisioning template between compatible ADOMs safely”. Copy a reviewed system template into another supported ADOM while validating version compatibility, referenced interfaces and device-specific variables before assigning it to the destination tenant. Copy a sample template from an internal lab ADOM to a separate test tenant, compare object references and target compatibility, and test deployment to one noncritical firewall. The case instead calls for: Create FortiManager device groups for operational rollouts inside an approved ADOM, use them as scheduling or target aids, and maintain ADOM-level access controls separately.

D.

The action is applicable: Create FortiManager device groups for operational rollouts inside an approved ADOM, use them as scheduling or target aids, and maintain ADOM-level access controls separately. But its proposed test—Assign a template to two staging FortiGates with different management addresses, preview intended changes, install only approved settings and confirm each device retains its unique required identity.—addresses “Apply a system template to standardize appropriate FortiGate device settings”. This requirement is confirmed instead by: Build a sample group of three staged branch FortiGates, target a harmless approved update, and show an administrator outside the ADOM remains unable to edit the group's policy package.

Question 216

A managed security firm is deciding when to use groups for device rollout and when separate ADOMs are necessary for customer isolation. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. Create FortiManager device groups for operational rollouts inside an approved ADOM, use them as scheduling or target aids, and maintain ADOM-level access controls separately.
  2. Review FortiManager's import wizard report for existing gateway policies, interfaces and dependent objects, resolve missing references and decide whether to preserve or replace local configuration before installing central changes.
  3. Check FortiManager platform and license device-management capacity against the expected number of registered devices, confirm supported scale and reserve room for HA clusters and planned growth.
  4. Compare a managed device's current stored revision with the last approved revision, locate the precise changed settings, and apply a supported restoration or central redeployment after appropriate review.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: A managed security firm is deciding when to use groups for device rollout and when separate ADOMs are necessary for customer isolation. Create FortiManager device groups for operational rollouts inside an approved ADOM, use them as scheduling or target aids, and maintain ADOM-level access controls separately. Device groups help administrators organize and select devices but do not replace ADOM database boundaries; a shared group label cannot prevent unauthorized object modification across customers. Verify the result with this test: Build a sample group of three staged branch FortiGates, target a harmless approved update, and show an administrator outside the ADOM remains unable to edit the group's policy package.

B.

Review FortiManager's import wizard report for existing gateway policies, interfaces and dependent objects, resolve missing references and decide whether to preserve or replace local configuration before installing central changes. This addresses “Reconcile an imported configuration report before first FortiManager policy installation”, where the governing principle is: Import moves a snapshot of current FortiGate policy into central management scope; unreadable objects or interface mappings can produce later install errors when local and intended central databases differ. The stated case instead calls for: Create FortiManager device groups for operational rollouts inside an approved ADOM, use them as scheduling or target aids, and maintain ADOM-level access controls separately.

C.

Check FortiManager platform and license device-management capacity against the expected number of registered devices, confirm supported scale and reserve room for HA clusters and planned growth. This addresses “Account for FortiManager managed device capacity and entitlement before expansion”, where the governing principle is: Central management limits are not removed by renaming devices or adding ADOMs; exceeding supported capacity can block new registrations and make a deployment plan operationally invalid. The stated case instead calls for: Create FortiManager device groups for operational rollouts inside an approved ADOM, use them as scheduling or target aids, and maintain ADOM-level access controls separately.

D.

Compare a managed device's current stored revision with the last approved revision, locate the precise changed settings, and apply a supported restoration or central redeployment after appropriate review. This addresses “Use FortiManager device revision history to identify and repair drift”, where the governing principle is: Device revision history helps reconstruct configuration changes and revert known states, while snapshots are not the same as an ADOM-wide policy/object database revision. The stated case instead calls for: Create FortiManager device groups for operational rollouts inside an approved ADOM, use them as scheduling or target aids, and maintain ADOM-level access controls separately.

Question 217

A managed security firm is deciding when to use groups for device rollout and when separate ADOMs are necessary for customer isolation. The engineer proposes the following change: Create FortiManager device groups for operational rollouts inside an approved ADOM, use them as scheduling or target aids, and maintain ADOM-level access controls separately. Which mechanism explains why it works?

  1. Device revision history helps reconstruct configuration changes and revert known states, while snapshots are not the same as an ADOM-wide policy/object database revision.
  2. Device groups help administrators organize and select devices but do not replace ADOM database boundaries; a shared group label cannot prevent unauthorized object modification across customers.
  3. Central management limits are not removed by renaming devices or adding ADOMs; exceeding supported capacity can block new registrations and make a deployment plan operationally invalid.
  4. Import moves a snapshot of current FortiGate policy into central management scope; unreadable objects or interface mappings can produce later install errors when local and intended central databases differ.

Answer & Explanations

Correct answer: B

A.

Device revision history helps reconstruct configuration changes and revert known states, while snapshots are not the same as an ADOM-wide policy/object database revision. That explains “Use FortiManager device revision history to identify and repair drift”, not the mechanism behind the described change. The relevant principle is: Device groups help administrators organize and select devices but do not replace ADOM database boundaries; a shared group label cannot prevent unauthorized object modification across customers.

B.

The question is set in this situation: A managed security firm is deciding when to use groups for device rollout and when separate ADOMs are necessary for customer isolation. Device groups help administrators organize and select devices but do not replace ADOM database boundaries; a shared group label cannot prevent unauthorized object modification across customers. The corresponding implementation is: Create FortiManager device groups for operational rollouts inside an approved ADOM, use them as scheduling or target aids, and maintain ADOM-level access controls separately.

C.

Central management limits are not removed by renaming devices or adding ADOMs; exceeding supported capacity can block new registrations and make a deployment plan operationally invalid. That explains “Account for FortiManager managed device capacity and entitlement before expansion”, not the mechanism behind the described change. The relevant principle is: Device groups help administrators organize and select devices but do not replace ADOM database boundaries; a shared group label cannot prevent unauthorized object modification across customers.

D.

Import moves a snapshot of current FortiGate policy into central management scope; unreadable objects or interface mappings can produce later install errors when local and intended central databases differ. That explains “Reconcile an imported configuration report before first FortiManager policy installation”, not the mechanism behind the described change. The relevant principle is: Device groups help administrators organize and select devices but do not replace ADOM database boundaries; a shared group label cannot prevent unauthorized object modification across customers.

Question 218

A managed security firm is deciding when to use groups for device rollout and when separate ADOMs are necessary for customer isolation. After implementing this change—Create FortiManager device groups for operational rollouts inside an approved ADOM, use them as scheduling or target aids, and maintain ADOM-level access controls separately.—which test most directly validates its intended outcome?

  1. Import a staging gateway with a known local rule and custom address object, compare the central package and mappings with its running state, and record a reviewed no-surprise install plan.
  2. Review current managed-device count and licensing on an authorized FortiManager instance, add a lab device within the approved capacity, and document a scale decision before exceeding it.
  3. Build a sample group of three staged branch FortiGates, target a harmless approved update, and show an administrator outside the ADOM remains unable to edit the group's policy package.
  4. Modify a safe lab interface description, retrieve the new revision, compare with the baseline and restore an approved version without deleting unrelated ADOM policy objects.

Answer & Explanations

Correct answer: C

A.

Import a staging gateway with a known local rule and custom address object, compare the central package and mappings with its running state, and record a reviewed no-surprise install plan. That would help test “Reconcile an imported configuration report before first FortiManager policy installation”, not the outcome required in this scenario. The relevant acceptance check is: Build a sample group of three staged branch FortiGates, target a harmless approved update, and show an administrator outside the ADOM remains unable to edit the group's policy package.

B.

Review current managed-device count and licensing on an authorized FortiManager instance, add a lab device within the approved capacity, and document a scale decision before exceeding it. That would help test “Account for FortiManager managed device capacity and entitlement before expansion”, not the outcome required in this scenario. The relevant acceptance check is: Build a sample group of three staged branch FortiGates, target a harmless approved update, and show an administrator outside the ADOM remains unable to edit the group's policy package.

C.

The question is set in this situation: A managed security firm is deciding when to use groups for device rollout and when separate ADOMs are necessary for customer isolation. Build a sample group of three staged branch FortiGates, target a harmless approved update, and show an administrator outside the ADOM remains unable to edit the group's policy package. This check is decisive because device groups help administrators organize and select devices but do not replace ADOM database boundaries; a shared group label cannot prevent unauthorized object modification across customers.

D.

Modify a safe lab interface description, retrieve the new revision, compare with the baseline and restore an approved version without deleting unrelated ADOM policy objects. That would help test “Use FortiManager device revision history to identify and repair drift”, not the outcome required in this scenario. The relevant acceptance check is: Build a sample group of three staged branch FortiGates, target a harmless approved update, and show an administrator outside the ADOM remains unable to edit the group's policy package.

Question 219

A managed security firm is deciding when to use groups for device rollout and when separate ADOMs are necessary for customer isolation. Which proposed shortcut most directly risks tenant policy exposure after incorrectly treating FortiManager device groups as security boundaries and should therefore be rejected?

  1. Place two tenants in a single unrestricted ADOM and claim that creating separate device groups guarantees legal customer data isolation and separate object administration.
  2. Assume creating dozens of ADOMs multiplies a FortiManager appliance's licensed device count indefinitely without purchasing capacity or verifying platform limits.
  3. Install an empty default FortiManager package over a production FortiGate immediately after registration without checking which live rules the import wizard recognized.
  4. Revert an arbitrary old revision without comparing what changed and assume every ADOM policy package and management administrator account must also roll back.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: A managed security firm is deciding when to use groups for device rollout and when separate ADOMs are necessary for customer isolation. Place two tenants in a single unrestricted ADOM and claim that creating separate device groups guarantees legal customer data isolation and separate object administration. The foreseeable failure is tenant policy exposure after incorrectly treating FortiManager device groups as security boundaries. The safer response is: Create FortiManager device groups for operational rollouts inside an approved ADOM, use them as scheduling or target aids, and maintain ADOM-level access controls separately.

B.

Assume creating dozens of ADOMs multiplies a FortiManager appliance's licensed device count indefinitely without purchasing capacity or verifying platform limits. That shortcut risks failed enterprise expansion when central device-management scale is assumed unlimited. Here the specific shortcut is: Place two tenants in a single unrestricted ADOM and claim that creating separate device groups guarantees legal customer data isolation and separate object administration.

C.

Install an empty default FortiManager package over a production FortiGate immediately after registration without checking which live rules the import wizard recognized. That shortcut risks unexpected disruption to permitted traffic after uncontrolled replacement of existing firewall rules during onboarding. Here the specific shortcut is: Place two tenants in a single unrestricted ADOM and claim that creating separate device groups guarantees legal customer data isolation and separate object administration.

D.

Revert an arbitrary old revision without comparing what changed and assume every ADOM policy package and management administrator account must also roll back. That shortcut risks accidental loss of legitimate device changes after treating a device revision as a complete FortiManager restore point. Here the specific shortcut is: Place two tenants in a single unrestricted ADOM and claim that creating separate device groups guarantees legal customer data isolation and separate object administration.

Question 220

A managed security firm is deciding when to use groups for device rollout and when separate ADOMs are necessary for customer isolation. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Review FortiManager's import wizard report for existing gateway policies, interfaces and dependent objects, resolve missing references and decide whether to preserve or replace local configuration before installing central changes. Verify: Build a sample group of three staged branch FortiGates, target a harmless approved update, and show an administrator outside the ADOM remains unable to edit the group's policy package.
  2. Implement: Create FortiManager device groups for operational rollouts inside an approved ADOM, use them as scheduling or target aids, and maintain ADOM-level access controls separately. Verify: Import a staging gateway with a known local rule and custom address object, compare the central package and mappings with its running state, and record a reviewed no-surprise install plan.
  3. Implement: Check FortiManager platform and license device-management capacity against the expected number of registered devices, confirm supported scale and reserve room for HA clusters and planned growth. Verify: Review current managed-device count and licensing on an authorized FortiManager instance, add a lab device within the approved capacity, and document a scale decision before exceeding it.
  4. Implement: Create FortiManager device groups for operational rollouts inside an approved ADOM, use them as scheduling or target aids, and maintain ADOM-level access controls separately. Verify: Build a sample group of three staged branch FortiGates, target a harmless approved update, and show an administrator outside the ADOM remains unable to edit the group's policy package.

Answer & Explanations

Correct answer: D

A.

The test would be relevant: Build a sample group of three staged branch FortiGates, target a harmless approved update, and show an administrator outside the ADOM remains unable to edit the group's policy package. But the offered implementation—Review FortiManager's import wizard report for existing gateway policies, interfaces and dependent objects, resolve missing references and decide whether to preserve or replace local configuration before installing central changes.—addresses “Reconcile an imported configuration report before first FortiManager policy installation”. The action needed here is: Create FortiManager device groups for operational rollouts inside an approved ADOM, use them as scheduling or target aids, and maintain ADOM-level access controls separately.

B.

The action is applicable: Create FortiManager device groups for operational rollouts inside an approved ADOM, use them as scheduling or target aids, and maintain ADOM-level access controls separately. But its proposed test—Import a staging gateway with a known local rule and custom address object, compare the central package and mappings with its running state, and record a reviewed no-surprise install plan.—addresses “Reconcile an imported configuration report before first FortiManager policy installation”. This requirement is confirmed instead by: Build a sample group of three staged branch FortiGates, target a harmless approved update, and show an administrator outside the ADOM remains unable to edit the group's policy package.

C.

This action/test pair addresses “Account for FortiManager managed device capacity and entitlement before expansion”. Check FortiManager platform and license device-management capacity against the expected number of registered devices, confirm supported scale and reserve room for HA clusters and planned growth. Review current managed-device count and licensing on an authorized FortiManager instance, add a lab device within the approved capacity, and document a scale decision before exceeding it. The case instead calls for: Create FortiManager device groups for operational rollouts inside an approved ADOM, use them as scheduling or target aids, and maintain ADOM-level access controls separately.

D.

The question is set in this situation: A managed security firm is deciding when to use groups for device rollout and when separate ADOMs are necessary for customer isolation. Create FortiManager device groups for operational rollouts inside an approved ADOM, use them as scheduling or target aids, and maintain ADOM-level access controls separately. Confirm it through this test: Build a sample group of three staged branch FortiGates, target a harmless approved update, and show an administrator outside the ADOM remains unable to edit the group's policy package. Device groups help administrators organize and select devices but do not replace ADOM database boundaries; a shared group label cannot prevent unauthorized object modification across customers.

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