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 44

Question 430

A university network team is diagnosing a stale shared service object and needs to locate whether the difference resides in the ADOM or on a single device. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Configure the intended interface mapping for each target firewall so policy packages referencing normalized logical interfaces resolve to the real supported FortiGate ports at installation. Verify: Preview one branch package targeting a FortiGate with wan1 and another with a differently named uplink, verify mapped interface values and run controlled permitted/denied traffic tests after install.
  2. Implement: Define a suitable dynamic mapping for a centrally shared policy object and configure distinct authorized values per target FortiGate without copying private branch subnets into one universal static object. Verify: Modify a harmless ADOM service object and a separate test device setting, inspect both database views and install only the reviewed policy change while checking the resulting FortiGate state.
  3. Implement: Edit shared firewall policy objects in the proper ADOM object database and separately examine device-specific configuration records, verifying how policy package installation renders the intended settings on a FortiGate. Verify: Modify a harmless ADOM service object and a separate test device setting, inspect both database views and install only the reviewed policy change while checking the resulting FortiGate state.
  4. Implement: Edit shared firewall policy objects in the proper ADOM object database and separately examine device-specific configuration records, verifying how policy package installation renders the intended settings on a FortiGate. Verify: Map a logical internal-network object to two different lab branch subnets, preview the installed package for each FortiGate and verify the generated addresses match the site.

Answer & Explanations

Correct answer: C

A.

This action/test pair addresses “Map normalized FortiManager policy interfaces to differing FortiGate port names”. Configure the intended interface mapping for each target firewall so policy packages referencing normalized logical interfaces resolve to the real supported FortiGate ports at installation. Preview one branch package targeting a FortiGate with wan1 and another with a differently named uplink, verify mapped interface values and run controlled permitted/denied traffic tests after install. The case instead calls for: Edit shared firewall policy objects in the proper ADOM object database and separately examine device-specific configuration records, verifying how policy package installation renders the intended settings on a FortiGate.

B.

The test would be relevant: Modify a harmless ADOM service object and a separate test device setting, inspect both database views and install only the reviewed policy change while checking the resulting FortiGate state. But the offered implementation—Define a suitable dynamic mapping for a centrally shared policy object and configure distinct authorized values per target FortiGate without copying private branch subnets into one universal static object.—addresses “Use FortiManager dynamic objects for per-device address differences”. The action needed here is: Edit shared firewall policy objects in the proper ADOM object database and separately examine device-specific configuration records, verifying how policy package installation renders the intended settings on a FortiGate.

C.

The question is set in this situation: A university network team is diagnosing a stale shared service object and needs to locate whether the difference resides in the ADOM or on a single device. Edit shared firewall policy objects in the proper ADOM object database and separately examine device-specific configuration records, verifying how policy package installation renders the intended settings on a FortiGate. Confirm it through this test: Modify a harmless ADOM service object and a separate test device setting, inspect both database views and install only the reviewed policy change while checking the resulting FortiGate state. ADOM objects and packages express shared policy intent, while device-level databases store target-specific configuration state; a change to one database need not update the live device until installation or retrieval occurs.

D.

The action is applicable: Edit shared firewall policy objects in the proper ADOM object database and separately examine device-specific configuration records, verifying how policy package installation renders the intended settings on a FortiGate. But its proposed test—Map a logical internal-network object to two different lab branch subnets, preview the installed package for each FortiGate and verify the generated addresses match the site.—addresses “Use FortiManager dynamic objects for per-device address differences”. This requirement is confirmed instead by: Modify a harmless ADOM service object and a separate test device setting, inspect both database views and install only the reviewed policy change while checking the resulting FortiGate state.

Question 431

A financial institution is consolidating dozens of FortiManager policy packages and its change board requires an ADOM recovery checkpoint. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path.
  2. Inspect FortiManager's package status, installation logs and managed FortiGate revision to confirm the intended policy actually reached the correct target, and investigate any out-of-sync status before closing the change ticket.
  3. After restoring or choosing an approved FortiManager ADOM revision, preview and explicitly install the corresponding policy package to affected target devices and verify their actual enforced revision.
  4. Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified.

