Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 25
Question 240
A university expects an acquisition to double managed gateway count and needs evidence that the central management platform can support the additional devices. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: A
The question is set in this situation: A university expects an acquisition to double managed gateway count and needs evidence that the central management platform can support the additional devices. 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. Confirm it through this 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. 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 test would be relevant: 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. 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: 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.
The action is applicable: 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. 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: 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.
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: 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.
Question 241
A multinational insurer wants to standardize a minor FortiGate setting on ten selected sites without touching production branches in other regions. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: B
Open FortiManager's device revision comparison for an affected FortiGate, identify only the business-relevant lines that diverge, and choose a reviewed restoration rather than reverting all device settings automatically. This addresses “Use FortiManager configuration comparison before restoring a previous gateway revision”, where the governing principle is: Historical revisions provide evidence of particular changes, but reversing unrelated authorized edits can introduce new outages; a selective diagnosis is essential before invoking a broad revert operation. The stated case instead calls for: 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.
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. 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. Verify the result with this test: 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.
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: 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.
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: 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.
Question 242
A multinational insurer wants to standardize a minor FortiGate setting on ten selected sites without touching production branches in other regions. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: A
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 corresponding implementation is: 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.
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: 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.
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: 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.
Historical revisions provide evidence of particular changes, but reversing unrelated authorized edits can introduce new outages; a selective diagnosis is essential before invoking a broad revert operation. That explains “Use FortiManager configuration comparison before restoring a previous gateway revision”, not the mechanism behind the described change. The relevant 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.
Question 243
A multinational insurer wants to standardize a minor FortiGate setting on ten selected sites without touching production branches in other regions. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: C
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: 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.
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: 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.
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. This check is decisive because 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.
Compare two stored revisions for a lab device with both an intentional description edit and a needed route fix, verify the cause and restore only an approved baseline where appropriate. That would help test “Use FortiManager configuration comparison before restoring a previous gateway revision”, not the outcome required in this scenario. The relevant acceptance check is: 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.
Question 244
A multinational insurer wants to standardize a minor FortiGate setting on ten selected sites without touching production branches in other regions. Which proposed shortcut most directly risks mass configuration drift after a valid command is executed against unapproved devices and should therefore be rejected?
Answer & Explanations
Correct answer: D
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: Schedule an unreviewed administrator-level CLI script against every FortiManager device across all customers because it worked once on a single test box.
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: Schedule an unreviewed administrator-level CLI script against every FortiManager device across all customers because it worked once on a single test box.
Select the oldest available device revision and force an unrestricted rollback of a branch firewall without checking whether it contains required routing and security updates. That shortcut risks branch connectivity loss after restoring an obsolete configuration in response to one isolated drift symptom. Here the specific shortcut is: Schedule an unreviewed administrator-level CLI script against every FortiManager device across all customers because it worked once on a single test box.
Schedule an unreviewed administrator-level CLI script against every FortiManager device across all customers because it worked once on a single test box. The foreseeable failure is mass configuration drift after a valid command is executed against unapproved devices. The safer response is: 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.
Question 245
A multinational insurer wants to standardize a minor FortiGate setting on ten selected sites without touching production branches in other regions. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: A
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. Confirm it through this test: 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. 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 action is applicable: 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. But its proposed test—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.—addresses “Choose script context and supported FortiOS syntax before bulk execution”. This requirement is confirmed instead by: 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.
This action/test pair addresses “Schedule scripts within controlled FortiManager maintenance windows”. 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. 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. The case instead calls for: 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.
The test would be relevant: 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. But the offered implementation—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.—addresses “Choose script context and supported FortiOS syntax before bulk execution”. The action needed here is: 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.
Question 246
An MSP is designing a repeatable FortiManager script process where per-customer target approval is mandatory before execution. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: C
Retrieve or inspect the relevant FortiGate configuration after an authorized script runs, compare the actual setting to the planned state and document any central database reconciliation required. This addresses “Validate configuration after a FortiManager script instead of relying on task completion”, where the governing principle is: The script engine's task result and the gateway's active configuration are separate sources of evidence; manual device-level changes can create differences that require FortiManager database updates or an import. The stated case instead calls for: 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.
The question is set in this situation: An MSP is designing a repeatable FortiManager script process where per-customer target approval is mandatory before execution. 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: 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.
The question is set in this situation: An MSP is designing a repeatable FortiManager script process where per-customer target approval is mandatory before execution. 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. 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. Verify the result with this test: 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.
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: 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.
Question 247
An MSP is designing a repeatable FortiManager script process where per-customer target approval is mandatory before execution. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: B
The question is set in this situation: An MSP is designing a repeatable FortiManager script process where per-customer target approval is mandatory before execution. 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: 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 question is set in this situation: An MSP is designing a repeatable FortiManager script process where per-customer target approval is mandatory before execution. 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 corresponding implementation is: 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.
The script engine's task result and the gateway's active configuration are separate sources of evidence; manual device-level changes can create differences that require FortiManager database updates or an import. That explains “Validate configuration after a FortiManager script instead of relying on task completion”, not the mechanism behind the described change. The relevant principle is: 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.
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: 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.
Question 248
An MSP is designing a repeatable FortiManager script process where per-customer target approval is mandatory before execution. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: 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: 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.
The question is set in this situation: An MSP is designing a repeatable FortiManager script process where per-customer target approval is mandatory before execution. 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: 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.
Run a harmless staged script, retrieve the affected setting, compare it with a stored before-state and confirm later central policy installation does not unintentionally undo the change. That would help test “Validate configuration after a FortiManager script instead of relying on task completion”, not the outcome required in this scenario. The relevant acceptance check is: 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.
The question is set in this situation: An MSP is designing a repeatable FortiManager script process where per-customer target approval is mandatory before execution. 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. This check is decisive because 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.
Question 249
An MSP is designing a repeatable FortiManager script process where per-customer target approval is mandatory before execution. Which proposed shortcut most directly risks mass configuration drift after a valid command is executed against unapproved devices and should therefore be rejected?
Answer & Explanations
Correct answer: D
Mark a script audit successful based solely on the job submission timestamp without examining whether the actual running FortiGate configuration changed. That shortcut risks false compliance evidence and later configuration rollback after script results are not reconciled with central management. Here the specific shortcut is: Schedule an unreviewed administrator-level CLI script against every FortiManager device across all customers because it worked once on a single test box.
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: Schedule an unreviewed administrator-level CLI script against every FortiManager device across all customers because it worked once on a single test box.
The question is set in this situation: An MSP is designing a repeatable FortiManager script process where per-customer target approval is mandatory before execution. 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: Schedule an unreviewed administrator-level CLI script against every FortiManager device across all customers because it worked once on a single test box.
The question is set in this situation: An MSP is designing a repeatable FortiManager script process where per-customer target approval is mandatory before execution. Schedule an unreviewed administrator-level CLI script against every FortiManager device across all customers because it worked once on a single test box. The foreseeable failure is mass configuration drift after a valid command is executed against unapproved devices. The safer response is: 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.
Question 250
An MSP is designing a repeatable FortiManager script process where per-customer target approval is mandatory before execution. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: B
This action/test pair addresses “Choose script context and supported FortiOS syntax before bulk execution”. 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. 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. The case instead calls for: 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.
The question is set in this situation: An MSP is designing a repeatable FortiManager script process where per-customer target approval is mandatory before execution. 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. Confirm it through this test: 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. 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 action is applicable: 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. But its proposed test—Run a harmless staged script, retrieve the affected setting, compare it with a stored before-state and confirm later central policy installation does not unintentionally undo the change.—addresses “Validate configuration after a FortiManager script instead of relying on task completion”. This requirement is confirmed instead by: 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.
The test would be relevant: 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. But the offered implementation—Retrieve or inspect the relevant FortiGate configuration after an authorized script runs, compare the actual setting to the planned state and document any central database reconciliation required.—addresses “Validate configuration after a FortiManager script instead of relying on task completion”. The action needed here is: 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.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- Fortinet FCP_FMG_AD-7.6 Practice Test 23 - 10 Questions (Last Reviewed 29-Oct-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 24 - 10 Questions (Last Reviewed 28-Oct-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 25 - 10 Questions (Last Reviewed 27-Oct-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 26 - 10 Questions (Last Reviewed 26-Oct-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 27 - 10 Questions (Last Reviewed 25-Oct-2026)