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 20

Question 190

A hospital network is rolling out consistent settings but each clinic gateway has a different WAN configuration and must avoid duplicate addresses. 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: 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: 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.
  3. 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: From a staged FortiGate inspect its configured FortiManager address and FGFM connectivity, view the incoming authorization request on FortiManager, and confirm registration only after approval.
  4. Implement: When a FortiGate initiates management to FortiManager, verify the configured central-management target, interface administrative access, routing and permitted FGFM session before changing unrelated firewall security policy. 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: A

A.

The question is set in this situation: A hospital network is rolling out consistent settings but each clinic gateway has a different WAN configuration and must avoid duplicate addresses. 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. Confirm it through this 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. 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.

B.

This action/test pair addresses “Create a model device for a FortiGate not yet physically connected”. 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. 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. The case instead calls for: 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.

C.

The action is applicable: 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. But its proposed test—From a staged FortiGate inspect its configured FortiManager address and FGFM connectivity, view the incoming authorization request on FortiManager, and confirm registration only after approval.—addresses “Troubleshoot FortiGate initiated registration using correct FGFM reachability”. This requirement is confirmed instead by: 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.

D.

The test would be relevant: 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. But the offered implementation—When a FortiGate initiates management to FortiManager, verify the configured central-management target, interface administrative access, routing and permitted FGFM session before changing unrelated firewall security policy.—addresses “Troubleshoot FortiGate initiated registration using correct FGFM reachability”. The action needed here is: 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.

Question 191

An MSP wants to replicate a hardened baseline for a new customer without copying that customer's unrelated object database or secrets. 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. When FortiManager reports a device configuration status of modified or out of sync, compare the central device database, last retrieved revision and actual FortiGate state before deciding whether to retrieve or reinstall.
  3. 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.
  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: C

A.

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

B.

When FortiManager reports a device configuration status of modified or out of sync, compare the central device database, last retrieved revision and actual FortiGate state before deciding whether to retrieve or reinstall. This addresses “Reconcile device database synchronization status with live FortiGate changes”, where the governing principle is: The FortiManager device database is not identical to every current FortiGate setting until retrieval or installation succeeds; a status indicator alone does not identify which side is authoritative. The stated case instead calls for: 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.

C.

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

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

Question 192

An MSP wants to replicate a hardened baseline for a new customer without copying that customer's unrelated object database or secrets. The engineer proposes the following change: 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. 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. 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.
  3. The FortiManager device database is not identical to every current FortiGate setting until retrieval or installation succeeds; a status indicator alone does not identify which side is authoritative.
  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 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: 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.

B.

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

C.

The FortiManager device database is not identical to every current FortiGate setting until retrieval or installation succeeds; a status indicator alone does not identify which side is authoritative. That explains “Reconcile device database synchronization status with live FortiGate changes”, not the mechanism behind the described change. The relevant 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.

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

Question 193

An MSP wants to replicate a hardened baseline for a new customer without copying that customer's unrelated object database or secrets. After implementing this change—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.—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. Introduce a controlled local configuration change on a test FortiGate, review device status and revision differences, then retrieve or restore as approved and confirm synchronized status.
  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. 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: A

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

B.

Introduce a controlled local configuration change on a test FortiGate, review device status and revision differences, then retrieve or restore as approved and confirm synchronized status. That would help test “Reconcile device database synchronization status with live FortiGate changes”, not the outcome required in this scenario. The relevant acceptance check is: 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.

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

D.

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

Question 194

An MSP wants to replicate a hardened baseline for a new customer without copying that customer's unrelated object database or secrets. Which proposed shortcut most directly risks cross-tenant configuration errors after reusing an incompatible shared provisioning template 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 transferring a template across ADOMs automatically migrates all customer credentials, interface names and version-specific commands without review.
  3. Install an empty default FortiManager package over a production FortiGate immediately after registration without checking which live rules the import wizard recognized.
  4. Click the synchronize button repeatedly without comparing intended central values against the changed firewall and assume every live device alteration was safe to adopt.

Answer & Explanations

Correct answer: B

A.

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: Assume transferring a template across ADOMs automatically migrates all customer credentials, interface names and version-specific commands without review.

B.

Assume transferring a template across ADOMs automatically migrates all customer credentials, interface names and version-specific commands without review. The foreseeable failure is cross-tenant configuration errors after reusing an incompatible shared provisioning template. The safer response is: 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.

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: Assume transferring a template across ADOMs automatically migrates all customer credentials, interface names and version-specific commands without review.

D.

Click the synchronize button repeatedly without comparing intended central values against the changed firewall and assume every live device alteration was safe to adopt. That shortcut risks persistent unauthorized configuration drift when FortiManager sync status is fixed without understanding which values changed. Here the specific shortcut is: Assume transferring a template across ADOMs automatically migrates all customer credentials, interface names and version-specific commands without review.