Answer & Explanations

Correct answer: A

A.

Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path. An ADOM revision records central policy/object state at a point in time; a device configuration revision for one FortiGate cannot replace the broader ADOM snapshot used to recover shared packages. Verify the result with this test: Save an ADOM revision, alter a harmless shared object and package order in a lab, inspect the differences and restore only an approved central baseline without affecting unrelated device-only settings.

B.

Inspect FortiManager's package status, installation logs and managed FortiGate revision to confirm the intended policy actually reached the correct target, and investigate any out-of-sync status before closing the change ticket. This addresses “Confirm FortiManager package status after a successful installation”, where the governing principle is: A successful central submission is not proof every gateway accepted and enforced the generated policy; per-device execution and database synchronization states provide necessary evidence. The stated case instead calls for: Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path.

C.

After restoring or choosing an approved FortiManager ADOM revision, preview and explicitly install the corresponding policy package to affected target devices and verify their actual enforced revision. This addresses “Reconcile ADOM revision recovery with package installation state on managed FortiGates”, where the governing principle is: An ADOM revision changes central database content; existing FortiGates do not automatically roll back running policies merely because an older management snapshot was selected. The stated case instead calls for: Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path.

D.

Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified. This addresses “Compare two FortiManager ADOM revisions to isolate a shared object change”, where the governing principle is: Comparing central snapshots distinguishes authorized changes from accidental object drift; blindly restoring an older snapshot may erase independent legitimate edits made later in the same ADOM. The stated case instead calls for: Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path.

Question 432

A financial institution is consolidating dozens of FortiManager policy packages and its change board requires an ADOM recovery checkpoint. The engineer proposes the following change: Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path. Which mechanism explains why it works?

  1. A successful central submission is not proof every gateway accepted and enforced the generated policy; per-device execution and database synchronization states provide necessary evidence.
  2. An ADOM revision records central policy/object state at a point in time; a device configuration revision for one FortiGate cannot replace the broader ADOM snapshot used to recover shared packages.
  3. An ADOM revision changes central database content; existing FortiGates do not automatically roll back running policies merely because an older management snapshot was selected.
  4. Comparing central snapshots distinguishes authorized changes from accidental object drift; blindly restoring an older snapshot may erase independent legitimate edits made later in the same ADOM.

Answer & Explanations

Correct answer: B

A.

A successful central submission is not proof every gateway accepted and enforced the generated policy; per-device execution and database synchronization states provide necessary evidence. That explains “Confirm FortiManager package status after a successful installation”, not the mechanism behind the described change. The relevant principle is: An ADOM revision records central policy/object state at a point in time; a device configuration revision for one FortiGate cannot replace the broader ADOM snapshot used to recover shared packages.

B.

An ADOM revision records central policy/object state at a point in time; a device configuration revision for one FortiGate cannot replace the broader ADOM snapshot used to recover shared packages. The corresponding implementation is: Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path.

C.

An ADOM revision changes central database content; existing FortiGates do not automatically roll back running policies merely because an older management snapshot was selected. That explains “Reconcile ADOM revision recovery with package installation state on managed FortiGates”, not the mechanism behind the described change. The relevant principle is: An ADOM revision records central policy/object state at a point in time; a device configuration revision for one FortiGate cannot replace the broader ADOM snapshot used to recover shared packages.

D.

Comparing central snapshots distinguishes authorized changes from accidental object drift; blindly restoring an older snapshot may erase independent legitimate edits made later in the same ADOM. That explains “Compare two FortiManager ADOM revisions to isolate a shared object change”, not the mechanism behind the described change. The relevant principle is: An ADOM revision records central policy/object state at a point in time; a device configuration revision for one FortiGate cannot replace the broader ADOM snapshot used to recover shared packages.

