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 23

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.

Question 221

A financial branch already runs local firewall policies and its new FortiManager owner needs to import them without interrupting payment applications. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. Use a supported FortiManager model device entry with an approved blueprint and correct serial or authorization data, then bind the physical FortiGate when it comes online and reconcile actual configuration.
  2. Use FortiManager's supported script scheduling and permission workflow to execute approved changes at designated times, accounting for device availability and a rollback or postexecution verification check.
  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. 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.

Answer & Explanations

Correct answer: D

A.

Use a supported FortiManager model device entry with an approved blueprint and correct serial or authorization data, then bind the physical FortiGate when it comes online and reconcile actual configuration. This addresses “Create a model device for a FortiGate not yet physically connected”, where the governing principle is: A model device is a planned representation for preprovisioning and does not prove the future hardware is reachable; matching the real device securely is required before intended settings can be pushed and verified. The stated case instead calls for: 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.

B.

Use FortiManager's supported script scheduling and permission workflow to execute approved changes at designated times, accounting for device availability and a rollback or postexecution verification check. This addresses “Schedule scripts within controlled FortiManager maintenance windows”, where the governing principle is: A scheduled task merely queues central execution; devices may be disconnected or reject commands, so the operator must inspect per-device results rather than infer success from the calendar event. The stated case instead calls for: 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.

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

D.

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

Question 222

A financial branch already runs local firewall policies and its new FortiManager owner needs to import them without interrupting payment applications. The engineer proposes the following change: 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. Which mechanism explains why it works?

  1. 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.
  2. 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.
  3. A scheduled task merely queues central execution; devices may be disconnected or reject commands, so the operator must inspect per-device results rather than infer success from the calendar event.
  4. A model device is a planned representation for preprovisioning and does not prove the future hardware is reachable; matching the real device securely is required before intended settings can be pushed and verified.

Answer & Explanations

Correct answer: B

A.

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

B.

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

C.

A scheduled task merely queues central execution; devices may be disconnected or reject commands, so the operator must inspect per-device results rather than infer success from the calendar event. That explains “Schedule scripts within controlled FortiManager maintenance windows”, not the mechanism behind the described change. The relevant 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.

D.

A model device is a planned representation for preprovisioning and does not prove the future hardware is reachable; matching the real device securely is required before intended settings can be pushed and verified. That explains “Create a model device for a FortiGate not yet physically connected”, not the mechanism behind the described change. The relevant 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.

Question 223

A financial branch already runs local firewall policies and its new FortiManager owner needs to import them without interrupting payment applications. After implementing this change—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.—which test most directly validates its intended outcome?

  1. Schedule a reversible lab update for a maintenance period, deliberately make one test gateway unavailable, and verify the task records success and failure separately with no silent retries outside approval.
  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. 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.
  4. Create a model FortiGate in a lab ADOM, associate a provisioning template, attach a matching simulated device identity, and confirm it transitions to live managed status without unexpected object differences.

Answer & Explanations

Correct answer: C

A.

Schedule a reversible lab update for a maintenance period, deliberately make one test gateway unavailable, and verify the task records success and failure separately with no silent retries outside approval. That would help test “Schedule scripts within controlled FortiManager maintenance windows”, not the outcome required in this scenario. The relevant acceptance check is: 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.

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

C.

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

D.

Create a model FortiGate in a lab ADOM, associate a provisioning template, attach a matching simulated device identity, and confirm it transitions to live managed status without unexpected object differences. That would help test “Create a model device for a FortiGate not yet physically connected”, not the outcome required in this scenario. The relevant acceptance check is: 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.

Question 224

A financial branch already runs local firewall policies and its new FortiManager owner needs to import them without interrupting payment applications. Which proposed shortcut most directly risks unexpected disruption to permitted traffic after uncontrolled replacement of existing firewall rules during onboarding and should therefore be rejected?

  1. Install an empty default FortiManager package over a production FortiGate immediately after registration without checking which live rules the import wizard recognized.
  2. Copy one gateway's entire network interface configuration blindly to a fleet of remote branches and assume identical static IP addresses cannot create conflicts.
  3. Schedule destructive configuration changes for midnight and declare every remote firewall updated before checking whether the devices were online or the commands completed.
  4. Record an unverified wildcard model entry and install firewall policies as though its network interfaces and serial number had already been checked against deployed hardware.

