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 33

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?

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

Answer & Explanations

Correct answer: D

A.

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.

B.

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.

C.

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.

D.

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.

Question 321

A healthcare gateway has unexpected DNS settings but also received an authorized emergency route, so operations must avoid reversing both changes together. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

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

A.

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

B.

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

C.

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

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. 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. Verify the result with this test: Compare two stored revisions for a lab device with both an intentional description edit and a needed route fix, verify the cause and restore only an approved baseline where appropriate.

Question 322

A healthcare gateway has unexpected DNS settings but also received an authorized emergency route, so operations must avoid reversing both changes together. The engineer proposes the following change: 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. Which mechanism explains why it works?

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

A.

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 corresponding implementation is: Open FortiManager's device revision comparison for an affected FortiGate, identify only the business-relevant lines that diverge, and choose a reviewed restoration rather than reverting all device settings automatically.

B.

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

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. That explains “Use FortiManager device revision history to identify and repair drift”, not the mechanism behind the described change. The relevant 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.

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. That explains “Retrieve the running FortiGate configuration to populate a new FortiManager revision”, not the mechanism behind the described change. The relevant 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.

Question 323

A healthcare gateway has unexpected DNS settings but also received an authorized emergency route, so operations must avoid reversing both changes together. After implementing this change—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.—which test most directly validates its intended outcome?

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

A.

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

B.

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

C.

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

D.

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: Compare two stored revisions for a lab device with both an intentional description edit and a needed route fix, verify the cause and restore only an approved baseline where appropriate.

Question 324

A healthcare gateway has unexpected DNS settings but also received an authorized emergency route, so operations must avoid reversing both changes together. Which proposed shortcut most directly risks branch connectivity loss after restoring an obsolete configuration in response to one isolated drift symptom and should therefore be rejected?

  1. 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.
  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. Revert an arbitrary old revision without comparing what changed and assume every ADOM policy package and management administrator account must also roll back.
  4. Press Retrieve Config after an unreviewed local change and declare all modifications approved corporate policy merely because the management database now contains them.

Answer & Explanations

Correct answer: B

A.

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

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. The foreseeable failure is branch connectivity loss after restoring an obsolete configuration in response to one isolated drift symptom. The safer response is: Open FortiManager's device revision comparison for an affected FortiGate, identify only the business-relevant lines that diverge, and choose a reviewed restoration rather than reverting all device settings automatically.

C.

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

D.

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

Question 325

A healthcare gateway has unexpected DNS settings but also received an authorized emergency route, so operations must avoid reversing both changes together. 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: 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: 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. 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.
  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: 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: B

A.

The test would be relevant: Compare two stored revisions for a lab device with both an intentional description edit and a needed route fix, verify the cause and restore only an approved baseline where appropriate. But the offered implementation—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: 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.

B.

Open FortiManager's device revision comparison for an affected FortiGate, identify only the business-relevant lines that diverge, and choose a reviewed restoration rather than reverting all device settings automatically. Confirm it through this test: Compare two stored revisions for a lab device with both an intentional description edit and a needed route fix, verify the cause and restore only an approved baseline where appropriate. Historical revisions provide evidence of particular changes, but reversing unrelated authorized edits can introduce new outages; a selective diagnosis is essential before invoking a broad revert operation.

C.

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

D.

The action is applicable: Open FortiManager's device revision comparison for an affected FortiGate, identify only the business-relevant lines that diverge, and choose a reviewed restoration rather than reverting all device settings automatically. But its proposed test—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: Compare two stored revisions for a lab device with both an intentional description edit and a needed route fix, verify the cause and restore only an approved baseline where appropriate.

Question 326

A retailer's branch device revision history contains several updates and the change board needs to isolate which single setting explains the reported failure. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. Review FortiManager's import wizard report for existing gateway policies, interfaces and dependent objects, resolve missing references and decide whether to preserve or replace local configuration before installing central changes.
  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. 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.
  4. 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.

Answer & Explanations

Correct answer: C

A.

Review FortiManager's import wizard report for existing gateway policies, interfaces and dependent objects, resolve missing references and decide whether to preserve or replace local configuration before installing central changes. This addresses “Reconcile an imported configuration report before first FortiManager policy installation”, where the governing principle is: Import moves a snapshot of current FortiGate policy into central management scope; unreadable objects or interface mappings can produce later install errors when local and intended central databases differ. The stated case instead calls for: Open FortiManager's device revision comparison for an affected FortiGate, identify only the business-relevant lines that diverge, and choose a reviewed restoration rather than reverting all device settings automatically.

B.

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

C.

The question is set in this situation: A retailer's branch device revision history contains several updates and the change board needs to isolate which single setting explains the reported failure. Open FortiManager's device revision comparison for an affected FortiGate, identify only the business-relevant lines that diverge, and choose a reviewed restoration rather than reverting all device settings automatically. 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. Verify the result with this test: Compare two stored revisions for a lab device with both an intentional description edit and a needed route fix, verify the cause and restore only an approved baseline where appropriate.

D.

The question is set in this situation: A retailer's branch device revision history contains several updates and the change board needs to isolate which single setting explains the reported failure. 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: 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.

Question 327

A retailer's branch device revision history contains several updates and the change board needs to isolate which single setting explains the reported failure. The engineer proposes the following change: 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. Which mechanism explains why it works?

  1. 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.
  2. 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.
  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. Import moves a snapshot of current FortiGate policy into central management scope; unreadable objects or interface mappings can produce later install errors when local and intended central databases differ.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: A retailer's branch device revision history contains several updates and the change board needs to isolate which single setting explains the reported failure. 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 corresponding implementation is: Open FortiManager's device revision comparison for an affected FortiGate, identify only the business-relevant lines that diverge, and choose a reviewed restoration rather than reverting all device settings automatically.