Question 433

A financial institution is consolidating dozens of FortiManager policy packages and its change board requires an ADOM recovery checkpoint. After implementing this change—Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path.—which test most directly validates its intended outcome?

  1. Install a harmless lab policy to two gateways, disconnect one during the task, verify only one successful result and reconcile the failed target after connectivity returns.
  2. Save an ADOM revision, alter a harmless shared object and package order in a lab, inspect the differences and restore only an approved central baseline without affecting unrelated device-only settings.
  3. Produce two lab ADOM revisions with separate service-object and rule-order edits, compare them and validate one selected rollback while keeping the unrelated approved change.
  4. Restore a test ADOM revision, confirm the central package version changed, inspect a staged FortiGate's still-running old policy, then install and verify the approved restored package.

Answer & Explanations

Correct answer: B

A.

Install a harmless lab policy to two gateways, disconnect one during the task, verify only one successful result and reconcile the failed target after connectivity returns. That would help test “Confirm FortiManager package status after a successful installation”, not the outcome required in this scenario. The relevant acceptance check is: Save an ADOM revision, alter a harmless shared object and package order in a lab, inspect the differences and restore only an approved central baseline without affecting unrelated device-only settings.

B.

Save an ADOM revision, alter a harmless shared object and package order in a lab, inspect the differences and restore only an approved central baseline without affecting unrelated device-only settings. This check is decisive because an ADOM revision records central policy/object state at a point in time; a device configuration revision for one FortiGate cannot replace the broader ADOM snapshot used to recover shared packages.

C.

Produce two lab ADOM revisions with separate service-object and rule-order edits, compare them and validate one selected rollback while keeping the unrelated approved change. That would help test “Compare two FortiManager ADOM revisions to isolate a shared object change”, not the outcome required in this scenario. The relevant acceptance check is: Save an ADOM revision, alter a harmless shared object and package order in a lab, inspect the differences and restore only an approved central baseline without affecting unrelated device-only settings.

D.

Restore a test ADOM revision, confirm the central package version changed, inspect a staged FortiGate's still-running old policy, then install and verify the approved restored package. That would help test “Reconcile ADOM revision recovery with package installation state on managed FortiGates”, not the outcome required in this scenario. The relevant acceptance check is: Save an ADOM revision, alter a harmless shared object and package order in a lab, inspect the differences and restore only an approved central baseline without affecting unrelated device-only settings.

Question 434

A financial institution is consolidating dozens of FortiManager policy packages and its change board requires an ADOM recovery checkpoint. Which proposed shortcut most directly risks permanent loss of shared policy context after an ADOM-wide change without an appropriate central revision and should therefore be rejected?

  1. Before restructuring a customer ADOM delete its policy packages and count on a single branch FortiGate revision history to recreate every central object automatically.
  2. Restore the first-ever ADOM revision whenever one object is wrong, without inspecting what valid subsequent business rules and device assignments will be removed.
  3. Restore a previous ADOM revision and report every gateway instantly rolled back even though no installation tasks or device policy checks were performed.
  4. Close a change ticket after the Install Wizard task is queued and report all customer gateways compliant without checking per-device success and installed revision.

Answer & Explanations

Correct answer: A

A.

Before restructuring a customer ADOM delete its policy packages and count on a single branch FortiGate revision history to recreate every central object automatically. The foreseeable failure is permanent loss of shared policy context after an ADOM-wide change without an appropriate central revision. The safer response is: Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path.

B.

Restore the first-ever ADOM revision whenever one object is wrong, without inspecting what valid subsequent business rules and device assignments will be removed. That shortcut risks unnecessary interruption after a broad central rollback erases valid later policy changes. Here the specific shortcut is: Before restructuring a customer ADOM delete its policy packages and count on a single branch FortiGate revision history to recreate every central object automatically.

C.