Answer & Explanations

Correct answer: A

A.

Install an empty default FortiManager package over a production FortiGate immediately after registration without checking which live rules the import wizard recognized. The foreseeable failure is unexpected disruption to permitted traffic after uncontrolled replacement of existing firewall rules during onboarding. The safer response is: 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.

B.

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: Install an empty default FortiManager package over a production FortiGate immediately after registration without checking which live rules the import wizard recognized.

C.

Schedule destructive configuration changes for midnight and declare every remote firewall updated before checking whether the devices were online or the commands completed. That shortcut risks unverified fleet-wide drift when FortiManager scheduling is mistaken for confirmed execution. Here the specific shortcut is: Install an empty default FortiManager package over a production FortiGate immediately after registration without checking which live rules the import wizard recognized.

D.

Record an unverified wildcard model entry and install firewall policies as though its network interfaces and serial number had already been checked against deployed hardware. That shortcut risks misapplied branch provisioning when placeholder device identity is mistaken for authenticated installed equipment. Here the specific shortcut is: Install an empty default FortiManager package over a production FortiGate immediately after registration without checking which live rules the import wizard recognized.

Question 225

A financial branch already runs local firewall policies and its new FortiManager owner needs to import them without interrupting payment applications. 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: 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.
  2. 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: 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: 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: Create a model FortiGate in a lab ADOM, associate a provisioning template, attach a matching simulated device identity, and confirm it transitions to live managed status without unexpected object differences.
  4. Implement: Use a supported FortiManager model device entry with an approved blueprint and correct serial or authorization data, then bind the physical FortiGate when it comes online and reconcile actual configuration. 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.

Answer & Explanations

Correct answer: B

A.

This action/test pair addresses “Apply a system template to standardize appropriate FortiGate device settings”. 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. 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. The case instead calls for: 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.

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

C.

The action is applicable: 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. But its proposed test—Create a model FortiGate in a lab ADOM, associate a provisioning template, attach a matching simulated device identity, and confirm it transitions to live managed status without unexpected object differences.—addresses “Create a model device for a FortiGate not yet physically connected”. This requirement is confirmed instead by: 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.

D.

The test would be relevant: 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. But the offered implementation—Use a supported FortiManager model device entry with an approved blueprint and correct serial or authorization data, then bind the physical FortiGate when it comes online and reconcile actual configuration.—addresses “Create a model device for a FortiGate not yet physically connected”. The action needed here is: 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.

Question 226

A university is transferring independently configured lab FortiGates into central management and must account for unusual interface mappings and custom objects. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. 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.
  2. 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.
  3. 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.
  4. Inspect the source and timestamp of an automatic FortiManager device configuration revision and compare it with separately managed ADOM revisions so the scope of a rollback is documented accurately.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: A university is transferring independently configured lab FortiGates into central management and must account for unusual interface mappings and custom objects. 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. 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. Verify the result with this 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.

B.

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. This addresses “Register and manage a FortiGate HA cluster as a consistent logical target”, where the governing principle is: 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. The stated case instead calls for: 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.

C.

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. This addresses “Organize registered FortiGates into device groups without confusing ADOM isolation”, where the governing 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. The stated case instead calls for: 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.

D.

Inspect the source and timestamp of an automatic FortiManager device configuration revision and compare it with separately managed ADOM revisions so the scope of a rollback is documented accurately. This addresses “Distinguish an automatic device configuration revision from an ADOM policy revision”, where the governing principle is: Device revisions capture relevant retrieved or managed gateway configuration state, whereas ADOM revisions represent central package and object snapshots; their audit and restoration purposes differ. The stated case instead calls for: 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.

Question 227

A university is transferring independently configured lab FortiGates into central management and must account for unusual interface mappings and custom objects. The engineer proposes the following change: 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. Which mechanism explains why it works?

  1. Device revisions capture relevant retrieved or managed gateway configuration state, whereas ADOM revisions represent central package and object snapshots; their audit and restoration purposes differ.
  2. 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.
  3. 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.
  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: D

A.

Device revisions capture relevant retrieved or managed gateway configuration state, whereas ADOM revisions represent central package and object snapshots; their audit and restoration purposes differ. That explains “Distinguish an automatic device configuration revision from an ADOM policy revision”, not the mechanism behind the described change. The relevant 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.

