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 14

Question 130

A government network center is onboarding new administrators and needs independent individual identities and evidence of their assigned ADOM permissions. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access. Verify: Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records.
  2. Implement: Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory. Verify: Create a benign object and policy revision in a lab ADOM, record protected backup and revision IDs, perform a controlled rollback test and compare prechange objects and policy packages.
  3. Implement: Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access. Verify: Move a lab device with an approved maintenance backup, confirm it appears in the new ADOM, review policy import or reassignment and verify its synchronization and installation status.
  4. Implement: Review device ownership, target ADOM version and object-policy dependencies before moving a registered FortiGate to a different ADOM using the supported FortiManager device-migration procedure. Verify: Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: A government network center is onboarding new administrators and needs independent individual identities and evidence of their assigned ADOM permissions. Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access. Confirm it through this test: Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records. Parallel administrators may have distinct permissions and session state; access to the FortiManager login page does not imply write rights to all ADOMs or protect against edit collisions.

B.

This action/test pair addresses “Restore FortiManager ADOM content after a controlled management change”. Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory. Create a benign object and policy revision in a lab ADOM, record protected backup and revision IDs, perform a controlled rollback test and compare prechange objects and policy packages. The case instead calls for: Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access.

C.

The action is applicable: Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access. But its proposed test—Move a lab device with an approved maintenance backup, confirm it appears in the new ADOM, review policy import or reassignment and verify its synchronization and installation status.—addresses “Move a registered FortiGate between ADOMs through a supported workflow”. This requirement is confirmed instead by: Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records.

D.

The test would be relevant: Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records. But the offered implementation—Review device ownership, target ADOM version and object-policy dependencies before moving a registered FortiGate to a different ADOM using the supported FortiManager device-migration procedure.—addresses “Move a registered FortiGate between ADOMs through a supported workflow”. The action needed here is: Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access.

Question 131

A financial organization schedules an ADOM schema upgrade and requires verifiable database recovery checkpoints before network maintenance begins. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. Set each ADOM to a supported FortiOS compatibility version for its managed devices and plan the official ADOM upgrade or migration path before introducing gateways on newer firmware.
  2. Choose the supported ADOM operation and device modes based on whether central FortiManager will own policy packages or inventory and device settings, then test the intended editing and installation workflow.
  3. Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant.
  4. Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory.

Answer & Explanations

Correct answer: D

A.

Set each ADOM to a supported FortiOS compatibility version for its managed devices and plan the official ADOM upgrade or migration path before introducing gateways on newer firmware. This addresses “Keep ADOM firmware version compatibility aligned with managed FortiGate releases”, where the governing principle is: FortiManager's ADOM data schema and features depend on the selected supported version; moving a FortiGate to newer FortiOS without checking ADOM support can break policy feature compatibility or management. The stated case instead calls for: Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory.

B.

Choose the supported ADOM operation and device modes based on whether central FortiManager will own policy packages or inventory and device settings, then test the intended editing and installation workflow. This addresses “Select FortiManager ADOM mode that matches FortiGate and policy responsibilities”, where the governing principle is: ADOM operating choices determine which central policy and device-management functions apply; selecting a more restricted mode cannot be fixed by simply labeling a firewall package as managed. The stated case instead calls for: Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory.

C.

Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant. This addresses “Protect FortiManager administrative access using scoped roles and external authentication”, where the governing principle is: A successful external login proves identity but does not automatically impose correct FortiManager administrative scope; explicit profile privileges and ADOM assignments enforce authorization across isolated management customers. The stated case instead calls for: Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory.

D.

Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory. ADOM configuration and security objects are stored centrally; a previous device-level revision does not necessarily include every ADOM-shared object, administrator profile or global policy assignment required to restore the intended state. Verify the result with this test: Create a benign object and policy revision in a lab ADOM, record protected backup and revision IDs, perform a controlled rollback test and compare prechange objects and policy packages.

Question 132

