Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 21
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?
Answer & Explanations
Correct answer: B
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.
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.
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.
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.
Question 201
A hospital uses a two-member FortiGate HA cluster at its internet boundary and wants to keep FortiManager's managed device inventory accurate. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: 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: 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.
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. 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. Verify the result with this test: Add a staged two-member FortiGate cluster, inspect primary and secondary member information, install one harmless policy change through the proper managed target, and check both members remain healthy.
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: 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.
Author a reviewed FortiManager CLI script using syntax compatible with the target FortiOS version, choose explicit devices or a restricted device group, and validate the intended scope before executing. This addresses “Execute a FortiManager CLI script only on approved FortiGate targets”, where the governing principle is: Central scripts can change many managed firewalls efficiently, so a correct command still creates risk if it runs against the wrong ADOM, firmware version or device selection. The stated case instead calls for: Discover a FortiGate HA cluster using supported FortiManager procedures, verify cluster identity and member status, and use an appropriate cluster target when managing shared policy and device configuration.
Question 202
A hospital uses a two-member FortiGate HA cluster at its internet boundary and wants to keep FortiManager's managed device inventory accurate. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: A
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 corresponding implementation is: Discover a FortiGate HA cluster using supported FortiManager procedures, verify cluster identity and member status, and use an appropriate cluster target when managing shared policy and device configuration.
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: 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.
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: 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.
Central scripts can change many managed firewalls efficiently, so a correct command still creates risk if it runs against the wrong ADOM, firmware version or device selection. That explains “Execute a FortiManager CLI script only on approved FortiGate targets”, not the mechanism behind the described change. The relevant 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.
Question 203
A hospital uses a two-member FortiGate HA cluster at its internet boundary and wants to keep FortiManager's managed device inventory accurate. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: C
Run a harmless diagnostic or reversible configuration script on two lab FortiGates, inspect the target list and per-device status, and confirm an unselected gateway has no resulting change. That would help test “Execute a FortiManager CLI script only on approved FortiGate targets”, not the outcome required in this scenario. The relevant acceptance check is: 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.
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: 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.
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. This check is decisive because 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.
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: 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.
Question 204
A hospital uses a two-member FortiGate HA cluster at its internet boundary and wants to keep FortiManager's managed device inventory accurate. Which proposed shortcut most directly risks cluster synchronization conflict and traffic disruption caused by independently managing devices that belong to one HA cluster and should therefore be rejected?
Answer & Explanations
Correct answer: D
Place two tenants in a single unrestricted ADOM and claim that creating separate device groups guarantees legal customer data isolation and separate object administration. That shortcut risks tenant policy exposure after incorrectly treating FortiManager device groups as security boundaries. Here the specific shortcut is: Treat each HA member as an unrelated branch firewall and independently apply conflicting production policies without checking cluster state or central management identity.
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: Treat each HA member as an unrelated branch firewall and independently apply conflicting production policies without checking cluster state or central management identity.
Schedule an unreviewed administrator-level CLI script against every FortiManager device across all customers because it worked once on a single test box. That shortcut risks mass configuration drift after a valid command is executed against unapproved devices. Here the specific shortcut is: Treat each HA member as an unrelated branch firewall and independently apply conflicting production policies without checking cluster state or central management identity.
Treat each HA member as an unrelated branch firewall and independently apply conflicting production policies without checking cluster state or central management identity. The foreseeable failure is cluster synchronization conflict and traffic disruption caused by independently managing devices that belong to one HA cluster. The safer response is: Discover a FortiGate HA cluster using supported FortiManager procedures, verify cluster identity and member status, and use an appropriate cluster target when managing shared policy and device configuration.
Question 205
A hospital uses a two-member FortiGate HA cluster at its internet boundary and wants to keep FortiManager's managed device inventory accurate. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: D
The test would be relevant: Add a staged two-member FortiGate cluster, inspect primary and secondary member information, install one harmless policy change through the proper managed target, and check both members remain healthy. But the offered implementation—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: 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 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: 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.
The action is applicable: Discover a FortiGate HA cluster using supported FortiManager procedures, verify cluster identity and member status, and use an appropriate cluster target when managing shared policy and device configuration. But its proposed test—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: 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.
Discover a FortiGate HA cluster using supported FortiManager procedures, verify cluster identity and member status, and use an appropriate cluster target when managing shared policy and device configuration. Confirm it through this test: Add a staged two-member FortiGate cluster, inspect primary and secondary member information, install one harmless policy change through the proper managed target, and check both members remain healthy. Multiple FortiGate HA member serial numbers do not necessarily represent independent production policy targets; a cluster has shared identity, synchronization state and supported installation behavior that must be understood.
Question 206
A bank's new data center has an HA firewall pair and its central team needs policy installation to honor cluster relationships rather than stand-alone device assumptions. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: 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: 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.
The question is set in this situation: A bank's new data center has an HA firewall pair and its central team needs policy installation to honor cluster relationships rather than stand-alone device assumptions. Discover a FortiGate HA cluster using supported FortiManager procedures, verify cluster identity and member status, and use an appropriate cluster target when managing shared policy and device configuration. 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. Verify the result with this test: Add a staged two-member FortiGate cluster, inspect primary and secondary member information, install one harmless policy change through the proper managed target, and check both members remain healthy.
Use the supported Retrieve Config operation for an approved device and compare the retrieved snapshot with the existing device database and known revision history before deciding whether to adopt differences. This addresses “Retrieve the running FortiGate configuration to populate a new FortiManager revision”, where the governing principle is: Configuration retrieval observes actual device-side state and can create a new FortiManager revision; it does not automatically prove every locally changed setting was authorized or should become central policy. The stated case instead calls for: Discover a FortiGate HA cluster using supported FortiManager procedures, verify cluster identity and member status, and use an appropriate cluster target when managing shared policy and device configuration.
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: Discover a FortiGate HA cluster using supported FortiManager procedures, verify cluster identity and member status, and use an appropriate cluster target when managing shared policy and device configuration.
Question 207
A bank's new data center has an HA firewall pair and its central team needs policy installation to honor cluster relationships rather than stand-alone device assumptions. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: 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: 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.
Configuration retrieval observes actual device-side state and can create a new FortiManager revision; it does not automatically prove every locally changed setting was authorized or should become central policy. That explains “Retrieve the running FortiGate configuration to populate a new FortiManager revision”, not the mechanism behind the described change. The relevant 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 question is set in this situation: A bank's new data center has an HA firewall pair and its central team needs policy installation to honor cluster relationships rather than stand-alone device assumptions. 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 corresponding implementation is: Discover a FortiGate HA cluster using supported FortiManager procedures, verify cluster identity and member status, and use an appropriate cluster target when managing shared policy and device configuration.
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: 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.
Question 208
A bank's new data center has an HA firewall pair and its central team needs policy installation to honor cluster relationships rather than stand-alone device assumptions. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: A
The question is set in this situation: A bank's new data center has an HA firewall pair and its central team needs policy installation to honor cluster relationships rather than stand-alone device assumptions. 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. This check is decisive because 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.
Change a harmless test setting directly on a staging FortiGate, retrieve configuration in FortiManager, inspect the revised record and document whether to accept or revert the local change. That would help test “Retrieve the running FortiGate configuration to populate a new FortiManager revision”, not the outcome required in this scenario. The relevant acceptance check is: 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.
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: 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.
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: 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.
Question 209
A bank's new data center has an HA firewall pair and its central team needs policy installation to honor cluster relationships rather than stand-alone device assumptions. Which proposed shortcut most directly risks cluster synchronization conflict and traffic disruption caused by independently managing devices that belong to one HA cluster and should therefore be rejected?
Answer & Explanations
Correct answer: B
Press Retrieve Config after an unreviewed local change and declare all modifications approved corporate policy merely because the management database now contains them. That shortcut risks unauthorized local changes legitimized when retrieved device configuration is mistaken for reviewed intent. Here the specific shortcut is: Treat each HA member as an unrelated branch firewall and independently apply conflicting production policies without checking cluster state or central management identity.
The question is set in this situation: A bank's new data center has an HA firewall pair and its central team needs policy installation to honor cluster relationships rather than stand-alone device assumptions. Treat each HA member as an unrelated branch firewall and independently apply conflicting production policies without checking cluster state or central management identity. The foreseeable failure is cluster synchronization conflict and traffic disruption caused by independently managing devices that belong to one HA cluster. The safer response is: Discover a FortiGate HA cluster using supported FortiManager procedures, verify cluster identity and member status, and use an appropriate cluster target when managing shared policy and device configuration.
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: Treat each HA member as an unrelated branch firewall and independently apply conflicting production policies without checking cluster state or central management identity.
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: Treat each HA member as an unrelated branch firewall and independently apply conflicting production policies without checking cluster state or central management identity.
Question 210
A bank's new data center has an HA firewall pair and its central team needs policy installation to honor cluster relationships rather than stand-alone device assumptions. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: C
The action is applicable: Discover a FortiGate HA cluster using supported FortiManager procedures, verify cluster identity and member status, and use an appropriate cluster target when managing shared policy and device configuration. But its proposed test—Review current managed-device count and licensing on an authorized FortiManager instance, add a lab device within the approved capacity, and document a scale decision before exceeding it.—addresses “Account for FortiManager managed device capacity and entitlement before expansion”. This requirement is confirmed instead by: Add a staged two-member FortiGate cluster, inspect primary and secondary member information, install one harmless policy change through the proper managed target, and check both members remain healthy.
This action/test pair addresses “Register a reachable FortiGate through the FortiManager Add Device wizard”. Use the supported Add Device workflow with the intended ADOM, correct management IP and authenticated FortiGate authorization, confirm FGFM communication and review the initial import report before declaring it managed. Register a staging firewall with FortiManager access allowed, inspect the device's serial number and managed status, retrieve its initial configuration and confirm the intended ADOM owns it. The case instead calls for: Discover a FortiGate HA cluster using supported FortiManager procedures, verify cluster identity and member status, and use an appropriate cluster target when managing shared policy and device configuration.
The question is set in this situation: A bank's new data center has an HA firewall pair and its central team needs policy installation to honor cluster relationships rather than stand-alone device assumptions. Discover a FortiGate HA cluster using supported FortiManager procedures, verify cluster identity and member status, and use an appropriate cluster target when managing shared policy and device configuration. Confirm it through this test: Add a staged two-member FortiGate cluster, inspect primary and secondary member information, install one harmless policy change through the proper managed target, and check both members remain healthy. Multiple FortiGate HA member serial numbers do not necessarily represent independent production policy targets; a cluster has shared identity, synchronization state and supported installation behavior that must be understood.
The test would be relevant: Add a staged two-member FortiGate cluster, inspect primary and secondary member information, install one harmless policy change through the proper managed target, and check both members remain healthy. But the offered implementation—Check FortiManager platform and license device-management capacity against the expected number of registered devices, confirm supported scale and reserve room for HA clusters and planned growth.—addresses “Account for FortiManager managed device capacity and entitlement before expansion”. The action needed here is: Discover a FortiGate HA cluster using supported FortiManager procedures, verify cluster identity and member status, and use an appropriate cluster target when managing shared policy and device configuration.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- Fortinet FCP_FMG_AD-7.6 Practice Test 19 - 10 Questions (Last Reviewed 02-Nov-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 20 - 10 Questions (Last Reviewed 01-Nov-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 21 - 10 Questions (Last Reviewed 31-Oct-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 22 - 10 Questions (Last Reviewed 30-Oct-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 23 - 10 Questions (Last Reviewed 29-Oct-2026)