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 18

Question 170

A managed security provider is diagnosing a remote firewall that has ordinary web connectivity but never completes the FortiManager management handshake. 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: 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: 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: 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: 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: 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.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: A managed security provider is diagnosing a remote firewall that has ordinary web connectivity but never completes the FortiManager management handshake. 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. Confirm it through this 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. 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.

B.

The action is applicable: 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. But its proposed 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.—addresses “Move a FortiManager provisioning template between compatible ADOMs safely”. This requirement is confirmed instead by: 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.

C.

This action/test pair addresses “Register and manage a FortiGate HA cluster as a consistent logical target”. 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. 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. The case instead calls for: 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.

D.

The test would be relevant: 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. But the offered implementation—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.—addresses “Move a FortiManager provisioning template between compatible ADOMs safely”. The action needed here is: 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.

Question 171

A retail chain prepares fifty store firewalls before shipment and needs consistent policies ready for binding when each actual unit connects. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

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

Answer & Explanations

Correct answer: D

A.

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

B.

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

C.

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

D.

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

Question 172

A retail chain prepares fifty store firewalls before shipment and needs consistent policies ready for binding when each actual unit connects. The engineer proposes the following change: 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. 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. 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.
  3. 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.
  4. 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.

Answer & Explanations

Correct answer: C

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

B.

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

C.

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

D.

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

Question 173

A retail chain prepares fifty store firewalls before shipment and needs consistent policies ready for binding when each actual unit connects. After implementing this change—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.—which test most directly validates its intended outcome?

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

A.

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

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

C.

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

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

Question 174

A retail chain prepares fifty store firewalls before shipment and needs consistent policies ready for binding when each actual unit connects. Which proposed shortcut most directly risks misapplied branch provisioning when placeholder device identity is mistaken for authenticated installed equipment and should therefore be rejected?

  1. Assume creating dozens of ADOMs multiplies a FortiManager appliance's licensed device count indefinitely without purchasing capacity or verifying platform limits.
  2. Treat any FortiManager revision number as a universal snapshot of all gateways, policies, objects, administrators and global settings and restore it without checking scope.
  3. Create an arbitrary offline device row with a plausible hostname and mark registration successful without reaching the FortiGate or checking management authorization.
  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: D

A.

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

B.

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

C.

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

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. The foreseeable failure is misapplied branch provisioning when placeholder device identity is mistaken for authenticated installed equipment. The safer response is: 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.

Question 175

A retail chain prepares fifty store firewalls before shipment and needs consistent policies ready for binding when each actual unit connects. Which combined implementation and verification plan is the best match for this workload?

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

Answer & Explanations

Correct answer: B

A.

The action is applicable: 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. 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: 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.

B.

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

C.

The test would be relevant: 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. 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: 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.

D.

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

Question 176

A national insurer orders branch equipment and wants to stage FortiManager configuration safely without claiming disconnected model devices are live. 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. 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. 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.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: A national insurer orders branch equipment and wants to stage FortiManager configuration safely without claiming disconnected model devices are live. 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. 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. Verify the result with this 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.

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

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

D.

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

Question 177

A national insurer orders branch equipment and wants to stage FortiManager configuration safely without claiming disconnected model devices are live. The engineer proposes the following change: 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. Which mechanism explains why it works?

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

A.

The question is set in this situation: A national insurer orders branch equipment and wants to stage FortiManager configuration safely without claiming disconnected model devices are live. 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 corresponding implementation is: 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.

B.

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

C.

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

D.

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

Question 178

A national insurer orders branch equipment and wants to stage FortiManager configuration safely without claiming disconnected model devices are live. After implementing this change—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.—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. 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.
  3. 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. 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: 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: 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.

B.

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

C.

The question is set in this situation: A national insurer orders branch equipment and wants to stage FortiManager configuration safely without claiming disconnected model devices are live. 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. This check is decisive because 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.

D.

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

Question 179

A national insurer orders branch equipment and wants to stage FortiManager configuration safely without claiming disconnected model devices are live. Which proposed shortcut most directly risks misapplied branch provisioning when placeholder device identity is mistaken for authenticated installed equipment and should therefore be rejected?

  1. Schedule destructive configuration changes for midnight and declare every remote firewall updated before checking whether the devices were online or the commands completed.
  2. Assume transferring a template across ADOMs automatically migrates all customer credentials, interface names and version-specific commands without review.
  3. Copy one gateway's entire network interface configuration blindly to a fleet of remote branches and assume identical static IP addresses cannot create conflicts.
  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: D

A.

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

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

C.

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

D.

The question is set in this situation: A national insurer orders branch equipment and wants to stage FortiManager configuration safely without claiming disconnected model devices are live. 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. The foreseeable failure is misapplied branch provisioning when placeholder device identity is mistaken for authenticated installed equipment. The safer response is: 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.

Question 180

A national insurer orders branch equipment and wants to stage FortiManager configuration safely without claiming disconnected model devices are live. Which combined implementation and verification plan is the best match for this workload?

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

A.

The action is applicable: 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. 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: 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.

B.

The question is set in this situation: A national insurer orders branch equipment and wants to stage FortiManager configuration safely without claiming disconnected model devices are live. 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. Confirm it through this 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. 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.

C.

The test would be relevant: 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. 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: 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.

D.

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

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