Restore a previous ADOM revision and report every gateway instantly rolled back even though no installation tasks or device policy checks were performed. That shortcut risks incorrect change records after management database restoration is confused with actual firewall enforcement rollback. Here the specific shortcut is: Before restructuring a customer ADOM delete its policy packages and count on a single branch FortiGate revision history to recreate every central object automatically.

D.

Close a change ticket after the Install Wizard task is queued and report all customer gateways compliant without checking per-device success and installed revision. That shortcut risks false audit evidence and inconsistent network filtering after installation task state is mistaken for device enforcement. Here the specific shortcut is: Before restructuring a customer ADOM delete its policy packages and count on a single branch FortiGate revision history to recreate every central object automatically.

Question 435

A financial institution is consolidating dozens of FortiManager policy packages and its change board requires an ADOM recovery checkpoint. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: After restoring or choosing an approved FortiManager ADOM revision, preview and explicitly install the corresponding policy package to affected target devices and verify their actual enforced revision. Verify: Save an ADOM revision, alter a harmless shared object and package order in a lab, inspect the differences and restore only an approved central baseline without affecting unrelated device-only settings.
  2. Implement: Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path. Verify: Restore a test ADOM revision, confirm the central package version changed, inspect a staged FortiGate's still-running old policy, then install and verify the approved restored package.
  3. Implement: Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path. Verify: Save an ADOM revision, alter a harmless shared object and package order in a lab, inspect the differences and restore only an approved central baseline without affecting unrelated device-only settings.
  4. Implement: Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified. Verify: Produce two lab ADOM revisions with separate service-object and rule-order edits, compare them and validate one selected rollback while keeping the unrelated approved change.

Answer & Explanations

Correct answer: C

A.

The test would be relevant: Save an ADOM revision, alter a harmless shared object and package order in a lab, inspect the differences and restore only an approved central baseline without affecting unrelated device-only settings. But the offered implementation—After restoring or choosing an approved FortiManager ADOM revision, preview and explicitly install the corresponding policy package to affected target devices and verify their actual enforced revision.—addresses “Reconcile ADOM revision recovery with package installation state on managed FortiGates”. The action needed here is: Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path.

B.

The action is applicable: Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path. But its proposed test—Restore a test ADOM revision, confirm the central package version changed, inspect a staged FortiGate's still-running old policy, then install and verify the approved restored package.—addresses “Reconcile ADOM revision recovery with package installation state on managed FortiGates”. This requirement is confirmed instead by: Save an ADOM revision, alter a harmless shared object and package order in a lab, inspect the differences and restore only an approved central baseline without affecting unrelated device-only settings.

C.

Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path. Confirm it through this test: Save an ADOM revision, alter a harmless shared object and package order in a lab, inspect the differences and restore only an approved central baseline without affecting unrelated device-only settings. An ADOM revision records central policy/object state at a point in time; a device configuration revision for one FortiGate cannot replace the broader ADOM snapshot used to recover shared packages.

D.

This action/test pair addresses “Compare two FortiManager ADOM revisions to isolate a shared object change”. Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified. Produce two lab ADOM revisions with separate service-object and rule-order edits, compare them and validate one selected rollback while keeping the unrelated approved change. The case instead calls for: Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path.

Question 436

An MSP must reverse a widespread shared object rename without restoring unrelated local FortiGate interface changes. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. After restoring or choosing an approved FortiManager ADOM revision, preview and explicitly install the corresponding policy package to affected target devices and verify their actual enforced revision.
  2. Use FortiManager's supported object usage and duplicate analysis to identify candidates, verify all policy references and the intended ADOM scope, then remove or consolidate only approved items.
  3. Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified.
  4. Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path.

Answer & Explanations

Correct answer: D

A.

The question is set in this situation: An MSP must reverse a widespread shared object rename without restoring unrelated local FortiGate interface changes. After restoring or choosing an approved FortiManager ADOM revision, preview and explicitly install the corresponding policy package to affected target devices and verify their actual enforced revision. This addresses “Reconcile ADOM revision recovery with package installation state on managed FortiGates”, where the governing principle is: An ADOM revision changes central database content; existing FortiGates do not automatically roll back running policies merely because an older management snapshot was selected. The stated case instead calls for: Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path.