A financial organization schedules an ADOM schema upgrade and requires verifiable database recovery checkpoints before network maintenance begins. The engineer proposes the following change: Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory. Which mechanism explains why it works?

  1. A successful external login proves identity but does not automatically impose correct FortiManager administrative scope; explicit profile privileges and ADOM assignments enforce authorization across isolated management customers.
  2. ADOM configuration and security objects are stored centrally; a previous device-level revision does not necessarily include every ADOM-shared object, administrator profile or global policy assignment required to restore the intended state.
  3. FortiManager's ADOM data schema and features depend on the selected supported version; moving a FortiGate to newer FortiOS without checking ADOM support can break policy feature compatibility or management.
  4. ADOM operating choices determine which central policy and device-management functions apply; selecting a more restricted mode cannot be fixed by simply labeling a firewall package as managed.

Answer & Explanations

Correct answer: B

A.

A successful external login proves identity but does not automatically impose correct FortiManager administrative scope; explicit profile privileges and ADOM assignments enforce authorization across isolated management customers. That explains “Protect FortiManager administrative access using scoped roles and external authentication”, not the mechanism behind the described change. The relevant principle is: ADOM configuration and security objects are stored centrally; a previous device-level revision does not necessarily include every ADOM-shared object, administrator profile or global policy assignment required to restore the intended state.

B.

ADOM configuration and security objects are stored centrally; a previous device-level revision does not necessarily include every ADOM-shared object, administrator profile or global policy assignment required to restore the intended state. The corresponding implementation is: Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory.

C.

FortiManager's ADOM data schema and features depend on the selected supported version; moving a FortiGate to newer FortiOS without checking ADOM support can break policy feature compatibility or management. That explains “Keep ADOM firmware version compatibility aligned with managed FortiGate releases”, not the mechanism behind the described change. The relevant principle is: ADOM configuration and security objects are stored centrally; a previous device-level revision does not necessarily include every ADOM-shared object, administrator profile or global policy assignment required to restore the intended state.

D.

ADOM operating choices determine which central policy and device-management functions apply; selecting a more restricted mode cannot be fixed by simply labeling a firewall package as managed. That explains “Select FortiManager ADOM mode that matches FortiGate and policy responsibilities”, not the mechanism behind the described change. The relevant principle is: ADOM configuration and security objects are stored centrally; a previous device-level revision does not necessarily include every ADOM-shared object, administrator profile or global policy assignment required to restore the intended state.

Question 133

A financial organization schedules an ADOM schema upgrade and requires verifiable database recovery checkpoints before network maintenance begins. After implementing this change—Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory.—which test most directly validates its intended outcome?

  1. Create a benign object and policy revision in a lab ADOM, record protected backup and revision IDs, perform a controlled rollback test and compare prechange objects and policy packages.
  2. Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout.
  3. Configure a test ADOM in the intended supported mode, verify which policy-editor, device database and installation operations are exposed, and compare them with a deliberately alternate mode.
  4. Compare a staged FortiGate's FortiOS version with the ADOM target version, verify management and object editor compatibility, and rehearse a supported one-click ADOM upgrade in the lab.

Answer & Explanations

Correct answer: A

A.

Create a benign object and policy revision in a lab ADOM, record protected backup and revision IDs, perform a controlled rollback test and compare prechange objects and policy packages. This check is decisive because aDOM configuration and security objects are stored centrally; a previous device-level revision does not necessarily include every ADOM-shared object, administrator profile or global policy assignment required to restore the intended state.

B.

Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout. That would help test “Protect FortiManager administrative access using scoped roles and external authentication”, not the outcome required in this scenario. The relevant acceptance check is: Create a benign object and policy revision in a lab ADOM, record protected backup and revision IDs, perform a controlled rollback test and compare prechange objects and policy packages.

C.

Configure a test ADOM in the intended supported mode, verify which policy-editor, device database and installation operations are exposed, and compare them with a deliberately alternate mode. That would help test “Select FortiManager ADOM mode that matches FortiGate and policy responsibilities”, not the outcome required in this scenario. The relevant acceptance check is: Create a benign object and policy revision in a lab ADOM, record protected backup and revision IDs, perform a controlled rollback test and compare prechange objects and policy packages.

D.

Compare a staged FortiGate's FortiOS version with the ADOM target version, verify management and object editor compatibility, and rehearse a supported one-click ADOM upgrade in the lab. That would help test “Keep ADOM firmware version compatibility aligned with managed FortiGate releases”, not the outcome required in this scenario. The relevant acceptance check is: Create a benign object and policy revision in a lab ADOM, record protected backup and revision IDs, perform a controlled rollback test and compare prechange objects and policy packages.

Question 134

