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 30

Question 290

A logistics company finds scripts completed but central device status remains out of sync and needs to reconcile the new configuration with FortiManager's databases. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Read the actual FortiManager script task log and device-side command output, identify target authentication, mode or unsupported syntax problems, and rerun only after repairing the demonstrated issue. Verify: 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. Implement: 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. Verify: 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.
  3. Implement: 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. Verify: Trigger a controlled unsupported command on one staging FortiGate, locate the failed command and status in FortiManager task output, correct it and prove a narrow retry succeeds.
  4. Implement: Author a reviewed FortiManager CLI script using syntax compatible with the target FortiOS version, choose explicit devices or a restricted device group, and validate the intended scope before executing. Verify: Run a harmless diagnostic or reversible configuration script on two lab FortiGates, inspect the target list and per-device status, and confirm an unselected gateway has no resulting change.

Answer & Explanations

Correct answer: B

A.

The test would be relevant: Run a harmless staged script, retrieve the affected setting, compare it with a stored before-state and confirm later central policy installation does not unintentionally undo the change. But the offered implementation—Read the actual FortiManager script task log and device-side command output, identify target authentication, mode or unsupported syntax problems, and rerun only after repairing the demonstrated issue.—addresses “Investigate a FortiManager script failure using per-device task results”. The action needed here is: Retrieve or inspect the relevant FortiGate configuration after an authorized script runs, compare the actual setting to the planned state and document any central database reconciliation required.

B.

The question is set in this situation: A logistics company finds scripts completed but central device status remains out of sync and needs to reconcile the new configuration with FortiManager's databases. Retrieve or inspect the relevant FortiGate configuration after an authorized script runs, compare the actual setting to the planned state and document any central database reconciliation required. Confirm it through this test: Run a harmless staged script, retrieve the affected setting, compare it with a stored before-state and confirm later central policy installation does not unintentionally undo the change. The script engine's task result and the gateway's active configuration are separate sources of evidence; manual device-level changes can create differences that require FortiManager database updates or an import.

C.

The action is applicable: Retrieve or inspect the relevant FortiGate configuration after an authorized script runs, compare the actual setting to the planned state and document any central database reconciliation required. But its proposed test—Trigger a controlled unsupported command on one staging FortiGate, locate the failed command and status in FortiManager task output, correct it and prove a narrow retry succeeds.—addresses “Investigate a FortiManager script failure using per-device task results”. This requirement is confirmed instead by: Run a harmless staged script, retrieve the affected setting, compare it with a stored before-state and confirm later central policy installation does not unintentionally undo the change.

D.

This action/test pair addresses “Execute a FortiManager CLI script only on approved FortiGate targets”. Author a reviewed FortiManager CLI script using syntax compatible with the target FortiOS version, choose explicit devices or a restricted device group, and validate the intended scope before executing. Run a harmless diagnostic or reversible configuration script on two lab FortiGates, inspect the target list and per-device status, and confirm an unselected gateway has no resulting change. The case instead calls for: Retrieve or inspect the relevant FortiGate configuration after an authorized script runs, compare the actual setting to the planned state and document any central database reconciliation required.

Question 291

A hospital branch technician changed a device setting locally and the central FortiManager team needs to distinguish observation from approval. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. 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.
  2. Use FortiManager's supported script scheduling and permission workflow to execute approved changes at designated times, accounting for device availability and a rollback or postexecution verification check.
  3. 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.
  4. 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.

Answer & Explanations

Correct answer: C

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

Use FortiManager's supported script scheduling and permission workflow to execute approved changes at designated times, accounting for device availability and a rollback or postexecution verification check. This addresses “Schedule scripts within controlled FortiManager maintenance windows”, where the governing principle is: A scheduled task merely queues central execution; devices may be disconnected or reject commands, so the operator must inspect per-device results rather than infer success from the calendar event. The stated case instead calls for: 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.

C.

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

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

Question 292

A hospital branch technician changed a device setting locally and the central FortiManager team needs to distinguish observation from approval. The engineer proposes the following change: 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. Which mechanism explains why it works?

  1. 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.
  2. 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.
  3. A scheduled task merely queues central execution; devices may be disconnected or reject commands, so the operator must inspect per-device results rather than infer success from the calendar event.
  4. 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.

Answer & Explanations

Correct answer: D

A.

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

B.

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

A scheduled task merely queues central execution; devices may be disconnected or reject commands, so the operator must inspect per-device results rather than infer success from the calendar event. That explains “Schedule scripts within controlled FortiManager maintenance windows”, not the mechanism behind the described change. The relevant principle is: 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.

D.

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

Question 293

A hospital branch technician changed a device setting locally and the central FortiManager team needs to distinguish observation from approval. After implementing this change—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.—which test most directly validates its intended outcome?

  1. Schedule a reversible lab update for a maintenance period, deliberately make one test gateway unavailable, and verify the task records success and failure separately with no silent retries outside approval.
  2. 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. 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.
  4. 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.

Answer & Explanations

Correct answer: B

A.

Schedule a reversible lab update for a maintenance period, deliberately make one test gateway unavailable, and verify the task records success and failure separately with no silent retries outside approval. That would help test “Schedule scripts within controlled FortiManager maintenance windows”, not the outcome required in this scenario. The relevant acceptance check is: 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.

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

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

D.

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