B.

Use FortiManager's supported object usage and duplicate analysis to identify candidates, verify all policy references and the intended ADOM scope, then remove or consolidate only approved items. This addresses “Detect unused and duplicate FortiManager objects before policy cleanup”, where the governing principle is: An unused or duplicate-looking object may still matter to another policy package or device-specific mapping; visibility into references helps avoid deleting a dependency needed for installation. The stated case instead calls for: Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path.

C.

The question is set in this situation: An MSP must reverse a widespread shared object rename without restoring unrelated local FortiGate interface changes. Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified. This addresses “Compare two FortiManager ADOM revisions to isolate a shared object change”, where the governing principle is: Comparing central snapshots distinguishes authorized changes from accidental object drift; blindly restoring an older snapshot may erase independent legitimate edits made later in the same ADOM. The stated case instead calls for: Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path.

D.

The question is set in this situation: An MSP must reverse a widespread shared object rename without restoring unrelated local FortiGate interface changes. Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path. An ADOM revision records central policy/object state at a point in time; a device configuration revision for one FortiGate cannot replace the broader ADOM snapshot used to recover shared packages. Verify the result with this test: Save an ADOM revision, alter a harmless shared object and package order in a lab, inspect the differences and restore only an approved central baseline without affecting unrelated device-only settings.

Question 437

An MSP must reverse a widespread shared object rename without restoring unrelated local FortiGate interface changes. The engineer proposes the following change: Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path. Which mechanism explains why it works?

  1. An ADOM revision changes central database content; existing FortiGates do not automatically roll back running policies merely because an older management snapshot was selected.
  2. An unused or duplicate-looking object may still matter to another policy package or device-specific mapping; visibility into references helps avoid deleting a dependency needed for installation.
  3. An ADOM revision records central policy/object state at a point in time; a device configuration revision for one FortiGate cannot replace the broader ADOM snapshot used to recover shared packages.
  4. Comparing central snapshots distinguishes authorized changes from accidental object drift; blindly restoring an older snapshot may erase independent legitimate edits made later in the same ADOM.

Answer & Explanations

Correct answer: C

A.

The question is set in this situation: An MSP must reverse a widespread shared object rename without restoring unrelated local FortiGate interface changes. An ADOM revision changes central database content; existing FortiGates do not automatically roll back running policies merely because an older management snapshot was selected. That explains “Reconcile ADOM revision recovery with package installation state on managed FortiGates”, not the mechanism behind the described change. The relevant principle is: An ADOM revision records central policy/object state at a point in time; a device configuration revision for one FortiGate cannot replace the broader ADOM snapshot used to recover shared packages.

B.

An unused or duplicate-looking object may still matter to another policy package or device-specific mapping; visibility into references helps avoid deleting a dependency needed for installation. That explains “Detect unused and duplicate FortiManager objects before policy cleanup”, not the mechanism behind the described change. The relevant principle is: An ADOM revision records central policy/object state at a point in time; a device configuration revision for one FortiGate cannot replace the broader ADOM snapshot used to recover shared packages.

C.

The question is set in this situation: An MSP must reverse a widespread shared object rename without restoring unrelated local FortiGate interface changes. An ADOM revision records central policy/object state at a point in time; a device configuration revision for one FortiGate cannot replace the broader ADOM snapshot used to recover shared packages. The corresponding implementation is: Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path.

D.

The question is set in this situation: An MSP must reverse a widespread shared object rename without restoring unrelated local FortiGate interface changes. Comparing central snapshots distinguishes authorized changes from accidental object drift; blindly restoring an older snapshot may erase independent legitimate edits made later in the same ADOM. That explains “Compare two FortiManager ADOM revisions to isolate a shared object change”, not the mechanism behind the described change. The relevant principle is: An ADOM revision records central policy/object state at a point in time; a device configuration revision for one FortiGate cannot replace the broader ADOM snapshot used to recover shared packages.

