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 17

Question 160

A university is adding a laboratory firewall and wants the operator to distinguish a pending device inventory entry from a registered managed device. Which combined implementation and verification plan is the best match for this workload?

  1. 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.
  2. 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: Register a staging firewall with FortiManager access allowed, inspect the device's serial number and managed status, retrieve its initial configuration and confirm the intended ADOM owns it.
  3. Implement: 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.
  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: 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: A

A.

The question is set in this situation: A university is adding a laboratory firewall and wants the operator to distinguish a pending device inventory entry from a registered managed device. 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. Confirm it through this 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. 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.

B.

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

C.

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

D.

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

Question 161

A financial institution added an edge ACL before a FortiGate rollout and the branch device no longer appears among pending FortiManager registration requests. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. 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.
  2. Compare a managed device's current stored revision with the last approved revision, locate the precise changed settings, and apply a supported restoration or central redeployment after appropriate review.
  3. 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.
  4. 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.

Answer & Explanations

Correct answer: A

A.

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

B.

Compare a managed device's current stored revision with the last approved revision, locate the precise changed settings, and apply a supported restoration or central redeployment after appropriate review. This addresses “Use FortiManager device revision history to identify and repair drift”, where the governing principle is: Device revision history helps reconstruct configuration changes and revert known states, while snapshots are not the same as an ADOM-wide policy/object database revision. The stated case instead calls for: 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.

C.

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

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

A financial institution added an edge ACL before a FortiGate rollout and the branch device no longer appears among pending FortiManager registration requests. The engineer proposes the following change: 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. Which mechanism explains why it works?

  1. 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.
  2. 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.
  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. Device revision history helps reconstruct configuration changes and revert known states, while snapshots are not the same as an ADOM-wide policy/object database revision.

Answer & Explanations

Correct answer: B

A.

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

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

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. That explains “Create a model device for a FortiGate not yet physically connected”, not the mechanism behind the described change. The relevant 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.

D.

Device revision history helps reconstruct configuration changes and revert known states, while snapshots are not the same as an ADOM-wide policy/object database revision. That explains “Use FortiManager device revision history to identify and repair drift”, not the mechanism behind the described change. The relevant principle is: 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.

Question 163

A financial institution added an edge ACL before a FortiGate rollout and the branch device no longer appears among pending FortiManager registration requests. After implementing this change—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.—which test most directly validates its intended outcome?

  1. Modify a safe lab interface description, retrieve the new revision, compare with the baseline and restore an approved version without deleting unrelated ADOM policy objects.
  2. Register a staging firewall with FortiManager access allowed, inspect the device's serial number and managed status, retrieve its initial configuration and confirm the intended ADOM owns it.
  3. 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. 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: D

A.

Modify a safe lab interface description, retrieve the new revision, compare with the baseline and restore an approved version without deleting unrelated ADOM policy objects. That would help test “Use FortiManager device revision history to identify and repair drift”, not the outcome required in this scenario. The relevant acceptance check is: 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.

B.

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

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

D.

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

Question 164

A financial institution added an edge ACL before a FortiGate rollout and the branch device no longer appears among pending FortiManager registration requests. Which proposed shortcut most directly risks failed device enrollment despite apparent IP reachability because the FGFM channel or authorization was not established and should therefore be rejected?

  1. 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.
  2. Create an arbitrary offline device row with a plausible hostname and mark registration successful without reaching the FortiGate or checking management authorization.
  3. Open unrelated browser ports across the network and assume any FortiGate that can ping the FortiManager management IP has already enrolled in central management.
  4. Revert an arbitrary old revision without comparing what changed and assume every ADOM policy package and management administrator account must also roll back.

Answer & Explanations

Correct answer: C

A.

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: Open unrelated browser ports across the network and assume any FortiGate that can ping the FortiManager management IP has already enrolled in central management.

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: Open unrelated browser ports across the network and assume any FortiGate that can ping the FortiManager management IP has already enrolled in central management.

C.

Open unrelated browser ports across the network and assume any FortiGate that can ping the FortiManager management IP has already enrolled in central management. The foreseeable failure is failed device enrollment despite apparent IP reachability because the FGFM channel or authorization was not established. The safer response 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.

D.

Revert an arbitrary old revision without comparing what changed and assume every ADOM policy package and management administrator account must also roll back. That shortcut risks accidental loss of legitimate device changes after treating a device revision as a complete FortiManager restore point. Here the specific shortcut is: Open unrelated browser ports across the network and assume any FortiGate that can ping the FortiManager management IP has already enrolled in central management.

Question 165

