Practice Exams:

Fortinet FCP_FMG_AD-7.6 Dumps

EXAM: Fortinet NSE 5 - FortiManager 7.6 Administrator
Verified By Experts
Premium Bundle
$49.99

FCP_FMG_AD-7.6 Premium ETE File


  • Premium File 62 Questions & Answers
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Fortinet FCP_FMG_AD-7.6 Practice Test 31

Question 300

A university's network group retrieves firewall configuration after a maintenance period and wants to know which differences appeared in revision history. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: 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. Verify: 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.
  2. Implement: 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. Verify: 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.
  3. Implement: 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. Verify: 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.
  4. Implement: 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. Verify: 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.

Answer & Explanations

Correct answer: B

A.

This action/test pair addresses “Reconcile device database synchronization status with live FortiGate changes”. 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. 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 case instead calls for: 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.

B.

The question is set in this situation: A university's network group retrieves firewall configuration after a maintenance period and wants to know which differences appeared in revision history. 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. Confirm it through this 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. 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.

C.

The test would be relevant: 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. 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: 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.

D.

The action is applicable: 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. 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: 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.

Question 301

A financial services team sees an unexpected branch firewall configuration difference and needs to identify when it entered the device database. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. 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.
  2. Check FortiManager platform and license device-management capacity against the expected number of registered devices, confirm supported scale and reserve room for HA clusters and planned growth.
  3. 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.
  4. 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.

Answer & Explanations

Correct answer: A

A.

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. 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. Verify the result with 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.

B.

Check FortiManager platform and license device-management capacity against the expected number of registered devices, confirm supported scale and reserve room for HA clusters and planned growth. This addresses “Account for FortiManager managed device capacity and entitlement before expansion”, where the governing principle is: Central management limits are not removed by renaming devices or adding ADOMs; exceeding supported capacity can block new registrations and make a deployment plan operationally invalid. The stated case instead calls for: 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.

C.

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. This addresses “Reconcile device database synchronization status with live FortiGate changes”, where the governing 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 stated 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.

D.

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: 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 302

A financial services team sees an unexpected branch firewall configuration difference and needs to identify when it entered the device database. The engineer proposes the following change: 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. Which mechanism explains why it works?

  1. 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.
  2. 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.
  3. 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.
  4. Central management limits are not removed by renaming devices or adding ADOMs; exceeding supported capacity can block new registrations and make a deployment plan operationally invalid.

Answer & Explanations

Correct answer: C

A.

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. That explains “Reconcile device database synchronization status with live FortiGate changes”, not the mechanism behind the described change. The relevant 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.

B.

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 revision history helps reconstruct configuration changes and revert known states, while snapshots are not the same as an ADOM-wide policy/object database revision.

C.

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 corresponding implementation 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.

D.

Central management limits are not removed by renaming devices or adding ADOMs; exceeding supported capacity can block new registrations and make a deployment plan operationally invalid. That explains “Account for FortiManager managed device capacity and entitlement before expansion”, not the mechanism behind the described change. The relevant principle is: 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.

Question 303

A financial services team sees an unexpected branch firewall configuration difference and needs to identify when it entered the device database. After implementing this change—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.—which test most directly validates its intended outcome?

  1. 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.
  2. 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.
  3. 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.
  4. Review current managed-device count and licensing on an authorized FortiManager instance, add a lab device within the approved capacity, and document a scale decision before exceeding it.

Answer & Explanations

Correct answer: B

A.

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: 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.

B.

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 check is decisive because 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.

C.

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. That would help test “Reconcile device database synchronization status with live FortiGate changes”, not the outcome required in this scenario. The relevant acceptance check is: 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.

D.

Review current managed-device count and licensing on an authorized FortiManager instance, add a lab device within the approved capacity, and document a scale decision before exceeding it. That would help test “Account for FortiManager managed device capacity and entitlement before expansion”, not the outcome required in this scenario. The relevant acceptance check is: 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.

Question 304

A financial services team sees an unexpected branch firewall configuration difference and needs to identify when it entered the device database. Which proposed shortcut most directly risks accidental loss of legitimate device changes after treating a device revision as a complete FortiManager restore point and should therefore be rejected?

  1. Click the synchronize button repeatedly without comparing intended central values against the changed firewall and assume every live device alteration was safe to adopt.
  2. 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.
  3. Assume creating dozens of ADOMs multiplies a FortiManager appliance's licensed device count indefinitely without purchasing capacity or verifying platform limits.
  4. Revert an arbitrary old revision without comparing what changed and assume every ADOM policy package and management administrator account must also roll back.