Question 438

An MSP must reverse a widespread shared object rename without restoring unrelated local FortiGate interface changes. After implementing this change—Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path.—which test most directly validates its intended outcome?

  1. In a disposable ADOM create two equal test address objects and an actually referenced third, inspect usage and duplicate views, then confirm deleting the approved unused one does not break validation.
  2. Restore a test ADOM revision, confirm the central package version changed, inspect a staged FortiGate's still-running old policy, then install and verify the approved restored package.
  3. Produce two lab ADOM revisions with separate service-object and rule-order edits, compare them and validate one selected rollback while keeping the unrelated approved change.
  4. Save an ADOM revision, alter a harmless shared object and package order in a lab, inspect the differences and restore only an approved central baseline without affecting unrelated device-only settings.

Answer & Explanations

Correct answer: D

A.

In a disposable ADOM create two equal test address objects and an actually referenced third, inspect usage and duplicate views, then confirm deleting the approved unused one does not break validation. That would help test “Detect unused and duplicate FortiManager objects before policy cleanup”, not the outcome required in this scenario. The relevant acceptance check is: Save an ADOM revision, alter a harmless shared object and package order in a lab, inspect the differences and restore only an approved central baseline without affecting unrelated device-only settings.

B.

The question is set in this situation: An MSP must reverse a widespread shared object rename without restoring unrelated local FortiGate interface changes. Restore a test ADOM revision, confirm the central package version changed, inspect a staged FortiGate's still-running old policy, then install and verify the approved restored package. That would help test “Reconcile ADOM revision recovery with package installation state on managed FortiGates”, not the outcome required in this scenario. The relevant acceptance check is: Save an ADOM revision, alter a harmless shared object and package order in a lab, inspect the differences and restore only an approved central baseline without affecting unrelated device-only settings.

C.

The question is set in this situation: An MSP must reverse a widespread shared object rename without restoring unrelated local FortiGate interface changes. Produce two lab ADOM revisions with separate service-object and rule-order edits, compare them and validate one selected rollback while keeping the unrelated approved change. That would help test “Compare two FortiManager ADOM revisions to isolate a shared object change”, not the outcome required in this scenario. The relevant acceptance check is: Save an ADOM revision, alter a harmless shared object and package order in a lab, inspect the differences and restore only an approved central baseline without affecting unrelated device-only settings.

D.

The question is set in this situation: An MSP must reverse a widespread shared object rename without restoring unrelated local FortiGate interface changes. Save an ADOM revision, alter a harmless shared object and package order in a lab, inspect the differences and restore only an approved central baseline without affecting unrelated device-only settings. This check is decisive because an ADOM revision records central policy/object state at a point in time; a device configuration revision for one FortiGate cannot replace the broader ADOM snapshot used to recover shared packages.

Question 439

An MSP must reverse a widespread shared object rename without restoring unrelated local FortiGate interface changes. Which proposed shortcut most directly risks permanent loss of shared policy context after an ADOM-wide change without an appropriate central revision and should therefore be rejected?

  1. Restore a previous ADOM revision and report every gateway instantly rolled back even though no installation tasks or device policy checks were performed.
  2. Before restructuring a customer ADOM delete its policy packages and count on a single branch FortiGate revision history to recreate every central object automatically.
  3. Restore the first-ever ADOM revision whenever one object is wrong, without inspecting what valid subsequent business rules and device assignments will be removed.
  4. Delete every object sharing an IP subnet because a naming report flags duplicates, without inspecting security policy, dynamic mappings or template dependencies.

Answer & Explanations

Correct answer: B

A.

The question is set in this situation: An MSP must reverse a widespread shared object rename without restoring unrelated local FortiGate interface changes. Restore a previous ADOM revision and report every gateway instantly rolled back even though no installation tasks or device policy checks were performed. That shortcut risks incorrect change records after management database restoration is confused with actual firewall enforcement rollback. Here the specific shortcut is: Before restructuring a customer ADOM delete its policy packages and count on a single branch FortiGate revision history to recreate every central object automatically.

