Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 27
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.
Question 261
A regional retailer needs to make an approved configuration change to store gateways after the closing shift and must record which sites actually changed. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: A
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. 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. Verify the result with this test: 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.
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: 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.
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: 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.
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: 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.
Question 262
A regional retailer needs to make an approved configuration change to store gateways after the closing shift and must record which sites actually changed. The engineer proposes the following 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: D
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: 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.
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: 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 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: 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.
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 corresponding implementation is: 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.
Question 263
A regional retailer needs to make an approved configuration change to store gateways after the closing shift and must record which sites actually changed. After implementing this 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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: B
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: 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.
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. This check is decisive because 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.
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: 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.
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: 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.
Question 264
A regional retailer needs to make an approved configuration change to store gateways after the closing shift and must record which sites actually changed. Which proposed shortcut most directly risks unverified fleet-wide drift when FortiManager scheduling is mistaken for confirmed execution and should therefore be rejected?
Answer & Explanations
Correct answer: C
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: Schedule destructive configuration changes for midnight and declare every remote firewall updated before checking whether the devices were online or the commands completed.
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: Schedule destructive configuration changes for midnight and declare every remote firewall updated before checking whether the devices were online or the commands completed.
Schedule destructive configuration changes for midnight and declare every remote firewall updated before checking whether the devices were online or the commands completed. The foreseeable failure is unverified fleet-wide drift when FortiManager scheduling is mistaken for confirmed execution. The safer response is: 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.
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 destructive configuration changes for midnight and declare every remote firewall updated before checking whether the devices were online or the commands completed.
Question 265
A regional retailer needs to make an approved configuration change to store gateways after the closing shift and must record which sites actually changed. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: B
The test would be relevant: 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. 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: 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.
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. Confirm it through this test: 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. 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.
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: 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.
The action is applicable: 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. 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: 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.
Question 266
A government organization uses FortiManager scripts for planned updates and requires an evidence trail for any device that missed the window. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: C
Match a FortiManager script's execution environment, command hierarchy and supported FortiOS version to the intended managed devices, and test commands in a compatible staging firewall before scheduling production execution. This addresses “Choose script context and supported FortiOS syntax before bulk execution”, where the governing principle is: Commands accepted on one FortiOS release or config subtree may fail in another context; FortiManager task submission success does not prove every child command was executed correctly. The stated case instead calls for: 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.
The question is set in this situation: A government organization uses FortiManager scripts for planned updates and requires an evidence trail for any device that missed the window. 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: 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.
The question is set in this situation: A government organization uses FortiManager scripts for planned updates and requires an evidence trail for any device that missed the window. 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. 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. Verify the result with this test: 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.
Inspect the source and timestamp of an automatic FortiManager device configuration revision and compare it with separately managed ADOM revisions so the scope of a rollback is documented accurately. This addresses “Distinguish an automatic device configuration revision from an ADOM policy revision”, where the governing principle is: Device revisions capture relevant retrieved or managed gateway configuration state, whereas ADOM revisions represent central package and object snapshots; their audit and restoration purposes differ. The stated case instead calls for: Use 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.
Question 267
A government organization uses FortiManager scripts for planned updates and requires an evidence trail for any device that missed the window. The engineer proposes the following 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: A
The question is set in this situation: A government organization uses FortiManager scripts for planned updates and requires an evidence trail for any device that missed the window. 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 corresponding implementation is: 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.
Device revisions capture relevant retrieved or managed gateway configuration state, whereas ADOM revisions represent central package and object snapshots; their audit and restoration purposes differ. That explains “Distinguish an automatic device configuration revision from an ADOM policy revision”, not the mechanism behind the described change. The relevant principle is: A 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 question is set in this situation: A government organization uses FortiManager scripts for planned updates and requires an evidence trail for any device that missed the window. 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: 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.
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: 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.
Question 268
A government organization uses FortiManager scripts for planned updates and requires an evidence trail for any device that missed the window. After implementing this 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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: D
Create a benign device-side change and an unrelated ADOM object change in a lab, verify which revision histories update and demonstrate independent scope for each recovery decision. That would help test “Distinguish an automatic device configuration revision from an ADOM policy revision”, not the outcome required in this scenario. The relevant acceptance check is: 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.
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: 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 question is set in this situation: A government organization uses FortiManager scripts for planned updates and requires an evidence trail for any device that missed the window. 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: 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 question is set in this situation: A government organization uses FortiManager scripts for planned updates and requires an evidence trail for any device that missed the window. 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. This check is decisive because 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.
Question 269
A government organization uses FortiManager scripts for planned updates and requires an evidence trail for any device that missed the window. Which proposed shortcut most directly risks unverified fleet-wide drift when FortiManager scheduling is mistaken for confirmed execution and should therefore be rejected?
Answer & Explanations
Correct answer: C
Copy CLI lines from a different Fortinet product and execute them unmodified across mixed FortiOS releases while interpreting a submitted task as complete success. That shortcut risks partial configuration deployment after script command syntax or context is incompatible with target gateways. Here the specific shortcut is: Schedule destructive configuration changes for midnight and declare every remote firewall updated before checking whether the devices were online or the commands completed.
Treat any FortiManager revision number as a universal snapshot of all gateways, policies, objects, administrators and global settings and restore it without checking scope. That shortcut risks wrong rollback selection after central and device configuration snapshots are conflated. Here the specific shortcut is: Schedule destructive configuration changes for midnight and declare every remote firewall updated before checking whether the devices were online or the commands completed.
The question is set in this situation: A government organization uses FortiManager scripts for planned updates and requires an evidence trail for any device that missed the window. Schedule destructive configuration changes for midnight and declare every remote firewall updated before checking whether the devices were online or the commands completed. The foreseeable failure is unverified fleet-wide drift when FortiManager scheduling is mistaken for confirmed execution. The safer response is: 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.
The question is set in this situation: A government organization uses FortiManager scripts for planned updates and requires an evidence trail for any device that missed the window. 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: Schedule destructive configuration changes for midnight and declare every remote firewall updated before checking whether the devices were online or the commands completed.
Question 270
A government organization uses FortiManager scripts for planned updates and requires an evidence trail for any device that missed the window. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: D
The test would be relevant: 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. 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: 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.
The action is applicable: 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. 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: 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.
This action/test pair addresses “Investigate a FortiManager script failure using per-device task results”. 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. 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. The case instead calls for: 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.
The question is set in this situation: A government organization uses FortiManager scripts for planned updates and requires an evidence trail for any device that missed the window. 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. Confirm it through this test: 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. 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.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- 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)
- Fortinet FCP_FMG_AD-7.6 Practice Test 29 - 10 Questions (Last Reviewed 23-Oct-2026)