Question 195

An MSP wants to replicate a hardened baseline for a new customer without copying that customer's unrelated object database or secrets. 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: 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. 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: 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.
  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: 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. 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.

Answer & Explanations

Correct answer: D

A.

This action/test pair addresses “Reconcile an imported configuration report before first FortiManager policy installation”. 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 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. The case instead calls for: 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.

B.

The test would be relevant: 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. But the offered implementation—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.—addresses “Organize registered FortiGates into device groups without confusing ADOM isolation”. The action needed here is: 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.

C.

The action is applicable: 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. But its proposed 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.—addresses “Organize registered FortiGates into device groups without confusing ADOM isolation”. This requirement is confirmed instead by: 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.

D.

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

Question 196

A multinational enterprise is transferring approved gateway defaults from a pilot ADOM to a production region running a different supported device inventory. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. Retrieve or inspect the relevant FortiGate configuration after an authorized script runs, compare the actual setting to the planned state and document any central database reconciliation required.
  2. 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.
  3. 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.
  4. When a FortiGate initiates management to FortiManager, verify the configured central-management target, interface administrative access, routing and permitted FGFM session before changing unrelated firewall security policy.

Answer & Explanations

Correct answer: C

A.

Retrieve or inspect the relevant FortiGate configuration after an authorized script runs, compare the actual setting to the planned state and document any central database reconciliation required. This addresses “Validate configuration after a FortiManager script instead of relying on task completion”, where the governing principle is: The script engine's task result and the gateway's active configuration are separate sources of evidence; manual device-level changes can create differences that require FortiManager database updates or an import. The stated case instead calls for: 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.

B.

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. This addresses “Register a reachable FortiGate through the FortiManager Add Device wizard”, where the governing principle is: A named FortiGate entry is not equivalent to an authenticated live management relationship; FortiManager must establish supported communications and reconcile the device configuration with the central database. The stated case instead calls for: 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.

C.

The question is set in this situation: A multinational enterprise is transferring approved gateway defaults from a pilot ADOM to a production region running a different supported device inventory. 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. 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. Verify the result with this test: 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.

D.

When a FortiGate initiates management to FortiManager, verify the configured central-management target, interface administrative access, routing and permitted FGFM session before changing unrelated firewall security policy. This addresses “Troubleshoot FortiGate initiated registration using correct FGFM reachability”, where the governing principle is: FortiGate and FortiManager require a supported FGFM control-plane connection; ordinary internet connectivity or reachability to the HTTPS login page does not establish device registration and configuration synchronization. The stated case instead calls for: 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.

Question 197

A multinational enterprise is transferring approved gateway defaults from a pilot ADOM to a production region running a different supported device inventory. The engineer proposes the following change: 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. Which mechanism explains why it works?

  1. FortiGate and FortiManager require a supported FGFM control-plane connection; ordinary internet connectivity or reachability to the HTTPS login page does not establish device registration and configuration synchronization.
  2. The script engine's task result and the gateway's active configuration are separate sources of evidence; manual device-level changes can create differences that require FortiManager database updates or an import.
  3. A named FortiGate entry is not equivalent to an authenticated live management relationship; FortiManager must establish supported communications and reconcile the device configuration with the central database.
  4. 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.

Answer & Explanations

Correct answer: D

A.

FortiGate and FortiManager require a supported FGFM control-plane connection; ordinary internet connectivity or reachability to the HTTPS login page does not establish device registration and configuration synchronization. That explains “Troubleshoot FortiGate initiated registration using correct FGFM reachability”, not the mechanism behind the described change. The relevant 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.

B.

The script engine's task result and the gateway's active configuration are separate sources of evidence; manual device-level changes can create differences that require FortiManager database updates or an import. That explains “Validate configuration after a FortiManager script instead of relying on task completion”, not the mechanism behind the described change. The relevant 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.

C.

A named FortiGate entry is not equivalent to an authenticated live management relationship; FortiManager must establish supported communications and reconcile the device configuration with the central database. That explains “Register a reachable FortiGate through the FortiManager Add Device wizard”, not the mechanism behind the described change. The relevant 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.

D.

The question is set in this situation: A multinational enterprise is transferring approved gateway defaults from a pilot ADOM to a production region running a different supported device inventory. 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 corresponding implementation is: 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.

Question 198