A financial institution added an edge ACL before a FortiGate rollout and the branch device no longer appears among pending FortiManager registration requests. 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: 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.
  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: 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. 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: 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: 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: B

A.

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

B.

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.

C.

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

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—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: 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 166

A managed security provider is diagnosing a remote firewall that has ordinary web connectivity but never completes the FortiManager management handshake. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. 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.
  2. Copy a reviewed system template into another supported ADOM while validating version compatibility, referenced interfaces and device-specific variables before assigning it to the destination tenant.
  3. Match a FortiManager script's execution environment, command hierarchy and supported FortiOS version to the intended managed devices, and test commands in a compatible staging firewall before scheduling production execution.
  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: D

A.

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

B.

Copy a reviewed system template into another supported ADOM while validating version compatibility, referenced interfaces and device-specific variables before assigning it to the destination tenant. This addresses “Move a FortiManager provisioning template between compatible ADOMs safely”, where the governing principle is: An ADOM copy can preserve template logic while omitting assumptions about destination devices or permissions; identical text can have different effects across firmware versions or interface inventories. The stated case instead calls for: 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.

C.

Match a FortiManager script's execution environment, command hierarchy and supported FortiOS version to the intended managed devices, and test commands in a compatible staging firewall before scheduling production execution. This addresses “Choose script context and supported FortiOS syntax before bulk execution”, where the governing principle is: Commands accepted on one FortiOS release or config subtree may fail in another context; FortiManager task submission success does not prove every child command was executed correctly. The stated case instead calls for: 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 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. 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. Verify the result with 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.

Question 167

A managed security provider is diagnosing a remote firewall that has ordinary web connectivity but never completes the FortiManager management handshake. The engineer proposes the following change: 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. 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. Commands accepted on one FortiOS release or config subtree may fail in another context; FortiManager task submission success does not prove every child command was executed correctly.
  3. 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.
  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 managed security provider is diagnosing a remote firewall that has ordinary web connectivity but never completes the FortiManager management handshake. 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 corresponding implementation 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.

B.

Commands accepted on one FortiOS release or config subtree may fail in another context; FortiManager task submission success does not prove every child command was executed correctly. That explains “Choose script context and supported FortiOS syntax before bulk execution”, not the mechanism behind the described change. The relevant principle is: 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.

C.

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

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

Question 168

A managed security provider is diagnosing a remote firewall that has ordinary web connectivity but never completes the FortiManager management handshake. After implementing this change—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.—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. Run a version-appropriate test script on two firmware variants in a lab, inspect per-device output and changed configuration, and revise the script where a command is unsupported.
  3. 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. 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: 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: 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.

B.

Run a version-appropriate test script on two firmware variants in a lab, inspect per-device output and changed configuration, and revise the script where a command is unsupported. That would help test “Choose script context and supported FortiOS syntax before bulk execution”, not the outcome required in this scenario. The relevant acceptance check is: 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.

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

D.

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

Question 169

A managed security provider is diagnosing a remote firewall that has ordinary web connectivity but never completes the FortiManager management handshake. Which proposed shortcut most directly risks failed device enrollment despite apparent IP reachability because the FGFM channel or authorization was not established and should therefore be rejected?

  1. Assume transferring a template across ADOMs automatically migrates all customer credentials, interface names and version-specific commands without review.
  2. Open unrelated browser ports across the network and assume any FortiGate that can ping the FortiManager management IP has already enrolled in central management.
  3. Copy CLI lines from a different Fortinet product and execute them unmodified across mixed FortiOS releases while interpreting a submitted task as complete success.
  4. Treat each HA member as an unrelated branch firewall and independently apply conflicting production policies without checking cluster state or central management identity.

Answer & Explanations

Correct answer: B

A.

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: Open unrelated browser ports across the network and assume any FortiGate that can ping the FortiManager management IP has already enrolled in central management.

B.

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. Open unrelated browser ports across the network and assume any FortiGate that can ping the FortiManager management IP has already enrolled in central management. The foreseeable failure is failed device enrollment despite apparent IP reachability because the FGFM channel or authorization was not established. The safer response 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.

C.

Copy CLI lines from a different Fortinet product and execute them unmodified across mixed FortiOS releases while interpreting a submitted task as complete success. That shortcut risks partial configuration deployment after script command syntax or context is incompatible with target gateways. Here the specific shortcut is: Open unrelated browser ports across the network and assume any FortiGate that can ping the FortiManager management IP has already enrolled in central management.

D.

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: Open unrelated browser ports across the network and assume any FortiGate that can ping the FortiManager management IP has already enrolled in central management.

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.

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