Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 29
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.
Question 281
A utility operator applies a device setting through FortiManager CLI scripts and needs proof the intended gateways actually enforce it. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: B
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: 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.
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. 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. Verify the result with this 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.
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: 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.
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: 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.
Question 282
A utility operator applies a device setting through FortiManager CLI scripts and needs proof the intended gateways actually enforce it. The engineer proposes the following change: 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. 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: 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.
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: 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.
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: 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 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 corresponding implementation is: 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.
Question 283
A utility operator applies a device setting through FortiManager CLI scripts and needs proof the intended gateways actually enforce it. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: A
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. This check is decisive because 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.
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 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.
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 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.
Run a version-appropriate test script on two firmware variants in a lab, inspect per-device output and changed configuration, and revise the script where a command is unsupported. That would help test “Choose script context and supported FortiOS syntax before bulk execution”, not the outcome required in this scenario. The relevant acceptance check is: Run a harmless 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.
Question 284
A utility operator applies a device setting through FortiManager CLI scripts and needs proof the intended gateways actually enforce it. Which proposed shortcut most directly risks false compliance evidence and later configuration rollback after script results are not reconciled with central management 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: Mark a script audit successful based solely on the job submission timestamp without examining whether the actual running FortiGate configuration changed.
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: Mark a script audit successful based solely on the job submission timestamp without examining whether the actual running FortiGate configuration changed.
Mark a script audit successful based solely on the job submission timestamp without examining whether the actual running FortiGate configuration changed. The foreseeable failure is false compliance evidence and later configuration rollback after script results are not reconciled with central management. The safer response is: 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.
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: Mark a script audit successful based solely on the job submission timestamp without examining whether the actual running FortiGate configuration changed.
Question 285
A utility operator applies a device setting through FortiManager CLI scripts and needs proof the intended gateways actually enforce it. 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 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. 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: 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.
The action is applicable: 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. 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: 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.
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: 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.
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. Confirm it through this 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. 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.
Question 286
A logistics company finds scripts completed but central device status remains out of sync and needs to reconcile the new configuration with FortiManager's databases. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: B
The question is set in this situation: A logistics company finds scripts completed but central device status remains out of sync and needs to reconcile the new configuration with FortiManager's databases. 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: 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.
The question is set in this situation: A logistics company finds scripts completed but central device status remains out of sync and needs to reconcile the new configuration with FortiManager's databases. 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. 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. Verify the result with this 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.
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: 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.
Discover a FortiGate HA cluster using supported FortiManager procedures, verify cluster identity and member status, and use an appropriate cluster target when managing shared policy and device configuration. This addresses “Register and manage a FortiGate HA cluster as a consistent logical target”, where the governing principle is: Multiple FortiGate HA member serial numbers do not necessarily represent independent production policy targets; a cluster has shared identity, synchronization state and supported installation behavior that must be understood. The stated case instead calls for: 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.
Question 287
A logistics company finds scripts completed but central device status remains out of sync and needs to reconcile the new configuration with FortiManager's databases. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: C
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: 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 question is set in this situation: A logistics company finds scripts completed but central device status remains out of sync and needs to reconcile the new configuration with FortiManager's databases. 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: 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 question is set in this situation: A logistics company finds scripts completed but central device status remains out of sync and needs to reconcile the new configuration with FortiManager's databases. 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 corresponding implementation is: 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.
Multiple FortiGate HA member serial numbers do not necessarily represent independent production policy targets; a cluster has shared identity, synchronization state and supported installation behavior that must be understood. That explains “Register and manage a FortiGate HA cluster as a consistent logical target”, not the mechanism behind the described change. The relevant 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.
Question 288
A logistics company finds scripts completed but central device status remains out of sync and needs to reconcile the new configuration with FortiManager's databases. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: A
The question is set in this situation: A logistics company finds scripts completed but central device status remains out of sync and needs to reconcile the new configuration with FortiManager's databases. 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. This check is decisive because 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.
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 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.
Add a staged two-member FortiGate cluster, inspect primary and secondary member information, install one harmless policy change through the proper managed target, and check both members remain healthy. That would help test “Register and manage a FortiGate HA cluster as a consistent logical target”, not the outcome required in this scenario. The relevant acceptance check is: 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 question is set in this situation: A logistics company finds scripts completed but central device status remains out of sync and needs to reconcile the new configuration with FortiManager's databases. 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 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.
Question 289
A logistics company finds scripts completed but central device status remains out of sync and needs to reconcile the new configuration with FortiManager's databases. Which proposed shortcut most directly risks false compliance evidence and later configuration rollback after script results are not reconciled with central management and should therefore be rejected?
Answer & Explanations
Correct answer: A
The question is set in this situation: A logistics company finds scripts completed but central device status remains out of sync and needs to reconcile the new configuration with FortiManager's databases. Mark a script audit successful based solely on the job submission timestamp without examining whether the actual running FortiGate configuration changed. The foreseeable failure is false compliance evidence and later configuration rollback after script results are not reconciled with central management. The safer response is: 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.
Treat each HA member as an unrelated branch firewall and independently apply conflicting production policies without checking cluster state or central management identity. That shortcut risks cluster synchronization conflict and traffic disruption caused by independently managing devices that belong to one HA cluster. Here the specific shortcut is: Mark a script audit successful based solely on the job submission timestamp without examining whether the actual running FortiGate configuration changed.
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: Mark a script audit successful based solely on the job submission timestamp without examining whether the actual running FortiGate configuration changed.
The question is set in this situation: A logistics company finds scripts completed but central device status remains out of sync and needs to reconcile the new configuration with FortiManager's databases. 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: Mark a script audit successful based solely on the job submission timestamp without examining whether the actual running FortiGate configuration changed.
Question 290
A logistics company finds scripts completed but central device status remains out of sync and needs to reconcile the new configuration with FortiManager's databases. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: B
The test would be relevant: 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. 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: 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.
The question is set in this situation: A logistics company finds scripts completed but central device status remains out of sync and needs to reconcile the new configuration with FortiManager's databases. 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. Confirm it through this 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. 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 action is applicable: 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. 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 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.
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: 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.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- 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)
- Fortinet FCP_FMG_AD-7.6 Practice Test 31 - 10 Questions (Last Reviewed 21-Oct-2026)