B.

The question is set in this situation: A retailer's branch device revision history contains several updates and the change board needs to isolate which single setting explains the reported failure. 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: 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.

C.

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

D.

Import moves a snapshot of current FortiGate policy into central management scope; unreadable objects or interface mappings can produce later install errors when local and intended central databases differ. That explains “Reconcile an imported configuration report before first FortiManager policy installation”, not the mechanism behind the described change. The relevant 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.

Question 328

A retailer's branch device revision history contains several updates and the change board needs to isolate which single setting explains the reported failure. After implementing this change—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.—which test most directly validates its intended outcome?

  1. Import a staging gateway with a known local rule and custom address object, compare the central package and mappings with its running state, and record a reviewed no-surprise install plan.
  2. 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.
  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. 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: D

A.

Import a staging gateway with a known local rule and custom address object, compare the central package and mappings with its running state, and record a reviewed no-surprise install plan. That would help test “Reconcile an imported configuration report before first FortiManager policy installation”, not the outcome required in this scenario. The relevant acceptance check is: 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.

B.

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

C.

The question is set in this situation: A retailer's branch device revision history contains several updates and the change board needs to isolate which single setting explains the reported failure. 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: 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.

D.

The question is set in this situation: A retailer's branch device revision history contains several updates and the change board needs to isolate which single setting explains the reported failure. 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. This check is decisive because 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.

Question 329

A retailer's branch device revision history contains several updates and the change board needs to isolate which single setting explains the reported failure. Which proposed shortcut most directly risks branch connectivity loss after restoring an obsolete configuration in response to one isolated drift symptom and should therefore be rejected?

  1. Install an empty default FortiManager package over a production FortiGate immediately after registration without checking which live rules the import wizard recognized.
  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. Press Retrieve Config after an unreviewed local change and declare all modifications approved corporate policy merely because the management database now contains them.
  4. 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.

Answer & Explanations

Correct answer: D

A.

Install an empty default FortiManager package over a production FortiGate immediately after registration without checking which live rules the import wizard recognized. That shortcut risks unexpected disruption to permitted traffic after uncontrolled replacement of existing firewall rules during onboarding. Here the specific shortcut is: 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.

B.

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

C.

The question is set in this situation: A retailer's branch device revision history contains several updates and the change board needs to isolate which single setting explains the reported failure. 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: 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.

D.

The question is set in this situation: A retailer's branch device revision history contains several updates and the change board needs to isolate which single setting explains the reported failure. 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. The foreseeable failure is branch connectivity loss after restoring an obsolete configuration in response to one isolated drift symptom. The safer response is: Open FortiManager's device revision comparison for an affected FortiGate, identify only the business-relevant lines that diverge, and choose a reviewed restoration rather than reverting all device settings automatically.

Question 330

A retailer's branch device revision history contains several updates and the change board needs to isolate which single setting explains the reported failure. Which combined implementation and verification plan is the best match for this workload?

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

This action/test pair addresses “Retrieve the running FortiGate configuration to populate a new FortiManager revision”. Use the supported Retrieve Config operation for an approved device and compare the retrieved snapshot with the existing device database and known revision history before deciding whether to adopt differences. Change a harmless test setting directly on a staging FortiGate, retrieve configuration in FortiManager, inspect the revised record and document whether to accept or revert the local change. The case instead calls for: Open FortiManager's device revision comparison for an affected FortiGate, identify only the business-relevant lines that diverge, and choose a reviewed restoration rather than reverting all device settings automatically.

B.

The question is set in this situation: A retailer's branch device revision history contains several updates and the change board needs to isolate which single setting explains the reported failure. Open FortiManager's device revision comparison for an affected FortiGate, identify only the business-relevant lines that diverge, and choose a reviewed restoration rather than reverting all device settings automatically. Confirm it through this test: Compare two stored revisions for a lab device with both an intentional description edit and a needed route fix, verify the cause and restore only an approved baseline where appropriate. Historical revisions provide evidence of particular changes, but reversing unrelated authorized edits can introduce new outages; a selective diagnosis is essential before invoking a broad revert operation.

C.

The test would be relevant: Compare two stored revisions for a lab device with both an intentional description edit and a needed route fix, verify the cause and restore only an approved baseline where appropriate. But the offered implementation—When FortiManager reports a device configuration status of modified or out of sync, compare the central device database, last retrieved revision and actual FortiGate state before deciding whether to retrieve or reinstall.—addresses “Reconcile device database synchronization status with live FortiGate changes”. The action needed here is: Open FortiManager's device revision comparison for an affected FortiGate, identify only the business-relevant lines that diverge, and choose a reviewed restoration rather than reverting all device settings automatically.

D.

The action is applicable: Open FortiManager's device revision comparison for an affected FortiGate, identify only the business-relevant lines that diverge, and choose a reviewed restoration rather than reverting all device settings automatically. But its proposed test—Introduce a controlled local configuration change on a test FortiGate, review device status and revision differences, then retrieve or restore as approved and confirm synchronized status.—addresses “Reconcile device database synchronization status with live FortiGate changes”. This requirement is confirmed instead by: Compare two stored revisions for a lab device with both an intentional description edit and a needed route fix, verify the cause and restore only an approved baseline where appropriate.

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