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 15

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.

Question 141

A retail cybersecurity team has approval to convert one ADOM to a newer compatibility version but the branch FortiGate upgrade is scheduled for a later date. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. Open the supported FortiManager topology or Fabric views for registered devices, correlate reported relationships with the approved network inventory, and investigate unexpected missing neighbors instead of presuming every discovered node is managed.
  2. 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.
  3. 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.
  4. 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.

Answer & Explanations

Correct answer: C

A.

Open the supported FortiManager topology or Fabric views for registered devices, correlate reported relationships with the approved network inventory, and investigate unexpected missing neighbors instead of presuming every discovered node is managed. This addresses “Use FortiManager network topology to validate managed estate visibility”, where the governing principle is: Topology visibility depends on device registration, supported telemetry and actual network relationships; a drawn fabric edge or visible hostname alone does not create device control or verify that firmware and policies are current. The stated case instead calls for: 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.

B.

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

C.

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

D.

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. This addresses “Move a registered FortiGate between ADOMs through a supported workflow”, where the governing principle is: An ADOM move changes the management database and package context for a device; dragging a device label between groups is not equivalent to reconciling its interface mappings, imported rules and target ADOM compatibility. The stated case instead calls for: 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.

Question 142

A retail cybersecurity team has approval to convert one ADOM to a newer compatibility version but the branch FortiGate upgrade is scheduled for a later date. The engineer proposes the following change: 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. Which mechanism explains why it works?

  1. 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.
  2. An ADOM move changes the management database and package context for a device; dragging a device label between groups is not equivalent to reconciling its interface mappings, imported rules and target ADOM compatibility.
  3. Topology visibility depends on device registration, supported telemetry and actual network relationships; a drawn fabric edge or visible hostname alone does not create device control or verify that firmware and policies are current.
  4. 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.

Answer & Explanations

Correct answer: A

A.

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

B.

An ADOM move changes the management database and package context for a device; dragging a device label between groups is not equivalent to reconciling its interface mappings, imported rules and target ADOM compatibility. That explains “Move a registered FortiGate between ADOMs through a supported workflow”, not the mechanism behind the described change. The relevant 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.

C.

Topology visibility depends on device registration, supported telemetry and actual network relationships; a drawn fabric edge or visible hostname alone does not create device control or verify that firmware and policies are current. That explains “Use FortiManager network topology to validate managed estate visibility”, not the mechanism behind the described change. The relevant 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.

D.

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

Question 143

A retail cybersecurity team has approval to convert one ADOM to a newer compatibility version but the branch FortiGate upgrade is scheduled for a later date. After implementing this change—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.—which test most directly validates its intended outcome?

  1. 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.
  2. Compare a known branch FortiGate and its neighboring devices against the topology view, inspect registration and last-contact status, and explain one deliberately disconnected test device.
  3. 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.
  4. 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.

Answer & Explanations

Correct answer: D

A.

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. That would help test “Move a registered FortiGate between ADOMs through a supported workflow”, not the outcome required in this scenario. The relevant acceptance check is: 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.

B.

Compare a known branch FortiGate and its neighboring devices against the topology view, inspect registration and last-contact status, and explain one deliberately disconnected test device. That would help test “Use FortiManager network topology to validate managed estate visibility”, not the outcome required in this scenario. The relevant acceptance check is: 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.

C.

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

D.

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

Question 144

A retail cybersecurity team has approval to convert one ADOM to a newer compatibility version but the branch FortiGate upgrade is scheduled for a later date. Which proposed shortcut most directly risks false upgrade compliance and potential policy mismatch after conflating ADOM schema upgrades with FortiOS software installation and should therefore be rejected?

  1. Rename a branch firewall to match the destination customer and assume it automatically moves with its policies into a new ADOM without migration or version checks.
  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. Treat all automatically discovered topology icons as trusted FortiManager-managed firewalls and install a corporate policy on them without verifying registration or permissions.
  4. 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.

Answer & Explanations

Correct answer: B

A.

Rename a branch firewall to match the destination customer and assume it automatically moves with its policies into a new ADOM without migration or version checks. That shortcut risks orphaned device or incorrect policy ownership after treating an ADOM move as a cosmetic rename. Here the specific shortcut is: 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.

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. The foreseeable failure is false upgrade compliance and potential policy mismatch after conflating ADOM schema upgrades with FortiOS software installation. The safer response is: 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.

C.

Treat all automatically discovered topology icons as trusted FortiManager-managed firewalls and install a corporate policy on them without verifying registration or permissions. That shortcut risks unauthorized management assumptions after confusing discovered network relationships with authenticated managed-device inventory. Here the specific shortcut is: 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.

D.

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

Question 145

A retail cybersecurity team has approval to convert one ADOM to a newer compatibility version but the branch FortiGate upgrade is scheduled for a later date. 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 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: 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.
  3. 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: 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: 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: 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.

Answer & Explanations

Correct answer: A

A.

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. Confirm it through this test: 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. 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.

B.

The action is applicable: 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. But its proposed test—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.—addresses “Keep ADOM firmware version compatibility aligned with managed FortiGate releases”. This requirement is confirmed instead by: 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.

C.

This action/test pair addresses “Move a registered FortiGate between ADOMs through a supported workflow”. 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. 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. The case instead calls for: 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.

D.

The test would be relevant: 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. But the offered implementation—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.—addresses “Keep ADOM firmware version compatibility aligned with managed FortiGate releases”. The action needed here is: 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.

Question 146

An MSP operates mixed-version customer estates and wants a change plan that proves which operations modify the FortiManager database versus firewall firmware. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. 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.
  2. Configure supported administrative domains that match independent customers or security jurisdictions, assign managed devices and administrators to correct ADOMs, and verify object and policy isolation.
  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. 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.