A financial organization schedules an ADOM schema upgrade and requires verifiable database recovery checkpoints before network maintenance begins. Which proposed shortcut most directly risks irreversible central policy history loss after failing to preserve management database and ADOM revisions and should therefore be rejected?

  1. Upgrade selected FortiGate devices to a new major version while leaving every management ADOM on an incompatible old schema and assuming new policy fields are universally recognized.
  2. Delete an ADOM before migration and assume its shared objects and review history will be recreated automatically from the current running configuration of one FortiGate.
  3. Turn on a mode that omits required central policy management and assume FortiManager will still author and install the organization's shared firewall rule base exactly as before.
  4. Grant every externally authenticated contractor a Super_User profile for all ADOMs because the enterprise RADIUS server already authenticated their passwords.

Answer & Explanations

Correct answer: B

A.

Upgrade selected FortiGate devices to a new major version while leaving every management ADOM on an incompatible old schema and assuming new policy fields are universally recognized. That shortcut risks unsupported policy and device features after ignoring FortiOS version dependencies of central ADOM databases. Here the specific shortcut is: Delete an ADOM before migration and assume its shared objects and review history will be recreated automatically from the current running configuration of one FortiGate.

B.

Delete an ADOM before migration and assume its shared objects and review history will be recreated automatically from the current running configuration of one FortiGate. The foreseeable failure is irreversible central policy history loss after failing to preserve management database and ADOM revisions. The safer response is: Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory.

C.

Turn on a mode that omits required central policy management and assume FortiManager will still author and install the organization's shared firewall rule base exactly as before. That shortcut risks missing centralized policy functionality after selecting an ADOM management mode inconsistent with operational requirements. Here the specific shortcut is: Delete an ADOM before migration and assume its shared objects and review history will be recreated automatically from the current running configuration of one FortiGate.

D.

Grant every externally authenticated contractor a Super_User profile for all ADOMs because the enterprise RADIUS server already authenticated their passwords. That shortcut risks unauthorized cross-tenant policy changes after conflating centralized authentication with least-privilege FortiManager authorization. Here the specific shortcut is: Delete an ADOM before migration and assume its shared objects and review history will be recreated automatically from the current running configuration of one FortiGate.

Question 135

A financial organization schedules an ADOM schema upgrade and requires verifiable database recovery checkpoints before network maintenance begins. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory. Verify: Configure a test ADOM in the intended supported mode, verify which policy-editor, device database and installation operations are exposed, and compare them with a deliberately alternate mode.
  2. Implement: Choose the supported ADOM operation and device modes based on whether central FortiManager will own policy packages or inventory and device settings, then test the intended editing and installation workflow. Verify: Create a benign object and policy revision in a lab ADOM, record protected backup and revision IDs, perform a controlled rollback test and compare prechange objects and policy packages.
  3. Implement: Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory. Verify: Create a benign object and policy revision in a lab ADOM, record protected backup and revision IDs, perform a controlled rollback test and compare prechange objects and policy packages.
  4. Implement: Set each ADOM to a supported FortiOS compatibility version for its managed devices and plan the official ADOM upgrade or migration path before introducing gateways on newer firmware. Verify: Compare a staged FortiGate's FortiOS version with the ADOM target version, verify management and object editor compatibility, and rehearse a supported one-click ADOM upgrade in the lab.

Answer & Explanations

Correct answer: C

A.

The action is applicable: Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory. But its proposed test—Configure a test ADOM in the intended supported mode, verify which policy-editor, device database and installation operations are exposed, and compare them with a deliberately alternate mode.—addresses “Select FortiManager ADOM mode that matches FortiGate and policy responsibilities”. This requirement is confirmed instead by: Create a benign object and policy revision in a lab ADOM, record protected backup and revision IDs, perform a controlled rollback test and compare prechange objects and policy packages.

B.

The test would be relevant: Create a benign object and policy revision in a lab ADOM, record protected backup and revision IDs, perform a controlled rollback test and compare prechange objects and policy packages. But the offered implementation—Choose the supported ADOM operation and device modes based on whether central FortiManager will own policy packages or inventory and device settings, then test the intended editing and installation workflow.—addresses “Select FortiManager ADOM mode that matches FortiGate and policy responsibilities”. The action needed here is: Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory.