B.

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. That explains “Register and manage a FortiGate HA cluster as a consistent logical target”, not the mechanism behind the described change. The relevant 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.

C.

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. That explains “Organize registered FortiGates into device groups without confusing ADOM isolation”, not the mechanism behind the described change. The relevant 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.

D.

The question is set in this situation: A university is transferring independently configured lab FortiGates into central management and must account for unusual interface mappings and custom objects. 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 corresponding implementation is: 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.

Question 228

A university is transferring independently configured lab FortiGates into central management and must account for unusual interface mappings and custom objects. After implementing this change—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.—which test most directly validates its intended outcome?

  1. 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.
  2. 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. 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.
  4. Create a benign device-side change and an unrelated ADOM object change in a lab, verify which revision histories update and demonstrate independent scope for each recovery decision.

Answer & Explanations

Correct answer: C

A.

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. That would help test “Register and manage a FortiGate HA cluster as a consistent logical target”, not the outcome required in this scenario. The relevant acceptance check is: 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.

B.

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. That would help test “Organize registered FortiGates into device groups without confusing ADOM isolation”, not the outcome required in this scenario. The relevant acceptance check is: 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.

C.

The question is set in this situation: A university is transferring independently configured lab FortiGates into central management and must account for unusual interface mappings and custom objects. 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. This check is decisive because 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.

D.

Create a benign device-side change and an unrelated ADOM object change in a lab, verify which revision histories update and demonstrate independent scope for each recovery decision. That would help test “Distinguish an automatic device configuration revision from an ADOM policy revision”, not the outcome required in this scenario. The relevant acceptance check is: 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.

Question 229

A university is transferring independently configured lab FortiGates into central management and must account for unusual interface mappings and custom objects. Which proposed shortcut most directly risks unexpected disruption to permitted traffic after uncontrolled replacement of existing firewall rules during onboarding and should therefore be rejected?

  1. Treat any FortiManager revision number as a universal snapshot of all gateways, policies, objects, administrators and global settings and restore it without checking scope.
  2. Treat each HA member as an unrelated branch firewall and independently apply conflicting production policies without checking cluster state or central management identity.
  3. Install an empty default FortiManager package over a production FortiGate immediately after registration without checking which live rules the import wizard recognized.
  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: C

A.

Treat any FortiManager revision number as a universal snapshot of all gateways, policies, objects, administrators and global settings and restore it without checking scope. That shortcut risks wrong rollback selection after central and device configuration snapshots are conflated. Here the specific shortcut is: Install an empty default FortiManager package over a production FortiGate immediately after registration without checking which live rules the import wizard recognized.

B.

Treat each HA member as an unrelated branch firewall and independently apply conflicting production policies without checking cluster state or central management identity. That shortcut risks cluster synchronization conflict and traffic disruption caused by independently managing devices that belong to one HA cluster. Here the specific shortcut is: Install an empty default FortiManager package over a production FortiGate immediately after registration without checking which live rules the import wizard recognized.

C.

The question is set in this situation: A university is transferring independently configured lab FortiGates into central management and must account for unusual interface mappings and custom objects. Install an empty default FortiManager package over a production FortiGate immediately after registration without checking which live rules the import wizard recognized. The foreseeable failure is unexpected disruption to permitted traffic after uncontrolled replacement of existing firewall rules during onboarding. The safer response is: 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.

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. That shortcut risks tenant policy exposure after incorrectly treating FortiManager device groups as security boundaries. Here the specific shortcut is: Install an empty default FortiManager package over a production FortiGate immediately after registration without checking which live rules the import wizard recognized.

Question 230

A university is transferring independently configured lab FortiGates into central management and must account for unusual interface mappings and custom objects. Which combined implementation and verification plan is the best match for this workload?

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

A.

This action/test pair addresses “Organize registered FortiGates into device groups without confusing ADOM 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. 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. The case instead calls for: 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.

B.

The question is set in this situation: A university is transferring independently configured lab FortiGates into central management and must account for unusual interface mappings and custom objects. 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. Confirm it through this 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. 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.

C.

The test would be relevant: 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. But the offered implementation—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.—addresses “Register and manage a FortiGate HA cluster as a consistent logical target”. The action needed here is: 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.

D.

The action is applicable: 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. But its proposed 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.—addresses “Register and manage a FortiGate HA cluster as a consistent logical target”. This requirement is confirmed instead by: 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.

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