Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 28
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.
Question 271
A bank's FortiManager task has an error for one branch but completed for twenty others, requiring a precise targeted remediation. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: A
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. 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. Verify the result with this 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.
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: 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.
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: 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.
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: 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.
Question 272
A bank's FortiManager task has an error for one branch but completed for twenty others, requiring a precise targeted remediation. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: B
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: 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.
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 corresponding implementation is: 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.
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: 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.
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 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.
Question 273
A bank's FortiManager task has an error for one branch but completed for twenty others, requiring a precise targeted remediation. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: D
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: 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.
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: 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.
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: 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.
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. This check is decisive because 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.
Question 274
A bank's FortiManager task has an error for one branch but completed for twenty others, requiring a precise targeted remediation. Which proposed shortcut most directly risks repeated undesired changes and persistent failures from treating a script task error as a harmless notification and should therefore be rejected?
Answer & Explanations
Correct answer: B
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: Ignore all script execution logs and rerun a failed bulk configuration job against every branch until the central dashboard stops displaying a warning.
Ignore all script execution logs and rerun a failed bulk configuration job against every branch until the central dashboard stops displaying a warning. The foreseeable failure is repeated undesired changes and persistent failures from treating a script task error as a harmless notification. The safer response is: 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.
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: Ignore all script execution logs and rerun a failed bulk configuration job against every branch until the central dashboard stops displaying a warning.
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: Ignore all script execution logs and rerun a failed bulk configuration job against every branch until the central dashboard stops displaying a warning.
Question 275
A bank's FortiManager task has an error for one branch but completed for twenty others, requiring a precise targeted remediation. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: C
The action is applicable: 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. 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: 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 test would be relevant: 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. 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: 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.
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. Confirm it through this 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. 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.
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: 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.
Question 276
An MSP is evaluating whether a script error comes from the wrong ADOM target, missing permissions or a device command rejected by its firmware. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: A
The question is set in this situation: An MSP is evaluating whether a script error comes from the wrong ADOM target, missing permissions or a device command rejected by its firmware. 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. 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. Verify the result with this 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.
The question is set in this situation: An MSP is evaluating whether a script error comes from the wrong ADOM target, missing permissions or a device command rejected by its firmware. 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: 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.
Check FortiManager platform and license device-management capacity against the expected number of registered devices, confirm supported scale and reserve room for HA clusters and planned growth. This addresses “Account for FortiManager managed device capacity and entitlement before expansion”, where the governing principle is: Central management limits are not removed by renaming devices or adding ADOMs; exceeding supported capacity can block new registrations and make a deployment plan operationally invalid. The stated case instead calls for: 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.
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: 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.
Question 277
An MSP is evaluating whether a script error comes from the wrong ADOM target, missing permissions or a device command rejected by its firmware. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: D
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: 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 question is set in this situation: An MSP is evaluating whether a script error comes from the wrong ADOM target, missing permissions or a device command rejected by its firmware. 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 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.
Central management limits are not removed by renaming devices or adding ADOMs; exceeding supported capacity can block new registrations and make a deployment plan operationally invalid. That explains “Account for FortiManager managed device capacity and entitlement before expansion”, not the mechanism behind the described change. The relevant principle is: 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 question is set in this situation: An MSP is evaluating whether a script error comes from the wrong ADOM target, missing permissions or a device command rejected by its firmware. 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 corresponding implementation is: 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.
Question 278
An MSP is evaluating whether a script error comes from the wrong ADOM target, missing permissions or a device command rejected by its firmware. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: A
The question is set in this situation: An MSP is evaluating whether a script error comes from the wrong ADOM target, missing permissions or a device command rejected by its firmware. 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. This check is decisive because 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.
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: 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 question is set in this situation: An MSP is evaluating whether a script error comes from the wrong ADOM target, missing permissions or a device command rejected by its firmware. 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: 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.
Review current managed-device count and licensing on an authorized FortiManager instance, add a lab device within the approved capacity, and document a scale decision before exceeding it. That would help test “Account for FortiManager managed device capacity and entitlement before expansion”, not the outcome required in this scenario. The relevant acceptance check is: 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.
Question 279
An MSP is evaluating whether a script error comes from the wrong ADOM target, missing permissions or a device command rejected by its firmware. Which proposed shortcut most directly risks repeated undesired changes and persistent failures from treating a script task error as a harmless notification and should therefore be rejected?
Answer & Explanations
Correct answer: C
Assume creating dozens of ADOMs multiplies a FortiManager appliance's licensed device count indefinitely without purchasing capacity or verifying platform limits. That shortcut risks failed enterprise expansion when central device-management scale is assumed unlimited. Here the specific shortcut is: Ignore all script execution logs and rerun a failed bulk configuration job against every branch until the central dashboard stops displaying a warning.
The question is set in this situation: An MSP is evaluating whether a script error comes from the wrong ADOM target, missing permissions or a device command rejected by its firmware. 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: Ignore all script execution logs and rerun a failed bulk configuration job against every branch until the central dashboard stops displaying a warning.
The question is set in this situation: An MSP is evaluating whether a script error comes from the wrong ADOM target, missing permissions or a device command rejected by its firmware. Ignore all script execution logs and rerun a failed bulk configuration job against every branch until the central dashboard stops displaying a warning. The foreseeable failure is repeated undesired changes and persistent failures from treating a script task error as a harmless notification. The safer response is: 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.
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: Ignore all script execution logs and rerun a failed bulk configuration job against every branch until the central dashboard stops displaying a warning.
Question 280
An MSP is evaluating whether a script error comes from the wrong ADOM target, missing permissions or a device command rejected by its firmware. 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: 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.
The question is set in this situation: An MSP is evaluating whether a script error comes from the wrong ADOM target, missing permissions or a device command rejected by its firmware. 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. Confirm it through this 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. 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 action is applicable: 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. But its proposed 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.—addresses “Execute a FortiManager CLI script only on approved FortiGate targets”. This requirement is confirmed instead by: 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 test would be relevant: 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. But the offered implementation—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.—addresses “Execute a FortiManager CLI script only on approved FortiGate targets”. The action needed here is: 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.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- 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)
- Fortinet FCP_FMG_AD-7.6 Practice Test 30 - 10 Questions (Last Reviewed 22-Oct-2026)