Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 9
Question 80
A government agency needs to delegate read-only firewall inventory to auditors without allowing those accounts to install or revise security policies. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: B
The question is set in this situation: A government agency needs to delegate read-only firewall inventory to auditors without allowing those accounts to install or revise security policies. This action/test pair addresses “Plan the FortiManager offline maintenance mode against connectivity requirements”. 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. 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. The case instead calls for: 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.
The question is set in this situation: A government agency needs to delegate read-only firewall inventory to auditors without allowing those accounts to install or revise security policies. 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. Confirm it through this test: 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. 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 question is set in this situation: A government agency needs to delegate read-only firewall inventory to auditors without allowing those accounts to install or revise security policies. The test would be relevant: 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. But the offered implementation—Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance.—addresses “Preserve FortiManager configuration with a tested backup and restore method”. The action needed here is: 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.
The question is set in this situation: A government agency needs to delegate read-only firewall inventory to auditors without allowing those accounts to install or revise security policies. The action is applicable: 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. But its proposed test—Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs.—addresses “Preserve FortiManager configuration with a tested backup and restore method”. This requirement is confirmed instead by: 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.
Question 81
A network services provider is onboarding two hospitals with different firewall policy owners and needs to keep their address objects and operator privileges separate. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: 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: 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.
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: 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.
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: 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.
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. 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. Verify the result with 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.
Question 82
A network services provider is onboarding two hospitals with different firewall policy owners and needs to keep their address objects and operator privileges separate. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: 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. The corresponding implementation 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.
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: 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.
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: 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.
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: 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.
Question 83
A network services provider is onboarding two hospitals with different firewall policy owners and needs to keep their address objects and operator privileges separate. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: B
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: 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.
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. This check is decisive because 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.
Sign in using a scoped analyst and an ADOM administrator, confirm the analyst sees only permitted data and cannot publish or install a test change, and inspect session audit records. That would help test “Coordinate ADOM administrative privileges and multi-administrator sessions”, not the outcome required in this scenario. The relevant acceptance check is: Create 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.
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: 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 84
A network services provider is onboarding two hospitals with different firewall policy owners and needs to keep their address objects and operator privileges separate. Which proposed shortcut most directly risks cross-customer policy exposure after using device organization labels as a substitute for ADOM isolation and should therefore be rejected?
Answer & Explanations
Correct answer: C
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: Put unrelated customers in one root ADOM and assume distinct device-group names automatically provide separate policy databases and administrative authority.
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: Put unrelated customers in one root ADOM and assume distinct device-group names automatically provide separate policy databases and administrative authority.
Put unrelated customers in one root ADOM and assume distinct device-group names automatically provide separate policy databases and administrative authority. The foreseeable failure is cross-customer policy exposure after using device organization labels as a substitute for ADOM isolation. The safer response 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.
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: Put unrelated customers in one root ADOM and assume distinct device-group names automatically provide separate policy databases and administrative authority.
Question 85
A network services provider is onboarding two hospitals with different firewall policy owners and needs to keep their address objects and operator privileges separate. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: C
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—Review device ownership, target ADOM version and object-policy dependencies before moving a registered FortiGate to a different ADOM using the supported FortiManager device-migration procedure.—addresses “Move a registered FortiGate between ADOMs through a supported workflow”. The action needed here is: 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—Move a lab device with an approved maintenance backup, confirm it appears in the new ADOM, review policy import or reassignment and verify its synchronization and installation status.—addresses “Move a registered FortiGate between ADOMs through a supported workflow”. This requirement is confirmed instead by: 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.
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 “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: 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.
Question 86
A multinational retail chain requires independent regional teams to manage approved FortiGate estates without modifying neighboring regions' ADOM policy packages. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: D
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: 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 and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance. This addresses “Preserve FortiManager configuration with a tested backup and restore method”, where the governing principle is: Device and ADOM database contents plus administrator settings are management-plane assets; keeping only a FortiGate running configuration does not provide a full replacement of FortiManager's object and policy records. The stated 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.
Choose the supported ADOM operation and device modes based on whether central FortiManager will own policy packages or inventory and device settings, then test the intended editing and installation workflow. This addresses “Select FortiManager ADOM mode that matches FortiGate and policy responsibilities”, where the governing principle is: ADOM operating choices determine which central policy and device-management functions apply; selecting a more restricted mode cannot be fixed by simply labeling a firewall package as managed. The stated case instead calls for: 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 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. 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. Verify the result with 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.
Question 87
A multinational retail chain requires independent regional teams to manage approved FortiGate estates without modifying neighboring regions' ADOM policy packages. The engineer proposes the following change: 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. Which mechanism explains why it works?
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. 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 corresponding implementation 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.
ADOM operating choices determine which central policy and device-management functions apply; selecting a more restricted mode cannot be fixed by simply labeling a firewall package as managed. That explains “Select FortiManager ADOM mode that matches FortiGate and policy responsibilities”, not the mechanism behind the described change. The relevant principle is: 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.
Device and ADOM database contents plus administrator settings are management-plane assets; keeping only a FortiGate running configuration does not provide a full replacement of FortiManager's object and policy records. That explains “Preserve FortiManager configuration with a tested backup and restore method”, not the mechanism behind the described change. The relevant 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.
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: 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.
Question 88
A multinational retail chain requires independent regional teams to manage approved FortiGate estates without modifying neighboring regions' ADOM policy packages. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: B
Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs. That would help test “Preserve FortiManager configuration with a tested backup and restore method”, not the outcome required in this scenario. The relevant acceptance check is: 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 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. 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. This check is decisive because 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.
Upgrade a disposable test ADOM, inspect its new version and unchanged FortiGate running release, then verify a compatible policy import and installation to a staged gateway. That would help test “Stage an ADOM upgrade independently of an individual FortiGate firmware upgrade”, not the outcome required in this scenario. The relevant acceptance check is: Create 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.
Configure a test ADOM in the intended supported mode, verify which policy-editor, device database and installation operations are exposed, and compare them with a deliberately alternate mode. That would help test “Select FortiManager ADOM mode that matches FortiGate and policy responsibilities”, not the outcome required in this scenario. The relevant acceptance check is: Create 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 89
A multinational retail chain requires independent regional teams to manage approved FortiGate estates without modifying neighboring regions' ADOM policy packages. Which proposed shortcut most directly risks cross-customer policy exposure after using device organization labels as a substitute for ADOM isolation and should therefore be rejected?
Answer & Explanations
Correct answer: D
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: Put unrelated customers in one root ADOM and assume distinct device-group names automatically provide separate policy databases and administrative authority.
Save one screenshot of the policy list and assume every FortiManager administrator, ADOM and workflow record can be reconstructed from managed FortiGate running configurations. That shortcut risks unrecoverable centralized policy and object history when a damaged management appliance lacks a valid tested backup. Here the specific shortcut is: Put unrelated customers in one root ADOM and assume distinct device-group names automatically provide separate policy databases and administrative authority.
Turn on a mode that omits required central policy management and assume FortiManager will still author and install the organization's shared firewall rule base exactly as before. That shortcut risks missing centralized policy functionality after selecting an ADOM management mode inconsistent with operational requirements. Here the specific shortcut is: Put unrelated customers in one root ADOM and assume distinct device-group names automatically provide separate policy databases and administrative authority.
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. Put unrelated customers in one root ADOM and assume distinct device-group names automatically provide separate policy databases and administrative authority. The foreseeable failure is cross-customer policy exposure after using device organization labels as a substitute for ADOM isolation. The safer response 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.
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.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- Fortinet FCP_FMG_AD-7.6 Practice Test 7 - 10 Questions (Last Reviewed 14-Nov-2026)
- 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)