Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 26
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.
Question 251
A bank manages FortiOS 7.4 and 7.6 branch devices and needs one controlled script schedule that does not assume identical command support. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: A
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. 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. Verify the result with this 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.
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: 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.
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: 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.
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: 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.
Question 252
A bank manages FortiOS 7.4 and 7.6 branch devices and needs one controlled script schedule that does not assume identical command support. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: C
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: 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 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: 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.
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 corresponding implementation is: 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.
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: 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.
Question 253
A bank manages FortiOS 7.4 and 7.6 branch devices and needs one controlled script schedule that does not assume identical command support. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: C
Run a harmless staged script, retrieve the affected setting, compare it with a stored before-state and confirm later central policy installation does not unintentionally undo the change. That would help test “Validate configuration after a FortiManager script instead of relying on task completion”, not the outcome required in this scenario. The relevant acceptance check is: 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.
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: 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.
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. This check is decisive because 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.
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: 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.
Question 254
A bank manages FortiOS 7.4 and 7.6 branch devices and needs one controlled script schedule that does not assume identical command support. Which proposed shortcut most directly risks partial configuration deployment after script command syntax or context is incompatible with target gateways and should therefore be rejected?
Answer & Explanations
Correct answer: B
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: Copy CLI lines from a different Fortinet product and execute them unmodified across mixed FortiOS releases while interpreting a submitted task as complete success.
Copy CLI lines from a different Fortinet product and execute them unmodified across mixed FortiOS releases while interpreting a submitted task as complete success. The foreseeable failure is partial configuration deployment after script command syntax or context is incompatible with target gateways. The safer response is: 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.
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: Copy CLI lines from a different Fortinet product and execute them unmodified across mixed FortiOS releases while interpreting a submitted task as complete success.
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: Copy CLI lines from a different Fortinet product and execute them unmodified across mixed FortiOS releases while interpreting a submitted task as complete success.
Question 255
A bank manages FortiOS 7.4 and 7.6 branch devices and needs one controlled script schedule that does not assume identical command support. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: D
The test would be relevant: 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. 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: 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.
The action is applicable: 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. 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 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.
This action/test pair addresses “Execute a FortiManager CLI script only on approved FortiGate targets”. 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. 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 case instead calls for: 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.
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. Confirm it through this 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. 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.
Question 256
A hospital network is investigating why a centrally launched script reports a device-side parse error despite working on the administrator's reference firewall. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: A
The question is set in this situation: A hospital network is investigating why a centrally launched script reports a device-side parse error despite working on the administrator's reference firewall. 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. 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. Verify the result with this 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.
The question is set in this situation: A hospital network is investigating why a centrally launched script reports a device-side parse error despite working on the administrator's reference firewall. 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: 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.
Read the actual FortiManager script task log and device-side command output, identify target authentication, mode or unsupported syntax problems, and rerun only after repairing the demonstrated issue. This addresses “Investigate a FortiManager script failure using per-device task results”, where the governing principle is: A global task may include successful and failed targets; executing the same script repeatedly without examining the FortiGate error can introduce duplicate changes while leaving the real issue unresolved. The stated case instead calls for: 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.
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: 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.
Question 257
A hospital network is investigating why a centrally launched script reports a device-side parse error despite working on the administrator's reference firewall. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: B
A global task may include successful and failed targets; executing the same script repeatedly without examining the FortiGate error can introduce duplicate changes while leaving the real issue unresolved. That explains “Investigate a FortiManager script failure using per-device task results”, not the mechanism behind the described change. The relevant 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 question is set in this situation: A hospital network is investigating why a centrally launched script reports a device-side parse error despite working on the administrator's reference firewall. 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 corresponding implementation is: 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.
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: 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 question is set in this situation: A hospital network is investigating why a centrally launched script reports a device-side parse error despite working on the administrator's reference firewall. 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: 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.
Question 258
A hospital network is investigating why a centrally launched script reports a device-side parse error despite working on the administrator's reference firewall. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: A
The question is set in this situation: A hospital network is investigating why a centrally launched script reports a device-side parse error despite working on the administrator's reference firewall. 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. This check is decisive because 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.
Trigger a controlled unsupported command on one staging FortiGate, locate the failed command and status in FortiManager task output, correct it and prove a narrow retry succeeds. That would help test “Investigate a FortiManager script failure using per-device task results”, not the outcome required in this scenario. The relevant acceptance check is: 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.
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: 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 question is set in this situation: A hospital network is investigating why a centrally launched script reports a device-side parse error despite working on the administrator's reference firewall. 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 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.
Question 259
A hospital network is investigating why a centrally launched script reports a device-side parse error despite working on the administrator's reference firewall. Which proposed shortcut most directly risks partial configuration deployment after script command syntax or context is incompatible with target gateways and should therefore be rejected?
Answer & Explanations
Correct answer: D
Ignore all script execution logs and rerun a failed bulk configuration job against every branch until the central dashboard stops displaying a warning. That shortcut risks repeated undesired changes and persistent failures from treating a script task error as a harmless notification. Here the specific shortcut is: Copy CLI lines from a different Fortinet product and execute them unmodified across mixed FortiOS releases while interpreting a submitted task as complete success.
The question is set in this situation: A hospital network is investigating why a centrally launched script reports a device-side parse error despite working on the administrator's reference firewall. 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: Copy CLI lines from a different Fortinet product and execute them unmodified across mixed FortiOS releases while interpreting a submitted task as complete success.
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: Copy CLI lines from a different Fortinet product and execute them unmodified across mixed FortiOS releases while interpreting a submitted task as complete success.
The question is set in this situation: A hospital network is investigating why a centrally launched script reports a device-side parse error despite working on the administrator's reference firewall. Copy CLI lines from a different Fortinet product and execute them unmodified across mixed FortiOS releases while interpreting a submitted task as complete success. The foreseeable failure is partial configuration deployment after script command syntax or context is incompatible with target gateways. The safer response is: 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.
Question 260
A hospital network is investigating why a centrally launched script reports a device-side parse error despite working on the administrator's reference firewall. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: C
The action is applicable: 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. But its proposed test—Trigger a controlled unsupported command on one staging FortiGate, locate the failed command and status in FortiManager task output, correct it and prove a narrow retry succeeds.—addresses “Investigate a FortiManager script failure using per-device task results”. This requirement is confirmed instead by: 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.
This action/test pair addresses “Validate configuration after a FortiManager script instead of relying on task completion”. 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. 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. The case instead calls for: 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.
The question is set in this situation: A hospital network is investigating why a centrally launched script reports a device-side parse error despite working on the administrator's reference firewall. 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. Confirm it through this 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. 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 test would be relevant: 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. But the offered implementation—Read the actual FortiManager script task log and device-side command output, identify target authentication, mode or unsupported syntax problems, and rerun only after repairing the demonstrated issue.—addresses “Investigate a FortiManager script failure using per-device task results”. The action needed here is: 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.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- 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)
- Fortinet FCP_FMG_AD-7.6 Practice Test 28 - 10 Questions (Last Reviewed 24-Oct-2026)