C.

Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory. Confirm it through this test: Create a benign object and policy revision in a lab ADOM, record protected backup and revision IDs, perform a controlled rollback test and compare prechange objects and policy packages. ADOM configuration and security objects are stored centrally; a previous device-level revision does not necessarily include every ADOM-shared object, administrator profile or global policy assignment required to restore the intended state.

D.

This action/test pair addresses “Keep ADOM firmware version compatibility aligned with managed FortiGate releases”. Set each ADOM to a supported FortiOS compatibility version for its managed devices and plan the official ADOM upgrade or migration path before introducing gateways on newer firmware. Compare a staged FortiGate's FortiOS version with the ADOM target version, verify management and object editor compatibility, and rehearse a supported one-click ADOM upgrade in the lab. The case instead calls for: Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory.

Question 136

A research institution is decommissioning an obsolete ADOM and needs a rollback strategy preserving shared policy objects until the final customer migration is accepted. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access.
  2. Use the documented FortiManager ADOM upgrade and version-migration workflow with a prechange backup, check supported target firmware ranges, and explicitly distinguish ADOM schema conversion from installing FortiOS on firewalls.
  3. Use the supported initial setup wizard or CLI to set management interfaces, routes, DNS, time synchronization and appropriately restricted administrator access before onboarding production FortiGates.
  4. Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory.

Answer & Explanations

Correct answer: D

A.

Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access. This addresses “Coordinate ADOM administrative privileges and multi-administrator sessions”, where the governing principle is: Parallel administrators may have distinct permissions and session state; access to the FortiManager login page does not imply write rights to all ADOMs or protect against edit collisions. The stated case instead calls for: Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory.

B.

Use the documented FortiManager ADOM upgrade and version-migration workflow with a prechange backup, check supported target firmware ranges, and explicitly distinguish ADOM schema conversion from installing FortiOS on firewalls. This addresses “Stage an ADOM upgrade independently of an individual FortiGate firmware upgrade”, where the governing principle is: Changing an ADOM database version does not itself reboot or upgrade every FortiGate; management compatibility and gateway firmware are separate coordinated changes that require their own installation and verification. The stated case instead calls for: Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory.

C.

Use the supported initial setup wizard or CLI to set management interfaces, routes, DNS, time synchronization and appropriately restricted administrator access before onboarding production FortiGates. This addresses “Complete initial FortiManager system networking and administrator hardening”, where the governing principle is: FGFM management and authenticated administrator sessions depend on reachable control-plane addressing and trustworthy timing; leaving default settings or an unreachable management path can prevent device discovery and secure operation. The stated case instead calls for: Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory.

D.

The question is set in this situation: A research institution is decommissioning an obsolete ADOM and needs a rollback strategy preserving shared policy objects until the final customer migration is accepted. Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory. ADOM configuration and security objects are stored centrally; a previous device-level revision does not necessarily include every ADOM-shared object, administrator profile or global policy assignment required to restore the intended state. Verify the result with this test: Create a benign object and policy revision in a lab ADOM, record protected backup and revision IDs, perform a controlled rollback test and compare prechange objects and policy packages.

Question 137

A research institution is decommissioning an obsolete ADOM and needs a rollback strategy preserving shared policy objects until the final customer migration is accepted. The engineer proposes the following change: Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory. Which mechanism explains why it works?

  1. Parallel administrators may have distinct permissions and session state; access to the FortiManager login page does not imply write rights to all ADOMs or protect against edit collisions.
  2. ADOM configuration and security objects are stored centrally; a previous device-level revision does not necessarily include every ADOM-shared object, administrator profile or global policy assignment required to restore the intended state.
  3. Changing an ADOM database version does not itself reboot or upgrade every FortiGate; management compatibility and gateway firmware are separate coordinated changes that require their own installation and verification.
  4. FGFM management and authenticated administrator sessions depend on reachable control-plane addressing and trustworthy timing; leaving default settings or an unreachable management path can prevent device discovery and secure operation.

Answer & Explanations

Correct answer: B

A.

Parallel administrators may have distinct permissions and session state; access to the FortiManager login page does not imply write rights to all ADOMs or protect against edit collisions. That explains “Coordinate ADOM administrative privileges and multi-administrator sessions”, not the mechanism behind the described change. The relevant principle is: ADOM configuration and security objects are stored centrally; a previous device-level revision does not necessarily include every ADOM-shared object, administrator profile or global policy assignment required to restore the intended state.