A multinational enterprise is transferring approved gateway defaults from a pilot ADOM to a production region running a different supported device inventory. After implementing this change—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.—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. From a staged FortiGate inspect its configured FortiManager address and FGFM connectivity, view the incoming authorization request on FortiManager, and confirm registration only after approval.
  3. Run a harmless staged script, retrieve the affected setting, compare it with a stored before-state and confirm later central policy installation does not unintentionally undo the change.
  4. 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.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: A multinational enterprise is transferring approved gateway defaults from a pilot ADOM to a production region running a different supported device inventory. 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. This check is decisive because 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.

B.

From a staged FortiGate inspect its configured FortiManager address and FGFM connectivity, view the incoming authorization request on FortiManager, and confirm registration only after approval. That would help test “Troubleshoot FortiGate initiated registration using correct FGFM reachability”, not the outcome required in this scenario. The relevant acceptance check is: 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.

C.

Run a harmless staged script, retrieve the affected setting, compare it with a stored before-state and confirm later central policy installation does not unintentionally undo the change. That would help test “Validate configuration after a FortiManager script instead of relying on task completion”, not the outcome required in this scenario. The relevant acceptance check is: 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.

D.

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. That would help test “Register a reachable FortiGate through the FortiManager Add Device wizard”, not the outcome required in this scenario. The relevant acceptance check is: 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.

Question 199

A multinational enterprise is transferring approved gateway defaults from a pilot ADOM to a production region running a different supported device inventory. Which proposed shortcut most directly risks cross-tenant configuration errors after reusing an incompatible shared provisioning template and should therefore be rejected?

  1. Mark a script audit successful based solely on the job submission timestamp without examining whether the actual running FortiGate configuration changed.
  2. Create an arbitrary offline device row with a plausible hostname and mark registration successful without reaching the FortiGate or checking management authorization.
  3. Assume transferring a template across ADOMs automatically migrates all customer credentials, interface names and version-specific commands without review.
  4. Open unrelated browser ports across the network and assume any FortiGate that can ping the FortiManager management IP has already enrolled in central management.

Answer & Explanations

Correct answer: C

A.

Mark a script audit successful based solely on the job submission timestamp without examining whether the actual running FortiGate configuration changed. That shortcut risks false compliance evidence and later configuration rollback after script results are not reconciled with central management. Here the specific shortcut is: Assume transferring a template across ADOMs automatically migrates all customer credentials, interface names and version-specific commands without review.

B.

Create an arbitrary offline device row with a plausible hostname and mark registration successful without reaching the FortiGate or checking management authorization. That shortcut risks unmanaged firewall falsely counted as centrally protected after its FortiManager record was never authenticated. Here the specific shortcut is: Assume transferring a template across ADOMs automatically migrates all customer credentials, interface names and version-specific commands without review.

C.

The question is set in this situation: A multinational enterprise is transferring approved gateway defaults from a pilot ADOM to a production region running a different supported device inventory. Assume transferring a template across ADOMs automatically migrates all customer credentials, interface names and version-specific commands without review. The foreseeable failure is cross-tenant configuration errors after reusing an incompatible shared provisioning template. The safer response is: 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.

D.

Open unrelated browser ports across the network and assume any FortiGate that can ping the FortiManager management IP has already enrolled in central management. That shortcut risks failed device enrollment despite apparent IP reachability because the FGFM channel or authorization was not established. Here the specific shortcut is: Assume transferring a template across ADOMs automatically migrates all customer credentials, interface names and version-specific commands without review.

Question 200

A multinational enterprise is transferring approved gateway defaults from a pilot ADOM to a production region running a different supported device inventory. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: When a FortiGate initiates management to FortiManager, verify the configured central-management target, interface administrative access, routing and permitted FGFM session before changing unrelated firewall security policy. Verify: From a staged FortiGate inspect its configured FortiManager address and FGFM connectivity, view the incoming authorization request on FortiManager, and confirm registration only after approval.
  2. 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.
  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: 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.
  4. 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: 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.

Answer & Explanations

Correct answer: B

A.

This action/test pair addresses “Troubleshoot FortiGate initiated registration using correct FGFM reachability”. When a FortiGate initiates management to FortiManager, verify the configured central-management target, interface administrative access, routing and permitted FGFM session before changing unrelated firewall security policy. From a staged FortiGate inspect its configured FortiManager address and FGFM connectivity, view the incoming authorization request on FortiManager, and confirm registration only after approval. The case instead calls for: 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.

B.

The question is set in this situation: A multinational enterprise is transferring approved gateway defaults from a pilot ADOM to a production region running a different supported device inventory. 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. Confirm it through this test: 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. 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.

C.

The action is applicable: 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. But its proposed test—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.—addresses “Register a reachable FortiGate through the FortiManager Add Device wizard”. This requirement is confirmed instead by: 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.

D.

The test would be relevant: 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. But the offered implementation—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.—addresses “Register a reachable FortiGate through the FortiManager Add Device wizard”. The action needed here is: 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.

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