B.

The question is set in this situation: An MSP must reverse a widespread shared object rename without restoring unrelated local FortiGate interface changes. Before restructuring a customer ADOM delete its policy packages and count on a single branch FortiGate revision history to recreate every central object automatically. The foreseeable failure is permanent loss of shared policy context after an ADOM-wide change without an appropriate central revision. The safer response is: Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path.

C.

The question is set in this situation: An MSP must reverse a widespread shared object rename without restoring unrelated local FortiGate interface changes. Restore the first-ever ADOM revision whenever one object is wrong, without inspecting what valid subsequent business rules and device assignments will be removed. That shortcut risks unnecessary interruption after a broad central rollback erases valid later policy changes. Here the specific shortcut is: Before restructuring a customer ADOM delete its policy packages and count on a single branch FortiGate revision history to recreate every central object automatically.

D.

Delete every object sharing an IP subnet because a naming report flags duplicates, without inspecting security policy, dynamic mappings or template dependencies. That shortcut risks failed installs or changed access decisions after careless cleanup of referenced central policy objects. Here the specific shortcut is: Before restructuring a customer ADOM delete its policy packages and count on a single branch FortiGate revision history to recreate every central object automatically.

Question 440

An MSP must reverse a widespread shared object rename without restoring unrelated local FortiGate interface changes. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path. Verify: Save an ADOM revision, alter a harmless shared object and package order in a lab, inspect the differences and restore only an approved central baseline without affecting unrelated device-only settings.
  2. Implement: Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path. Verify: Produce two lab ADOM revisions with separate service-object and rule-order edits, compare them and validate one selected rollback while keeping the unrelated approved change.
  3. Implement: Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified. Verify: Save an ADOM revision, alter a harmless shared object and package order in a lab, inspect the differences and restore only an approved central baseline without affecting unrelated device-only settings.
  4. Implement: After restoring or choosing an approved FortiManager ADOM revision, preview and explicitly install the corresponding policy package to affected target devices and verify their actual enforced revision. Verify: Restore a test ADOM revision, confirm the central package version changed, inspect a staged FortiGate's still-running old policy, then install and verify the approved restored package.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: An MSP must reverse a widespread shared object rename without restoring unrelated local FortiGate interface changes. Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path. Confirm it through this test: Save an ADOM revision, alter a harmless shared object and package order in a lab, inspect the differences and restore only an approved central baseline without affecting unrelated device-only settings. An ADOM revision records central policy/object state at a point in time; a device configuration revision for one FortiGate cannot replace the broader ADOM snapshot used to recover shared packages.

B.

The action is applicable: Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path. But its proposed test—Produce two lab ADOM revisions with separate service-object and rule-order edits, compare them and validate one selected rollback while keeping the unrelated approved change.—addresses “Compare two FortiManager ADOM revisions to isolate a shared object change”. This requirement is confirmed instead by: Save an ADOM revision, alter a harmless shared object and package order in a lab, inspect the differences and restore only an approved central baseline without affecting unrelated device-only settings.

C.

The test would be relevant: Save an ADOM revision, alter a harmless shared object and package order in a lab, inspect the differences and restore only an approved central baseline without affecting unrelated device-only settings. But the offered implementation—Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified.—addresses “Compare two FortiManager ADOM revisions to isolate a shared object change”. The action needed here is: Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path.

D.

This action/test pair addresses “Reconcile ADOM revision recovery with package installation state on managed FortiGates”. After restoring or choosing an approved FortiManager ADOM revision, preview and explicitly install the corresponding policy package to affected target devices and verify their actual enforced revision. Restore a test ADOM revision, confirm the central package version changed, inspect a staged FortiGate's still-running old policy, then install and verify the approved restored package. The case instead calls for: Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path.

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