Answer & Explanations

Correct answer: D

A.

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. This addresses “Restore FortiManager ADOM content after a controlled management change”, where the governing 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. The stated case instead calls for: 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.

B.

Configure supported administrative domains that match independent customers or security jurisdictions, assign managed devices and administrators to correct ADOMs, and verify object and policy isolation. This addresses “Divide a multi-customer FortiManager environment into appropriate ADOMs”, where the governing principle is: ADOMs partition FortiManager's management scope and databases; a descriptive device group by itself does not create isolation between customers or prevent an administrator from editing shared policy objects. The stated case instead calls for: 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.

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

D.

The question is set in this situation: An MSP operates mixed-version customer estates and wants a change plan that proves which operations modify the FortiManager database versus firewall firmware. 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. 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. Verify the result with this test: 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.

Question 147

An MSP operates mixed-version customer estates and wants a change plan that proves which operations modify the FortiManager database versus firewall firmware. The engineer proposes the following change: 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. Which mechanism explains why it works?

  1. ADOMs partition FortiManager's management scope and databases; a descriptive device group by itself does not create isolation between customers or prevent an administrator from editing shared policy objects.
  2. 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.
  3. 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.
  4. 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.

Answer & Explanations

Correct answer: B

A.

ADOMs partition FortiManager's management scope and databases; a descriptive device group by itself does not create isolation between customers or prevent an administrator from editing shared policy objects. That explains “Divide a multi-customer FortiManager environment into appropriate ADOMs”, not the mechanism behind the described change. The relevant 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.

B.

The question is set in this situation: An MSP operates mixed-version customer estates and wants a change plan that proves which operations modify the FortiManager database versus firewall firmware. 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 corresponding implementation is: 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.

C.

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

D.

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. That explains “Restore FortiManager ADOM content after a controlled management change”, not the mechanism behind the described change. The relevant 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.

Question 148

An MSP operates mixed-version customer estates and wants a change plan that proves which operations modify the FortiManager database versus firewall firmware. After implementing this change—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.—which test most directly validates its intended outcome?

  1. Create two lab ADOMs with separate administrators and policy packages, verify a device and object from the first are unavailable for modification from the second, and document global policy exceptions.
  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. 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.
  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: C

A.

Create two lab ADOMs with separate administrators and policy packages, verify a device and object from the first are unavailable for modification from the second, and document global policy exceptions. That would help test “Divide a multi-customer FortiManager environment into appropriate ADOMs”, not the outcome required in this scenario. The relevant acceptance check is: 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.

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

C.

The question is set in this situation: An MSP operates mixed-version customer estates and wants a change plan that proves which operations modify the FortiManager database versus firewall firmware. 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. This check is decisive because 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.

D.

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. That would help test “Restore FortiManager ADOM content after a controlled management change”, not the outcome required in this scenario. The relevant acceptance check is: 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.

Question 149

An MSP operates mixed-version customer estates and wants a change plan that proves which operations modify the FortiManager database versus firewall firmware. Which proposed shortcut most directly risks false upgrade compliance and potential policy mismatch after conflating ADOM schema upgrades with FortiOS software installation and should therefore be rejected?

  1. Grant every externally authenticated contractor a Super_User profile for all ADOMs because the enterprise RADIUS server already authenticated their passwords.
  2. Put unrelated customers in one root ADOM and assume distinct device-group names automatically provide separate policy databases and administrative authority.
  3. 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.
  4. 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.

Answer & Explanations

Correct answer: C

A.

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

B.

Put unrelated customers in one root ADOM and assume distinct device-group names automatically provide separate policy databases and administrative authority. That shortcut risks cross-customer policy exposure after using device organization labels as a substitute for ADOM isolation. Here the specific shortcut is: 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.

C.

The question is set in this situation: An MSP operates mixed-version customer estates and wants a change plan that proves which operations modify the FortiManager database versus firewall firmware. 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. The foreseeable failure is false upgrade compliance and potential policy mismatch after conflating ADOM schema upgrades with FortiOS software installation. The safer response is: 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.

D.

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. That shortcut risks irreversible central policy history loss after failing to preserve management database and ADOM revisions. Here the specific shortcut is: 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.

Question 150

An MSP operates mixed-version customer estates and wants a change plan that proves which operations modify the FortiManager database versus firewall firmware. 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: 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. 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.
  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: 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.
  4. Implement: Configure supported administrative domains that match independent customers or security jurisdictions, assign managed devices and administrators to correct ADOMs, and verify object and policy isolation. Verify: Create two lab ADOMs with separate administrators and policy packages, verify a device and object from the first are unavailable for modification from the second, and document global policy exceptions.

Answer & Explanations

Correct answer: B

A.

The action is applicable: 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. But its proposed 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.—addresses “Restore FortiManager ADOM content after a controlled management change”. This requirement is confirmed instead by: 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.

B.

The question is set in this situation: An MSP operates mixed-version customer estates and wants a change plan that proves which operations modify the FortiManager database versus firewall firmware. 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. Confirm it through this test: 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. 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.

C.

The test would be relevant: 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. But the offered implementation—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.—addresses “Restore FortiManager ADOM content after a controlled management change”. The action needed here is: 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.

D.

This action/test pair addresses “Divide a multi-customer FortiManager environment into appropriate ADOMs”. Configure supported administrative domains that match independent customers or security jurisdictions, assign managed devices and administrators to correct ADOMs, and verify object and policy isolation. Create two lab ADOMs with separate administrators and policy packages, verify a device and object from the first are unavailable for modification from the second, and document global policy exceptions. The case instead calls for: 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.

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