Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 10
Question 90
A multinational retail chain requires independent regional teams to manage approved FortiGate estates without modifying neighboring regions' ADOM policy packages. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: A
The question is set in this situation: A multinational retail chain requires independent regional teams to manage approved FortiGate estates without modifying neighboring regions' ADOM policy packages. 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. Confirm it through this test: 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. 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.
This action/test pair addresses “Select FortiManager ADOM mode that matches FortiGate and policy responsibilities”. 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. 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. The case instead calls for: 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.
The test would be relevant: 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. 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: 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.
The action is applicable: 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. 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: 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.
Question 91
A managed services provider is creating a monitoring-oriented ADOM and wants to avoid claiming it supports the same central policy workflow as a full management ADOM. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: B
Use the documented FortiManager JSON-RPC API with an appropriately authorized automation identity, correct session handling and supported methods to read approved device or policy-package data before attempting a change. This addresses “Authenticate and scope FortiManager JSON API operations using the correct methods”, where the governing principle is: FortiManager management API requests use defined endpoints, JSON-RPC methods and session or token authorization; a successful HTTP transport response alone does not prove an internal API operation succeeded or was permitted. The stated case instead calls for: 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.
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. 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. Verify the result with this 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.
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: 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.
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: 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.
Question 92
A managed services provider is creating a monitoring-oriented ADOM and wants to avoid claiming it supports the same central policy workflow as a full management ADOM. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: C
FortiManager management API requests use defined endpoints, JSON-RPC methods and session or token authorization; a successful HTTP transport response alone does not prove an internal API operation succeeded or was permitted. That explains “Authenticate and scope FortiManager JSON API operations using the correct methods”, not the mechanism behind the described change. The relevant 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.
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 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.
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 corresponding implementation is: 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.
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: 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.
Question 93
A managed services provider is creating a monitoring-oriented ADOM and wants to avoid claiming it supports the same central policy workflow as a full management ADOM. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: D
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: 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.
Run a read-only API request for the allowed test ADOM installation target, inspect both transport and JSON result status, and prove the same identity cannot change an excluded ADOM. That would help test “Authenticate and scope FortiManager JSON API operations using the correct methods”, not the outcome required in this scenario. The relevant acceptance check is: 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.
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: 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.
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. This check is decisive because 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.
Question 94
A managed services provider is creating a monitoring-oriented ADOM and wants to avoid claiming it supports the same central policy workflow as a full management ADOM. Which proposed shortcut most directly risks missing centralized policy functionality after selecting an ADOM management mode inconsistent with operational requirements and should therefore be rejected?
Answer & Explanations
Correct answer: 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: 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.
Send unauthenticated arbitrary HTTP PUT bodies to the FortiManager root URL and assume every HTTP 200 result means an approved configuration change was installed. That shortcut risks misreported automation success or cross-domain configuration access caused by ignoring FortiManager API authorization and status fields. Here the specific shortcut is: 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.
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. The foreseeable failure is missing centralized policy functionality after selecting an ADOM management mode inconsistent with operational requirements. The safer response is: 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.
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: 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.
Question 95
A managed services provider is creating a monitoring-oriented ADOM and wants to avoid claiming it supports the same central policy workflow as a full management ADOM. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: 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: 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.
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. Confirm it through this 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. 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 test would be relevant: 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. 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: 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.
The action is applicable: 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. 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: 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.
Question 96
A university migrates from device-only oversight to standardized policy packages and needs an ADOM mode change supported by a clear validation plan. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: A
The question is set in this situation: A university migrates from device-only oversight to standardized policy packages and needs an ADOM mode change supported by a clear validation plan. 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. 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. Verify the result with this 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.
Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation. This addresses “Explain central management versus FortiGate enforcement responsibilities”, where the governing principle is: FortiManager coordinates intended configuration and deployment to registered FortiGates; the managed firewall continues packet processing under its installed policy even if the management appliance is unavailable. The stated case instead calls for: 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.
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: 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.
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: 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.
Question 97
A university migrates from device-only oversight to standardized policy packages and needs an ADOM mode change supported by a clear validation plan. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: D
FortiManager coordinates intended configuration and deployment to registered FortiGates; the managed firewall continues packet processing under its installed policy even if the management appliance is unavailable. That explains “Explain central management versus FortiGate enforcement responsibilities”, not the mechanism behind the described change. The relevant 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.
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: 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.
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 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 question is set in this situation: A university migrates from device-only oversight to standardized policy packages and needs an ADOM mode change supported by a clear validation plan. 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 corresponding implementation is: 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.
Question 98
A university migrates from device-only oversight to standardized policy packages and needs an ADOM mode change supported by a clear validation plan. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: C
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: 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.
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: 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.
The question is set in this situation: A university migrates from device-only oversight to standardized policy packages and needs an ADOM mode change supported by a clear validation plan. 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. This check is decisive because 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.
Disconnect the management lab briefly, verify a FortiGate still enforces its previously installed security policy, reconnect FGFM management, and perform a documented policy installation from FortiManager. That would help test “Explain central management versus FortiGate enforcement responsibilities”, not the outcome required in this scenario. The relevant acceptance check is: 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.
Question 99
A university migrates from device-only oversight to standardized policy packages and needs an ADOM mode change supported by a clear validation plan. Which proposed shortcut most directly risks missing centralized policy functionality after selecting an ADOM management mode inconsistent with operational requirements and should therefore be rejected?
Answer & Explanations
Correct answer: A
The question is set in this situation: A university migrates from device-only oversight to standardized policy packages and needs an ADOM mode change supported by a clear validation plan. 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. The foreseeable failure is missing centralized policy functionality after selecting an ADOM management mode inconsistent with operational requirements. The safer response is: 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.
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: 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.
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: 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.
Treat the FortiManager VM as the inline packet-forwarding firewall and move the production traffic gateway off the network because its manager is online. That shortcut risks loss of actual traffic filtering caused by confusing central configuration control with an enforcement gateway. Here the specific shortcut is: 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.
Question 100
A university migrates from device-only oversight to standardized policy packages and needs an ADOM mode change supported by a clear validation plan. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: B
The action is applicable: 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. But its proposed test—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.—addresses “Divide a multi-customer FortiManager environment into appropriate ADOMs”. This requirement is confirmed instead by: 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.
The question is set in this situation: A university migrates from device-only oversight to standardized policy packages and needs an ADOM mode change supported by a clear validation plan. 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. Confirm it through this 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. 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.
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: 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.
The test would be relevant: 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. But the offered implementation—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.—addresses “Divide a multi-customer FortiManager environment into appropriate ADOMs”. The action needed here is: 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.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- Fortinet FCP_FMG_AD-7.6 Practice Test 8 - 10 Questions (Last Reviewed 13-Nov-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 9 - 10 Questions (Last Reviewed 12-Nov-2026)
- 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)