Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 34
Question 330
A retailer's branch device revision history contains several updates and the change board needs to isolate which single setting explains the reported failure. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: B
This action/test pair addresses “Retrieve the running FortiGate configuration to populate a new FortiManager revision”. Use the supported Retrieve Config operation for an approved device and compare the retrieved snapshot with the existing device database and known revision history before deciding whether to adopt differences. Change a harmless test setting directly on a staging FortiGate, retrieve configuration in FortiManager, inspect the revised record and document whether to accept or revert the local change. The case instead calls for: Open FortiManager's device revision comparison for an affected FortiGate, identify only the business-relevant lines that diverge, and choose a reviewed restoration rather than reverting all device settings automatically.
The question is set in this situation: A retailer's branch device revision history contains several updates and the change board needs to isolate which single setting explains the reported failure. Open FortiManager's device revision comparison for an affected FortiGate, identify only the business-relevant lines that diverge, and choose a reviewed restoration rather than reverting all device settings automatically. Confirm it through this test: Compare two stored revisions for a lab device with both an intentional description edit and a needed route fix, verify the cause and restore only an approved baseline where appropriate. Historical revisions provide evidence of particular changes, but reversing unrelated authorized edits can introduce new outages; a selective diagnosis is essential before invoking a broad revert operation.
The test would be relevant: Compare two stored revisions for a lab device with both an intentional description edit and a needed route fix, verify the cause and restore only an approved baseline where appropriate. But the offered implementation—When FortiManager reports a device configuration status of modified or out of sync, compare the central device database, last retrieved revision and actual FortiGate state before deciding whether to retrieve or reinstall.—addresses “Reconcile device database synchronization status with live FortiGate changes”. The action needed here is: Open FortiManager's device revision comparison for an affected FortiGate, identify only the business-relevant lines that diverge, and choose a reviewed restoration rather than reverting all device settings automatically.
The action is applicable: Open FortiManager's device revision comparison for an affected FortiGate, identify only the business-relevant lines that diverge, and choose a reviewed restoration rather than reverting all device settings automatically. But its proposed test—Introduce a controlled local configuration change on a test FortiGate, review device status and revision differences, then retrieve or restore as approved and confirm synchronized status.—addresses “Reconcile device database synchronization status with live FortiGate changes”. This requirement is confirmed instead by: Compare two stored revisions for a lab device with both an intentional description edit and a needed route fix, verify the cause and restore only an approved baseline where appropriate.
Question 331
A banking team receives an out-of-sync alert after a technician modifies a branch device directly and needs to protect the approved central baseline. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: A
When FortiManager reports a device configuration status of modified or out of sync, compare the central device database, last retrieved revision and actual FortiGate state before deciding whether to retrieve or reinstall. The FortiManager device database is not identical to every current FortiGate setting until retrieval or installation succeeds; a status indicator alone does not identify which side is authoritative. Verify the result with this test: Introduce a controlled local configuration change on a test FortiGate, review device status and revision differences, then retrieve or restore as approved and confirm synchronized status.
Open FortiManager's device revision comparison for an affected FortiGate, identify only the business-relevant lines that diverge, and choose a reviewed restoration rather than reverting all device settings automatically. This addresses “Use FortiManager configuration comparison before restoring a previous gateway revision”, where the governing principle is: Historical revisions provide evidence of particular changes, but reversing unrelated authorized edits can introduce new outages; a selective diagnosis is essential before invoking a broad revert operation. The stated case instead calls for: When FortiManager reports a device configuration status of modified or out of sync, compare the central device database, last retrieved revision and actual FortiGate state before deciding whether to retrieve or reinstall.
Use the supported Retrieve Config operation for an approved device and compare the retrieved snapshot with the existing device database and known revision history before deciding whether to adopt differences. This addresses “Retrieve the running FortiGate configuration to populate a new FortiManager revision”, where the governing principle is: Configuration retrieval observes actual device-side state and can create a new FortiManager revision; it does not automatically prove every locally changed setting was authorized or should become central policy. The stated case instead calls for: When FortiManager reports a device configuration status of modified or out of sync, compare the central device database, last retrieved revision and actual FortiGate state before deciding whether to retrieve or reinstall.
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: When FortiManager reports a device configuration status of modified or out of sync, compare the central device database, last retrieved revision and actual FortiGate state before deciding whether to retrieve or reinstall.
Question 332
A banking team receives an out-of-sync alert after a technician modifies a branch device directly and needs to protect the approved central baseline. The engineer proposes the following change: When FortiManager reports a device configuration status of modified or out of sync, compare the central device database, last retrieved revision and actual FortiGate state before deciding whether to retrieve or reinstall. Which mechanism explains why it works?
Answer & Explanations
Correct answer: C
Historical revisions provide evidence of particular changes, but reversing unrelated authorized edits can introduce new outages; a selective diagnosis is essential before invoking a broad revert operation. That explains “Use FortiManager configuration comparison before restoring a previous gateway revision”, not the mechanism behind the described change. The relevant principle is: The FortiManager device database is not identical to every current FortiGate setting until retrieval or installation succeeds; a status indicator alone does not identify which side is authoritative.
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: The FortiManager device database is not identical to every current FortiGate setting until retrieval or installation succeeds; a status indicator alone does not identify which side is authoritative.
The FortiManager device database is not identical to every current FortiGate setting until retrieval or installation succeeds; a status indicator alone does not identify which side is authoritative. The corresponding implementation is: When FortiManager reports a device configuration status of modified or out of sync, compare the central device database, last retrieved revision and actual FortiGate state before deciding whether to retrieve or reinstall.
Configuration retrieval observes actual device-side state and can create a new FortiManager revision; it does not automatically prove every locally changed setting was authorized or should become central policy. That explains “Retrieve the running FortiGate configuration to populate a new FortiManager revision”, not the mechanism behind the described change. The relevant principle is: The FortiManager device database is not identical to every current FortiGate setting until retrieval or installation succeeds; a status indicator alone does not identify which side is authoritative.
Question 333
A banking team receives an out-of-sync alert after a technician modifies a branch device directly and needs to protect the approved central baseline. After implementing this change—When FortiManager reports a device configuration status of modified or out of sync, compare the central device database, last retrieved revision and actual FortiGate state before deciding whether to retrieve or reinstall.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: B
Change a harmless test setting directly on a staging FortiGate, retrieve configuration in FortiManager, inspect the revised record and document whether to accept or revert the local change. That would help test “Retrieve the running FortiGate configuration to populate a new FortiManager revision”, not the outcome required in this scenario. The relevant acceptance check is: Introduce a controlled local configuration change on a test FortiGate, review device status and revision differences, then retrieve or restore as approved and confirm synchronized status.
Introduce a controlled local configuration change on a test FortiGate, review device status and revision differences, then retrieve or restore as approved and confirm synchronized status. This check is decisive because the FortiManager device database is not identical to every current FortiGate setting until retrieval or installation succeeds; a status indicator alone does not identify which side is authoritative.
Compare two stored revisions for a lab device with both an intentional description edit and a needed route fix, verify the cause and restore only an approved baseline where appropriate. That would help test “Use FortiManager configuration comparison before restoring a previous gateway revision”, not the outcome required in this scenario. The relevant acceptance check is: Introduce a controlled local configuration change on a test FortiGate, review device status and revision differences, then retrieve or restore as approved and confirm synchronized status.
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: Introduce a controlled local configuration change on a test FortiGate, review device status and revision differences, then retrieve or restore as approved and confirm synchronized status.
Question 334
A banking team receives an out-of-sync alert after a technician modifies a branch device directly and needs to protect the approved central baseline. Which proposed shortcut most directly risks persistent unauthorized configuration drift when FortiManager sync status is fixed without understanding which values changed and should therefore be rejected?
Answer & Explanations
Correct answer: D
Mark a script audit successful based solely on the job submission timestamp without examining whether the actual running FortiGate configuration changed. That shortcut risks false compliance evidence and later configuration rollback after script results are not reconciled with central management. Here the specific shortcut is: Click the synchronize button repeatedly without comparing intended central values against the changed firewall and assume every live device alteration was safe to adopt.
Select the oldest available device revision and force an unrestricted rollback of a branch firewall without checking whether it contains required routing and security updates. That shortcut risks branch connectivity loss after restoring an obsolete configuration in response to one isolated drift symptom. Here the specific shortcut is: Click the synchronize button repeatedly without comparing intended central values against the changed firewall and assume every live device alteration was safe to adopt.
Press Retrieve Config after an unreviewed local change and declare all modifications approved corporate policy merely because the management database now contains them. That shortcut risks unauthorized local changes legitimized when retrieved device configuration is mistaken for reviewed intent. Here the specific shortcut is: Click the synchronize button repeatedly without comparing intended central values against the changed firewall and assume every live device alteration was safe to adopt.
Click the synchronize button repeatedly without comparing intended central values against the changed firewall and assume every live device alteration was safe to adopt. The foreseeable failure is persistent unauthorized configuration drift when FortiManager sync status is fixed without understanding which values changed. The safer response is: When FortiManager reports a device configuration status of modified or out of sync, compare the central device database, last retrieved revision and actual FortiGate state before deciding whether to retrieve or reinstall.
Question 335
A banking team receives an out-of-sync alert after a technician modifies a branch device directly and needs to protect the approved central baseline. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: C
The test would be relevant: Introduce a controlled local configuration change on a test FortiGate, review device status and revision differences, then retrieve or restore as approved and confirm synchronized status. But the offered implementation—Open FortiManager's device revision comparison for an affected FortiGate, identify only the business-relevant lines that diverge, and choose a reviewed restoration rather than reverting all device settings automatically.—addresses “Use FortiManager configuration comparison before restoring a previous gateway revision”. The action needed here is: When FortiManager reports a device configuration status of modified or out of sync, compare the central device database, last retrieved revision and actual FortiGate state before deciding whether to retrieve or reinstall.
The action is applicable: When FortiManager reports a device configuration status of modified or out of sync, compare the central device database, last retrieved revision and actual FortiGate state before deciding whether to retrieve or reinstall. But its proposed test—Compare two stored revisions for a lab device with both an intentional description edit and a needed route fix, verify the cause and restore only an approved baseline where appropriate.—addresses “Use FortiManager configuration comparison before restoring a previous gateway revision”. This requirement is confirmed instead by: Introduce a controlled local configuration change on a test FortiGate, review device status and revision differences, then retrieve or restore as approved and confirm synchronized status.
When FortiManager reports a device configuration status of modified or out of sync, compare the central device database, last retrieved revision and actual FortiGate state before deciding whether to retrieve or reinstall. Confirm it through this test: Introduce a controlled local configuration change on a test FortiGate, review device status and revision differences, then retrieve or restore as approved and confirm synchronized status. The FortiManager device database is not identical to every current FortiGate setting until retrieval or installation succeeds; a status indicator alone does not identify which side is authoritative.
This action/test pair addresses “Retrieve the running FortiGate configuration to populate a new FortiManager revision”. Use the supported Retrieve Config operation for an approved device and compare the retrieved snapshot with the existing device database and known revision history before deciding whether to adopt differences. Change a harmless test setting directly on a staging FortiGate, retrieve configuration in FortiManager, inspect the revised record and document whether to accept or revert the local change. The case instead calls for: When FortiManager reports a device configuration status of modified or out of sync, compare the central device database, last retrieved revision and actual FortiGate state before deciding whether to retrieve or reinstall.
Question 336
An MSP is reconciling one customer firewall that differs from the FortiManager device database despite having a recent successful policy installation. 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 reconciling one customer firewall that differs from the FortiManager device database despite having a recent successful policy installation. When FortiManager reports a device configuration status of modified or out of sync, compare the central device database, last retrieved revision and actual FortiGate state before deciding whether to retrieve or reinstall. The FortiManager device database is not identical to every current FortiGate setting until retrieval or installation succeeds; a status indicator alone does not identify which side is authoritative. Verify the result with this test: Introduce a controlled local configuration change on a test FortiGate, review device status and revision differences, then retrieve or restore as approved and confirm synchronized status.
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: When FortiManager reports a device configuration status of modified or out of sync, compare the central device database, last retrieved revision and actual FortiGate state before deciding whether to retrieve or reinstall.
The question is set in this situation: An MSP is reconciling one customer firewall that differs from the FortiManager device database despite having a recent successful policy installation. Open FortiManager's device revision comparison for an affected FortiGate, identify only the business-relevant lines that diverge, and choose a reviewed restoration rather than reverting all device settings automatically. This addresses “Use FortiManager configuration comparison before restoring a previous gateway revision”, where the governing principle is: Historical revisions provide evidence of particular changes, but reversing unrelated authorized edits can introduce new outages; a selective diagnosis is essential before invoking a broad revert operation. The stated case instead calls for: When FortiManager reports a device configuration status of modified or out of sync, compare the central device database, last retrieved revision and actual FortiGate state before deciding whether to retrieve or reinstall.
Copy a reviewed system template into another supported ADOM while validating version compatibility, referenced interfaces and device-specific variables before assigning it to the destination tenant. This addresses “Move a FortiManager provisioning template between compatible ADOMs safely”, where the governing principle is: An ADOM copy can preserve template logic while omitting assumptions about destination devices or permissions; identical text can have different effects across firmware versions or interface inventories. The stated case instead calls for: When FortiManager reports a device configuration status of modified or out of sync, compare the central device database, last retrieved revision and actual FortiGate state before deciding whether to retrieve or reinstall.
Question 337
An MSP is reconciling one customer firewall that differs from the FortiManager device database despite having a recent successful policy installation. The engineer proposes the following change: When FortiManager reports a device configuration status of modified or out of sync, compare the central device database, last retrieved revision and actual FortiGate state before deciding whether to retrieve or reinstall. Which mechanism explains why it works?
Answer & Explanations
Correct answer: B
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: The FortiManager device database is not identical to every current FortiGate setting until retrieval or installation succeeds; a status indicator alone does not identify which side is authoritative.
The question is set in this situation: An MSP is reconciling one customer firewall that differs from the FortiManager device database despite having a recent successful policy installation. The FortiManager device database is not identical to every current FortiGate setting until retrieval or installation succeeds; a status indicator alone does not identify which side is authoritative. The corresponding implementation is: When FortiManager reports a device configuration status of modified or out of sync, compare the central device database, last retrieved revision and actual FortiGate state before deciding whether to retrieve or reinstall.
An ADOM copy can preserve template logic while omitting assumptions about destination devices or permissions; identical text can have different effects across firmware versions or interface inventories. That explains “Move a FortiManager provisioning template between compatible ADOMs safely”, not the mechanism behind the described change. The relevant principle is: The FortiManager device database is not identical to every current FortiGate setting until retrieval or installation succeeds; a status indicator alone does not identify which side is authoritative.
The question is set in this situation: An MSP is reconciling one customer firewall that differs from the FortiManager device database despite having a recent successful policy installation. Historical revisions provide evidence of particular changes, but reversing unrelated authorized edits can introduce new outages; a selective diagnosis is essential before invoking a broad revert operation. That explains “Use FortiManager configuration comparison before restoring a previous gateway revision”, not the mechanism behind the described change. The relevant principle is: The FortiManager device database is not identical to every current FortiGate setting until retrieval or installation succeeds; a status indicator alone does not identify which side is authoritative.
Question 338
An MSP is reconciling one customer firewall that differs from the FortiManager device database despite having a recent successful policy installation. After implementing this change—When FortiManager reports a device configuration status of modified or out of sync, compare the central device database, last retrieved revision and actual FortiGate state before deciding whether to retrieve or reinstall.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: D
The question is set in this situation: An MSP is reconciling one customer firewall that differs from the FortiManager device database despite having a recent successful policy installation. Compare two stored revisions for a lab device with both an intentional description edit and a needed route fix, verify the cause and restore only an approved baseline where appropriate. That would help test “Use FortiManager configuration comparison before restoring a previous gateway revision”, not the outcome required in this scenario. The relevant acceptance check is: Introduce a controlled local configuration change on a test FortiGate, review device status and revision differences, then retrieve or restore as approved and confirm synchronized status.
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: Introduce a controlled local configuration change on a test FortiGate, review device status and revision differences, then retrieve or restore as approved and confirm synchronized status.
Copy a sample template from an internal lab ADOM to a separate test tenant, compare object references and target compatibility, and test deployment to one noncritical firewall. That would help test “Move a FortiManager provisioning template between compatible ADOMs safely”, not the outcome required in this scenario. The relevant acceptance check is: Introduce a controlled local configuration change on a test FortiGate, review device status and revision differences, then retrieve or restore as approved and confirm synchronized status.
The question is set in this situation: An MSP is reconciling one customer firewall that differs from the FortiManager device database despite having a recent successful policy installation. Introduce a controlled local configuration change on a test FortiGate, review device status and revision differences, then retrieve or restore as approved and confirm synchronized status. This check is decisive because the FortiManager device database is not identical to every current FortiGate setting until retrieval or installation succeeds; a status indicator alone does not identify which side is authoritative.
Question 339
An MSP is reconciling one customer firewall that differs from the FortiManager device database despite having a recent successful policy installation. Which proposed shortcut most directly risks persistent unauthorized configuration drift when FortiManager sync status is fixed without understanding which values changed and should therefore be rejected?
Answer & Explanations
Correct answer: A
The question is set in this situation: An MSP is reconciling one customer firewall that differs from the FortiManager device database despite having a recent successful policy installation. Click the synchronize button repeatedly without comparing intended central values against the changed firewall and assume every live device alteration was safe to adopt. The foreseeable failure is persistent unauthorized configuration drift when FortiManager sync status is fixed without understanding which values changed. The safer response is: When FortiManager reports a device configuration status of modified or out of sync, compare the central device database, last retrieved revision and actual FortiGate state before deciding whether to retrieve or reinstall.
Assume transferring a template across ADOMs automatically migrates all customer credentials, interface names and version-specific commands without review. That shortcut risks cross-tenant configuration errors after reusing an incompatible shared provisioning template. Here the specific shortcut is: Click the synchronize button repeatedly without comparing intended central values against the changed firewall and assume every live device alteration was safe to adopt.
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: Click the synchronize button repeatedly without comparing intended central values against the changed firewall and assume every live device alteration was safe to adopt.
The question is set in this situation: An MSP is reconciling one customer firewall that differs from the FortiManager device database despite having a recent successful policy installation. Select the oldest available device revision and force an unrestricted rollback of a branch firewall without checking whether it contains required routing and security updates. That shortcut risks branch connectivity loss after restoring an obsolete configuration in response to one isolated drift symptom. Here the specific shortcut is: Click the synchronize button repeatedly without comparing intended central values against the changed firewall and assume every live device alteration was safe to adopt.
Question 340
An MSP is reconciling one customer firewall that differs from the FortiManager device database despite having a recent successful policy installation. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: C
The action is applicable: When FortiManager reports a device configuration status of modified or out of sync, compare the central device database, last retrieved revision and actual FortiGate state before deciding whether to retrieve or reinstall. But its proposed test—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.—addresses “Distinguish an automatic device configuration revision from an ADOM policy revision”. This requirement is confirmed instead by: Introduce a controlled local configuration change on a test FortiGate, review device status and revision differences, then retrieve or restore as approved and confirm synchronized status.
This action/test pair addresses “Use FortiManager configuration comparison before restoring a previous gateway revision”. Open FortiManager's device revision comparison for an affected FortiGate, identify only the business-relevant lines that diverge, and choose a reviewed restoration rather than reverting all device settings automatically. Compare two stored revisions for a lab device with both an intentional description edit and a needed route fix, verify the cause and restore only an approved baseline where appropriate. The case instead calls for: When FortiManager reports a device configuration status of modified or out of sync, compare the central device database, last retrieved revision and actual FortiGate state before deciding whether to retrieve or reinstall.
The question is set in this situation: An MSP is reconciling one customer firewall that differs from the FortiManager device database despite having a recent successful policy installation. When FortiManager reports a device configuration status of modified or out of sync, compare the central device database, last retrieved revision and actual FortiGate state before deciding whether to retrieve or reinstall. Confirm it through this test: Introduce a controlled local configuration change on a test FortiGate, review device status and revision differences, then retrieve or restore as approved and confirm synchronized status. The FortiManager device database is not identical to every current FortiGate setting until retrieval or installation succeeds; a status indicator alone does not identify which side is authoritative.
The test would be relevant: Introduce a controlled local configuration change on a test FortiGate, review device status and revision differences, then retrieve or restore as approved and confirm synchronized status. But the offered implementation—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.—addresses “Distinguish an automatic device configuration revision from an ADOM policy revision”. The action needed here is: When FortiManager reports a device configuration status of modified or out of sync, compare the central device database, last retrieved revision and actual FortiGate state before deciding whether to retrieve or reinstall.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- Fortinet FCP_FMG_AD-7.6 Practice Test 32 - 10 Questions (Last Reviewed 20-Oct-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 33 - 10 Questions (Last Reviewed 19-Oct-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 34 - 10 Questions (Last Reviewed 18-Oct-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 35 - 10 Questions (Last Reviewed 17-Oct-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 36 - 10 Questions (Last Reviewed 16-Oct-2026)