A hospital branch technician changed a device setting locally and the central FortiManager team needs to distinguish observation from approval. Which proposed shortcut most directly risks unauthorized local changes legitimized when retrieved device configuration is mistaken for reviewed intent and should therefore be rejected?

  1. Press Retrieve Config after an unreviewed local change and declare all modifications approved corporate policy merely because the management database now contains them.
  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. Click the synchronize button repeatedly without comparing intended central values against the changed firewall and assume every live device alteration was safe to adopt.
  4. Schedule destructive configuration changes for midnight and declare every remote firewall updated before checking whether the devices were online or the commands completed.

Answer & Explanations

Correct answer: A

A.

Press Retrieve Config after an unreviewed local change and declare all modifications approved corporate policy merely because the management database now contains them. The foreseeable failure is unauthorized local changes legitimized when retrieved device configuration is mistaken for reviewed intent. The safer response 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.

B.

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: Press Retrieve Config after an unreviewed local change and declare all modifications approved corporate policy merely because the management database now contains them.

C.

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: Press Retrieve Config after an unreviewed local change and declare all modifications approved corporate policy merely because the management database now contains them.

D.

Schedule destructive configuration changes for midnight and declare every remote firewall updated before checking whether the devices were online or the commands completed. That shortcut risks unverified fleet-wide drift when FortiManager scheduling is mistaken for confirmed execution. Here the specific shortcut is: Press Retrieve Config after an unreviewed local change and declare all modifications approved corporate policy merely because the management database now contains them.

Question 295

A hospital branch technician changed a device setting locally and the central FortiManager team needs to distinguish observation from approval. Which combined implementation and verification plan is the best match for this workload?

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

Answer & Explanations

Correct answer: D

A.

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

B.

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

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

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.

Question 296

A university's network group retrieves firewall configuration after a maintenance period and wants to know which differences appeared in revision history. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. Use a supported FortiManager model device entry with an approved blueprint and correct serial or authorization data, then bind the physical FortiGate when it comes online and reconcile actual configuration.
  2. 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.
  3. 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.
  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: C

A.

Use a supported FortiManager model device entry with an approved blueprint and correct serial or authorization data, then bind the physical FortiGate when it comes online and reconcile actual configuration. This addresses “Create a model device for a FortiGate not yet physically connected”, where the governing principle is: A model device is a planned representation for preprovisioning and does not prove the future hardware is reachable; matching the real device securely is required before intended settings can be pushed and verified. The stated 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. 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: 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.

C.

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

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

Question 297

A university's network group retrieves firewall configuration after a maintenance period and wants to know which differences appeared in revision history. The engineer proposes the following change: 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. Which mechanism explains why it works?

  1. A model device is a planned representation for preprovisioning and does not prove the future hardware is reachable; matching the real device securely is required before intended settings can be pushed and verified.
  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. 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.
  4. 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.

Answer & Explanations

Correct answer: D

A.

A model device is a planned representation for preprovisioning and does not prove the future hardware is reachable; matching the real device securely is required before intended settings can be pushed and verified. That explains “Create a model device for a FortiGate not yet physically connected”, not the mechanism behind the described change. The relevant 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.

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

D.

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

Question 298

A university's network group retrieves firewall configuration after a maintenance period and wants to know which differences appeared in revision history. After implementing this change—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.—which test most directly validates its intended outcome?

  1. Create a model FortiGate in a lab ADOM, associate a provisioning template, attach a matching simulated device identity, and confirm it transitions to live managed status without unexpected object differences.
  2. 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.
  3. 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. 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.

Answer & Explanations

Correct answer: C

A.

Create a model FortiGate in a lab ADOM, associate a provisioning template, attach a matching simulated device identity, and confirm it transitions to live managed status without unexpected object differences. That would help test “Create a model device for a FortiGate not yet physically connected”, not the outcome required in this scenario. The relevant acceptance check is: 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.

B.

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

C.

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

D.

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

A university's network group retrieves firewall configuration after a maintenance period and wants to know which differences appeared in revision history. Which proposed shortcut most directly risks unauthorized local changes legitimized when retrieved device configuration is mistaken for reviewed intent and should therefore be rejected?

  1. Press Retrieve Config after an unreviewed local change and declare all modifications approved corporate policy merely because the management database now contains them.
  2. Click the synchronize button repeatedly without comparing intended central values against the changed firewall and assume every live device alteration was safe to adopt.
  3. 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.
  4. Record an unverified wildcard model entry and install firewall policies as though its network interfaces and serial number had already been checked against deployed hardware.

Answer & Explanations

Correct answer: A

A.

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. Press Retrieve Config after an unreviewed local change and declare all modifications approved corporate policy merely because the management database now contains them. The foreseeable failure is unauthorized local changes legitimized when retrieved device configuration is mistaken for reviewed intent. The safer response 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.

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. 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: Press Retrieve Config after an unreviewed local change and declare all modifications approved corporate policy merely because the management database now contains them.

C.

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: Press Retrieve Config after an unreviewed local change and declare all modifications approved corporate policy merely because the management database now contains them.

D.

Record an unverified wildcard model entry and install firewall policies as though its network interfaces and serial number had already been checked against deployed hardware. That shortcut risks misapplied branch provisioning when placeholder device identity is mistaken for authenticated installed equipment. Here the specific shortcut is: Press Retrieve Config after an unreviewed local change and declare all modifications approved corporate policy merely because the management database now contains them.

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.

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