B.

The question is set in this situation: A research institution is decommissioning an obsolete ADOM and needs a rollback strategy preserving shared policy objects until the final customer migration is accepted. ADOM configuration and security objects are stored centrally; a previous device-level revision does not necessarily include every ADOM-shared object, administrator profile or global policy assignment required to restore the intended state. The corresponding implementation is: Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory.

C.

Changing an ADOM database version does not itself reboot or upgrade every FortiGate; management compatibility and gateway firmware are separate coordinated changes that require their own installation and verification. That explains “Stage an ADOM upgrade independently of an individual FortiGate firmware upgrade”, not the mechanism behind the described change. The relevant principle is: ADOM configuration and security objects are stored centrally; a previous device-level revision does not necessarily include every ADOM-shared object, administrator profile or global policy assignment required to restore the intended state.

D.

FGFM management and authenticated administrator sessions depend on reachable control-plane addressing and trustworthy timing; leaving default settings or an unreachable management path can prevent device discovery and secure operation. That explains “Complete initial FortiManager system networking and administrator hardening”, not the mechanism behind the described change. The relevant principle is: ADOM configuration and security objects are stored centrally; a previous device-level revision does not necessarily include every ADOM-shared object, administrator profile or global policy assignment required to restore the intended state.

Question 138

A research institution is decommissioning an obsolete ADOM and needs a rollback strategy preserving shared policy objects until the final customer migration is accepted. After implementing this change—Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory.—which test most directly validates its intended outcome?

  1. Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records.
  2. Upgrade a disposable test ADOM, inspect its new version and unchanged FortiGate running release, then verify a compatible policy import and installation to a staged gateway.
  3. From an authorized management subnet connect to the new FortiManager, verify its route, clock and name resolution, deny an unapproved management source, and confirm no default shared administrator credential remains.
  4. Create a benign object and policy revision in a lab ADOM, record protected backup and revision IDs, perform a controlled rollback test and compare prechange objects and policy packages.

Answer & Explanations

Correct answer: D

A.

Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records. That would help test “Coordinate ADOM administrative privileges and multi-administrator sessions”, not the outcome required in this scenario. The relevant acceptance check is: Create a benign object and policy revision in a lab ADOM, record protected backup and revision IDs, perform a controlled rollback test and compare prechange objects and policy packages.

B.

Upgrade a disposable test ADOM, inspect its new version and unchanged FortiGate running release, then verify a compatible policy import and installation to a staged gateway. That would help test “Stage an ADOM upgrade independently of an individual FortiGate firmware upgrade”, not the outcome required in this scenario. The relevant acceptance check is: Create a benign object and policy revision in a lab ADOM, record protected backup and revision IDs, perform a controlled rollback test and compare prechange objects and policy packages.

C.

From an authorized management subnet connect to the new FortiManager, verify its route, clock and name resolution, deny an unapproved management source, and confirm no default shared administrator credential remains. That would help test “Complete initial FortiManager system networking and administrator hardening”, not the outcome required in this scenario. The relevant acceptance check is: Create a benign object and policy revision in a lab ADOM, record protected backup and revision IDs, perform a controlled rollback test and compare prechange objects and policy packages.

D.

The question is set in this situation: A research institution is decommissioning an obsolete ADOM and needs a rollback strategy preserving shared policy objects until the final customer migration is accepted. Create a benign object and policy revision in a lab ADOM, record protected backup and revision IDs, perform a controlled rollback test and compare prechange objects and policy packages. This check is decisive because aDOM configuration and security objects are stored centrally; a previous device-level revision does not necessarily include every ADOM-shared object, administrator profile or global policy assignment required to restore the intended state.

Question 139