Answer & Explanations

Correct answer: D

A.

Click the synchronize button repeatedly without comparing intended central values against the changed firewall and assume every live device alteration was safe to adopt. That shortcut risks persistent unauthorized configuration drift when FortiManager sync status is fixed without understanding which values changed. Here the specific shortcut is: Revert an arbitrary old revision without comparing what changed and assume every ADOM policy package and management administrator account must also roll back.

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: Revert an arbitrary old revision without comparing what changed and assume every ADOM policy package and management administrator account must also roll back.

C.

Assume creating dozens of ADOMs multiplies a FortiManager appliance's licensed device count indefinitely without purchasing capacity or verifying platform limits. That shortcut risks failed enterprise expansion when central device-management scale is assumed unlimited. Here the specific shortcut is: Revert an arbitrary old revision without comparing what changed and assume every ADOM policy package and management administrator account must also roll back.

D.

Revert an arbitrary old revision without comparing what changed and assume every ADOM policy package and management administrator account must also roll back. The foreseeable failure is accidental loss of legitimate device changes after treating a device revision as a complete FortiManager restore point. The safer response 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.

Question 305

A financial services team sees an unexpected branch firewall configuration difference and needs to identify when it entered the device database. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: 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. Verify: 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.
  2. Implement: 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. Verify: 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.
  3. Implement: 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. Verify: 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.
  4. Implement: 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. Verify: 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.

Answer & Explanations

Correct answer: D

A.

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—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: 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.

B.

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—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: 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.

C.

This action/test pair addresses “Reconcile device database synchronization status with live FortiGate changes”. 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. 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 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.

D.

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.

Question 306

A research institution is planning a targeted FortiGate rollback without rolling back every central object or policy in the ADOM. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. 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.
  2. 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.
  3. 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.
  4. 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.

Answer & Explanations

Correct answer: A

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. 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. Verify the result with 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.

B.

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. 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: 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.

C.

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: 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.

D.

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: 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 307

A research institution is planning a targeted FortiGate rollback without rolling back every central object or policy in the ADOM. The engineer proposes the following change: 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. Which mechanism explains why it works?

  1. 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.
  2. 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.
  3. 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.
  4. 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.

Answer & Explanations

Correct answer: C

A.

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: 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.

B.

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: 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.

C.

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. 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 corresponding implementation 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.

D.

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. 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 revision history helps reconstruct configuration changes and revert known states, while snapshots are not the same as an ADOM-wide policy/object database revision.

Question 308

A research institution is planning a targeted FortiGate rollback without rolling back every central object or policy in the ADOM. After implementing this change—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.—which test most directly validates its intended outcome?

  1. 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.
  2. 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.
  3. 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.
  4. 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.

Answer & Explanations

Correct answer: B

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. 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: 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.

B.

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. 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 check is decisive because 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.

C.

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: 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.

D.

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 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: 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.

Question 309

A research institution is planning a targeted FortiGate rollback without rolling back every central object or policy in the ADOM. Which proposed shortcut most directly risks accidental loss of legitimate device changes after treating a device revision as a complete FortiManager restore point and should therefore be rejected?

  1. 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.
  2. Revert an arbitrary old revision without comparing what changed and assume every ADOM policy package and management administrator account must also roll back.
  3. Mark a script audit successful based solely on the job submission timestamp without examining whether the actual running FortiGate configuration changed.
  4. Treat any FortiManager revision number as a universal snapshot of all gateways, policies, objects, administrators and global settings and restore it without checking scope.

Answer & Explanations

Correct answer: B

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. 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: Revert an arbitrary old revision without comparing what changed and assume every ADOM policy package and management administrator account must also roll back.

B.

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. Revert an arbitrary old revision without comparing what changed and assume every ADOM policy package and management administrator account must also roll back. The foreseeable failure is accidental loss of legitimate device changes after treating a device revision as a complete FortiManager restore point. The safer response 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.

C.

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: Revert an arbitrary old revision without comparing what changed and assume every ADOM policy package and management administrator account must also roll back.

D.

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: Revert an arbitrary old revision without comparing what changed and assume every ADOM policy package and management administrator account must also roll back.

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?

  1. Implement: 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. Verify: 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.
  2. Implement: 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. Verify: 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.
  3. Implement: 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. Verify: 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.
  4. Implement: 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. Verify: 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.

Answer & Explanations

Correct answer: A

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.

B.

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.

C.

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.

D.

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.

Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests