Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 12
Question 110
An MSP is aligning ADOM version upgrades with customer firmware maintenance windows to avoid forcing all client firewalls to change simultaneously. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: D
The action is applicable: 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. 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: 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 test would be relevant: 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. 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: 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 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: 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.
The question is set in this situation: An MSP is aligning ADOM version upgrades with customer firmware maintenance windows to avoid forcing all client firewalls to change simultaneously. 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. Confirm it through this 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. 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.
Question 111
A chain of clinics sold one branch to a different business unit and must transfer its managed FortiGate to a different FortiManager ADOM. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: A
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. 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. Verify the result with this 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.
Identify whether the FortiManager deployment uses supported FortiAnalyzer features or forwards events to an approved FortiAnalyzer service, and configure the intended logging and event-analysis path separately from policy provisioning. This addresses “Choose FortiManager integrated logging versus dedicated FortiAnalyzer capabilities”, where the governing principle is: Central policy management and log analytics are related but separate functions; naming a FortiAnalyzer integration does not make FortiManager an unrestricted long-term log repository or guarantee that gateway event data is received. The stated case instead calls for: 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.
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: 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.
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: 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.
Question 112
A chain of clinics sold one branch to a different business unit and must transfer its managed FortiGate to a different FortiManager ADOM. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: C
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: 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.
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: 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.
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 corresponding implementation is: 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.
Central policy management and log analytics are related but separate functions; naming a FortiAnalyzer integration does not make FortiManager an unrestricted long-term log repository or guarantee that gateway event data is received. That explains “Choose FortiManager integrated logging versus dedicated FortiAnalyzer capabilities”, not the mechanism behind the described change. The relevant 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.
Question 113
A chain of clinics sold one branch to a different business unit and must transfer its managed FortiGate to a different FortiManager ADOM. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: C
Generate a harmless blocked connection on a test FortiGate, verify its log reaches the configured analysis destination and remains searchable, and separately confirm FortiManager can still install policy. That would help test “Choose FortiManager integrated logging versus dedicated FortiAnalyzer capabilities”, not the outcome required in this scenario. The relevant acceptance check is: 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.
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: 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.
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. This check is decisive because 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.
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: 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.
Question 114
A chain of clinics sold one branch to a different business unit and must transfer its managed FortiGate to a different FortiManager ADOM. Which proposed shortcut most directly risks orphaned device or incorrect policy ownership after treating an ADOM move as a cosmetic rename and should therefore be rejected?
Answer & Explanations
Correct answer: D
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: 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.
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: 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.
Deploy FortiManager, leave every gateway without any logging destination, and report that FortiAnalyzer security reports must appear automatically after policy installation. That shortcut risks missing security visibility after assuming central configuration automatically delivers usable analytics and log retention. Here the specific shortcut is: 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.
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. The foreseeable failure is orphaned device or incorrect policy ownership after treating an ADOM move as a cosmetic rename. The safer response is: 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.
Question 115
A chain of clinics sold one branch to a different business unit and must transfer its managed FortiGate to a different FortiManager ADOM. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: B
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: 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.
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. Confirm it through this 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. 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 action is applicable: 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. But its proposed 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.—addresses “Stage an ADOM upgrade independently of an individual FortiGate firmware upgrade”. This requirement is confirmed instead by: 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 test would be relevant: 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. But the offered implementation—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.—addresses “Stage an ADOM upgrade independently of an individual FortiGate firmware upgrade”. The action needed here is: 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.
Question 116
An IT services group is reorganizing customer contracts and needs evidence that a moved device still has the right policy and administrative scope. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: A
The question is set in this situation: An IT services group is reorganizing customer contracts and needs evidence that a moved device still has the right policy and administrative scope. 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. 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. Verify the result with this 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.
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: 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.
Use FortiManager's supported offline mode only for a documented disconnected management or staging workflow and confirm that operations requiring live FortiGuard or connected devices have a separate readiness plan. This addresses “Plan the FortiManager offline maintenance mode against connectivity requirements”, where the governing principle is: An offline management state changes what external or live configuration interactions can complete; cached object editing does not imply current FortiGuard information or device synchronization is available. The stated case instead calls for: 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.
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: 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.
Question 117
An IT services group is reorganizing customer contracts and needs evidence that a moved device still has the right policy and administrative scope. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: D
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: 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.
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: 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.
An offline management state changes what external or live configuration interactions can complete; cached object editing does not imply current FortiGuard information or device synchronization is available. That explains “Plan the FortiManager offline maintenance mode against connectivity requirements”, not the mechanism behind the described change. The relevant 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 question is set in this situation: An IT services group is reorganizing customer contracts and needs evidence that a moved device still has the right policy and administrative scope. 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 corresponding implementation is: 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.
Question 118
An IT services group is reorganizing customer contracts and needs evidence that a moved device still has the right policy and administrative scope. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: B
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: 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 question is set in this situation: An IT services group is reorganizing customer contracts and needs evidence that a moved device still has the right policy and administrative scope. 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. This check is decisive because 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.
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: 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.
In a disconnected lab verify permitted local work, record which registration, update or installation actions are unavailable, then reconnect and demonstrate an explicitly reviewed synchronized change. That would help test “Plan the FortiManager offline maintenance mode against connectivity requirements”, not the outcome required in this scenario. The relevant acceptance check is: 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.
Question 119
An IT services group is reorganizing customer contracts and needs evidence that a moved device still has the right policy and administrative scope. Which proposed shortcut most directly risks orphaned device or incorrect policy ownership after treating an ADOM move as a cosmetic rename and should therefore be rejected?
Answer & Explanations
Correct answer: A
The question is set in this situation: An IT services group is reorganizing customer contracts and needs evidence that a moved device still has the right policy and administrative scope. 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. The foreseeable failure is orphaned device or incorrect policy ownership after treating an ADOM move as a cosmetic rename. The safer response is: 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.
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: 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.
Declare FortiManager permanently disconnected while promising live FortiGuard signatures and immediate policy installs to every remote gateway without any communication path. That shortcut risks stale management state and failed updates after treating offline staging capabilities as evidence of live connectivity. Here the specific shortcut is: 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.
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: 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.
Question 120
An IT services group is reorganizing customer contracts and needs evidence that a moved device still has the right policy and administrative scope. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: C
This action/test pair addresses “Coordinate ADOM administrative privileges and multi-administrator sessions”. Use explicit FortiManager administrator profiles, authorized ADOM assignments and session visibility so delegated teams can perform their tasks without creating shared unrestricted administrative access. 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. The case instead calls for: 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.
The test would be relevant: 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. 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: 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.
The question is set in this situation: An IT services group is reorganizing customer contracts and needs evidence that a moved device still has the right policy and administrative scope. 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. Confirm it through this 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. 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 action is applicable: 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. 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: 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.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- Fortinet FCP_FMG_AD-7.6 Practice Test 10 - 10 Questions (Last Reviewed 11-Nov-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 11 - 10 Questions (Last Reviewed 10-Nov-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 12 - 10 Questions (Last Reviewed 09-Nov-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 13 - 10 Questions (Last Reviewed 08-Nov-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 14 - 10 Questions (Last Reviewed 07-Nov-2026)