Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 32
Question 310
A research institution is planning a targeted FortiGate rollback without rolling back every central object or policy in the ADOM. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: A
The question is set in this situation: A research institution is planning a targeted FortiGate rollback without rolling back every central object or policy in the ADOM. Compare a managed device's current stored revision with the last approved revision, locate the precise changed settings, and apply a supported restoration or central redeployment after appropriate review. Confirm it through this test: Modify a safe lab interface description, retrieve the new revision, compare with the baseline and restore an approved version without deleting unrelated ADOM policy objects. Device revision history helps reconstruct configuration changes and revert known states, while snapshots are not the same as an ADOM-wide policy/object database revision.
The test would be relevant: Modify a safe lab interface description, retrieve the new revision, compare with the baseline and restore an approved version without deleting unrelated ADOM policy objects. 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: Compare a managed device's current stored revision with the last approved revision, locate the precise changed settings, and apply a supported restoration or central redeployment after appropriate review.
The action is applicable: Compare a managed device's current stored revision with the last approved revision, locate the precise changed settings, and apply a supported restoration or central redeployment after appropriate review. 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: Modify a safe lab interface description, retrieve the new revision, compare with the baseline and restore an approved version without deleting unrelated ADOM policy objects.
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: Compare a managed device's current stored revision with the last approved revision, locate the precise changed settings, and apply a supported restoration or central redeployment after appropriate review.
Question 311
A managed services provider is investigating whether a firewall interface edit or shared object update caused an install warning. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: C
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: 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.
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: 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.
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. 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. Verify the result with this 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.
Compare a managed device's current stored revision with the last approved revision, locate the precise changed settings, and apply a supported restoration or central redeployment after appropriate review. This addresses “Use FortiManager device revision history to identify and repair drift”, where the governing principle is: Device revision history helps reconstruct configuration changes and revert known states, while snapshots are not the same as an ADOM-wide policy/object database revision. The stated case instead calls for: 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.
Question 312
A managed services provider is investigating whether a firewall interface edit or shared object update caused an install warning. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: D
Device revision history helps reconstruct configuration changes and revert known states, while snapshots are not the same as an ADOM-wide policy/object database revision. That explains “Use FortiManager device revision history to identify and repair drift”, not the mechanism behind the described change. The relevant 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.
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: 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.
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: 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.
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 corresponding implementation is: 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.
Question 313
A managed services provider is investigating whether a firewall interface edit or shared object update caused an install warning. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: A
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. This check is decisive because 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.
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: 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.
Modify a safe lab interface description, retrieve the new revision, compare with the baseline and restore an approved version without deleting unrelated ADOM policy objects. That would help test “Use FortiManager device revision history to identify and repair drift”, not the outcome required in this scenario. The relevant acceptance check is: 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.
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: 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.
Question 314
A managed services provider is investigating whether a firewall interface edit or shared object update caused an install warning. Which proposed shortcut most directly risks wrong rollback selection after central and device configuration snapshots are conflated and should therefore be rejected?
Answer & Explanations
Correct answer: B
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: Treat any FortiManager revision number as a universal snapshot of all gateways, policies, objects, administrators and global settings and restore it without checking scope.
Treat any FortiManager revision number as a universal snapshot of all gateways, policies, objects, administrators and global settings and restore it without checking scope. The foreseeable failure is wrong rollback selection after central and device configuration snapshots are conflated. The safer response is: 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.
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: Treat any FortiManager revision number as a universal snapshot of all gateways, policies, objects, administrators and global settings and restore it without checking scope.
Revert an arbitrary old revision without comparing what changed and assume every ADOM policy package and management administrator account must also roll back. That shortcut risks accidental loss of legitimate device changes after treating a device revision as a complete FortiManager restore point. Here the specific shortcut is: Treat any FortiManager revision number as a universal snapshot of all gateways, policies, objects, administrators and global settings and restore it without checking scope.
Question 315
A managed services provider is investigating whether a firewall interface edit or shared object update caused an install warning. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: C
The test would be relevant: 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. But the offered implementation—Compare a managed device's current stored revision with the last approved revision, locate the precise changed settings, and apply a supported restoration or central redeployment after appropriate review.—addresses “Use FortiManager device revision history to identify and repair drift”. The action needed here is: 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.
The action is applicable: 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. But its proposed test—Modify a safe lab interface description, retrieve the new revision, compare with the baseline and restore an approved version without deleting unrelated ADOM policy objects.—addresses “Use FortiManager device revision history to identify and repair drift”. This requirement is confirmed instead by: 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.
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. Confirm it through this 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. 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.
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: 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.
Question 316
A university has both device and ADOM revisions and needs to explain why each is useful for a different configuration recovery action. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: D
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: 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.
The question is set in this situation: A university has both device and ADOM revisions and needs to explain why each is useful for a different configuration recovery action. Compare a managed device's current stored revision with the last approved revision, locate the precise changed settings, and apply a supported restoration or central redeployment after appropriate review. This addresses “Use FortiManager device revision history to identify and repair drift”, where the governing principle is: Device revision history helps reconstruct configuration changes and revert known states, while snapshots are not the same as an ADOM-wide policy/object database revision. The stated case instead calls for: 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.
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: 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.
The question is set in this situation: A university has both device and ADOM revisions and needs to explain why each is useful for a different configuration recovery action. 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. 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. Verify the result with this 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.
Question 317
A university has both device and ADOM revisions and needs to explain why each is useful for a different configuration recovery action. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: C
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: 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 question is set in this situation: A university has both device and ADOM revisions and needs to explain why each is useful for a different configuration recovery action. Device revision history helps reconstruct configuration changes and revert known states, while snapshots are not the same as an ADOM-wide policy/object database revision. That explains “Use FortiManager device revision history to identify and repair drift”, not the mechanism behind the described change. The relevant 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 question is set in this situation: A university has both device and ADOM revisions and needs to explain why each is useful for a different configuration recovery action. 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 corresponding implementation is: 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.
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: 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.
Question 318
A university has both device and ADOM revisions and needs to explain why each is useful for a different configuration recovery action. After implementing this change—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.—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: 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.
The question is set in this situation: A university has both device and ADOM revisions and needs to explain why each is useful for a different configuration recovery action. 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. This check is decisive because 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.
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: 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.
The question is set in this situation: A university has both device and ADOM revisions and needs to explain why each is useful for a different configuration recovery action. Modify a safe lab interface description, retrieve the new revision, compare with the baseline and restore an approved version without deleting unrelated ADOM policy objects. That would help test “Use FortiManager device revision history to identify and repair drift”, not the outcome required in this scenario. The relevant acceptance check is: 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.
Question 319
A university has both device and ADOM revisions and needs to explain why each is useful for a different configuration recovery action. Which proposed shortcut most directly risks wrong rollback selection after central and device configuration snapshots are conflated and should therefore be rejected?
Answer & Explanations
Correct answer: A
The question is set in this situation: A university has both device and ADOM revisions and needs to explain why each is useful for a different configuration recovery action. Treat any FortiManager revision number as a universal snapshot of all gateways, policies, objects, administrators and global settings and restore it without checking scope. The foreseeable failure is wrong rollback selection after central and device configuration snapshots are conflated. The safer response is: 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.
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: Treat any FortiManager revision number as a universal snapshot of all gateways, policies, objects, administrators and global settings and restore it without checking scope.
The question is set in this situation: A university has both device and ADOM revisions and needs to explain why each is useful for a different configuration recovery action. Revert an arbitrary old revision without comparing what changed and assume every ADOM policy package and management administrator account must also roll back. That shortcut risks accidental loss of legitimate device changes after treating a device revision as a complete FortiManager restore point. Here the specific shortcut is: Treat any FortiManager revision number as a universal snapshot of all gateways, policies, objects, administrators and global settings and restore it without checking scope.
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: Treat any FortiManager revision number as a universal snapshot of all gateways, policies, objects, administrators and global settings and restore it without checking scope.
Question 320
A university has both device and ADOM revisions and needs to explain why each is useful for a different configuration recovery action. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: D
The action is applicable: 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. But its proposed test—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.—addresses “Retrieve the running FortiGate configuration to populate a new FortiManager revision”. This requirement is confirmed instead by: 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.
The test would be relevant: 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. But the offered implementation—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.—addresses “Retrieve the running FortiGate configuration to populate a new FortiManager revision”. The action needed here is: 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 action/test pair addresses “Use FortiManager device revision history to identify and repair drift”. Compare a managed device's current stored revision with the last approved revision, locate the precise changed settings, and apply a supported restoration or central redeployment after appropriate review. Modify a safe lab interface description, retrieve the new revision, compare with the baseline and restore an approved version without deleting unrelated ADOM policy objects. The case instead calls for: 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.
The question is set in this situation: A university has both device and ADOM revisions and needs to explain why each is useful for a different configuration recovery action. 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. Confirm it through this 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. 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.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- 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)
- 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)