A research institution is decommissioning an obsolete ADOM and needs a rollback strategy preserving shared policy objects until the final customer migration is accepted. Which proposed shortcut most directly risks irreversible central policy history loss after failing to preserve management database and ADOM revisions and should therefore be rejected?

  1. Delete an ADOM before migration and assume its shared objects and review history will be recreated automatically from the current running configuration of one FortiGate.
  2. Click the ADOM upgrade control and report that all registered FortiGate appliances have also received a complete firmware update even though no gateway software jobs ran.
  3. Share the central superuser password among regional security teams and rely on verbal agreements to stop users making simultaneous conflicting changes.
  4. Expose a factory-default FortiManager management interface directly to the internet and begin registering branch gateways before setting a restricted administrator account or working route.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: A research institution is decommissioning an obsolete ADOM and needs a rollback strategy preserving shared policy objects until the final customer migration is accepted. Delete an ADOM before migration and assume its shared objects and review history will be recreated automatically from the current running configuration of one FortiGate. The foreseeable failure is irreversible central policy history loss after failing to preserve management database and ADOM revisions. The safer response is: Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory.

B.

Click the ADOM upgrade control and report that all registered FortiGate appliances have also received a complete firmware update even though no gateway software jobs ran. That shortcut risks false upgrade compliance and potential policy mismatch after conflating ADOM schema upgrades with FortiOS software installation. Here the specific shortcut is: Delete an ADOM before migration and assume its shared objects and review history will be recreated automatically from the current running configuration of one FortiGate.

C.

Share the central superuser password among regional security teams and rely on verbal agreements to stop users making simultaneous conflicting changes. That shortcut risks untraceable privileged policy changes and multi-tenant exposure caused by shared FortiManager administrator credentials. Here the specific shortcut is: Delete an ADOM before migration and assume its shared objects and review history will be recreated automatically from the current running configuration of one FortiGate.

D.

Expose a factory-default FortiManager management interface directly to the internet and begin registering branch gateways before setting a restricted administrator account or working route. That shortcut risks central management compromise or failed device onboarding from unprotected factory defaults and incomplete network bootstrap. Here the specific shortcut is: Delete an ADOM before migration and assume its shared objects and review history will be recreated automatically from the current running configuration of one FortiGate.

Question 140

A research institution is decommissioning an obsolete ADOM and needs a rollback strategy preserving shared policy objects until the final customer migration is accepted. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Use the documented FortiManager ADOM upgrade and version-migration workflow with a prechange backup, check supported target firmware ranges, and explicitly distinguish ADOM schema conversion from installing FortiOS on firewalls. Verify: Upgrade a disposable test ADOM, inspect its new version and unchanged FortiGate running release, then verify a compatible policy import and installation to a staged gateway.
  2. Implement: Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access. Verify: Create a benign object and policy revision in a lab ADOM, record protected backup and revision IDs, perform a controlled rollback test and compare prechange objects and policy packages.
  3. Implement: Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory. Verify: Create a benign object and policy revision in a lab ADOM, record protected backup and revision IDs, perform a controlled rollback test and compare prechange objects and policy packages.
  4. Implement: Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory. Verify: Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records.

Answer & Explanations

Correct answer: C

A.

This action/test pair addresses “Stage an ADOM upgrade independently of an individual FortiGate firmware upgrade”. Use the documented FortiManager ADOM upgrade and version-migration workflow with a prechange backup, check supported target firmware ranges, and explicitly distinguish ADOM schema conversion from installing FortiOS on firewalls. Upgrade a disposable test ADOM, inspect its new version and unchanged FortiGate running release, then verify a compatible policy import and installation to a staged gateway. The case instead calls for: Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory.

B.

The test would be relevant: Create a benign object and policy revision in a lab ADOM, record protected backup and revision IDs, perform a controlled rollback test and compare prechange objects and policy packages. But the offered implementation—Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access.—addresses “Coordinate ADOM administrative privileges and multi-administrator sessions”. The action needed here is: Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory.

C.

The question is set in this situation: A research institution is decommissioning an obsolete ADOM and needs a rollback strategy preserving shared policy objects until the final customer migration is accepted. Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory. Confirm it through this test: Create a benign object and policy revision in a lab ADOM, record protected backup and revision IDs, perform a controlled rollback test and compare prechange objects and policy packages. ADOM configuration and security objects are stored centrally; a previous device-level revision does not necessarily include every ADOM-shared object, administrator profile or global policy assignment required to restore the intended state.

D.

The action is applicable: Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory. But its proposed test—Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records.—addresses “Coordinate ADOM administrative privileges and multi-administrator sessions”. This requirement is confirmed instead by: Create a benign object and policy revision in a lab ADOM, record protected backup and revision IDs, perform a controlled rollback test and compare prechange objects and policy packages.

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