Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 16
Question 150
An MSP operates mixed-version customer estates and wants a change plan that proves which operations modify the FortiManager database versus firewall firmware. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: B
The action is applicable: Use the documented FortiManager ADOM upgrade and version-migration workflow with a prechange backup, check supported target firmware ranges, and explicitly distinguish ADOM schema conversion from installing FortiOS on firewalls. But its proposed test—Create a benign object and policy revision in a lab ADOM, record protected backup and revision IDs, perform a controlled rollback test and compare prechange objects and policy packages.—addresses “Restore FortiManager ADOM content after a controlled management change”. This requirement is confirmed instead by: Upgrade a disposable test ADOM, inspect its new version and unchanged FortiGate running release, then verify a compatible policy import and installation to a staged gateway.
The question is set in this situation: An MSP operates mixed-version customer estates and wants a change plan that proves which operations modify the FortiManager database versus firewall firmware. Use the documented FortiManager ADOM upgrade and version-migration workflow with a prechange backup, check supported target firmware ranges, and explicitly distinguish ADOM schema conversion from installing FortiOS on firewalls. Confirm it through this test: Upgrade a disposable test ADOM, inspect its new version and unchanged FortiGate running release, then verify a compatible policy import and installation to a staged gateway. Changing an ADOM database version does not itself reboot or upgrade every FortiGate; management compatibility and gateway firmware are separate coordinated changes that require their own installation and verification.
The test would be relevant: Upgrade a disposable test ADOM, inspect its new version and unchanged FortiGate running release, then verify a compatible policy import and installation to a staged gateway. But the offered implementation—Capture a full protected FortiManager backup and relevant ADOM revision before an invasive configuration or ADOM upgrade, and test a supported recovery path instead of attempting to rebuild deleted policies from memory.—addresses “Restore FortiManager ADOM content after a controlled management change”. The action needed here is: Use the documented FortiManager ADOM upgrade and version-migration workflow with a prechange backup, check supported target firmware ranges, and explicitly distinguish ADOM schema conversion from installing FortiOS on firewalls.
This action/test pair addresses “Divide a multi-customer FortiManager environment into appropriate ADOMs”. Configure supported administrative domains that match independent customers or security jurisdictions, assign managed devices and administrators to correct ADOMs, and verify object and policy isolation. Create two lab ADOMs with separate administrators and policy packages, verify a device and object from the first are unavailable for modification from the second, and document global policy exceptions. The case instead calls for: Use the documented FortiManager ADOM upgrade and version-migration workflow with a prechange backup, check supported target firmware ranges, and explicitly distinguish ADOM schema conversion from installing FortiOS on firewalls.
Question 151
A bank is onboarding a newly deployed branch FortiGate and needs proof that it is communicating with the correct FortiManager ADOM. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: A
Use the supported Add Device workflow with the intended ADOM, correct management IP and authenticated FortiGate authorization, confirm FGFM communication and review the initial import report before declaring it managed. A named FortiGate entry is not equivalent to an authenticated live management relationship; FortiManager must establish supported communications and reconcile the device configuration with the central database. Verify the result with this test: Register a staging firewall with FortiManager access allowed, inspect the device's serial number and managed status, retrieve its initial configuration and confirm the intended ADOM owns it.
Use a supported FortiManager model device entry with an approved blueprint and correct serial or authorization data, then bind the physical FortiGate when it comes online and reconcile actual configuration. This addresses “Create a model device for a FortiGate not yet physically connected”, where the governing principle is: A model device is a planned representation for preprovisioning and does not prove the future hardware is reachable; matching the real device securely is required before intended settings can be pushed and verified. The stated case instead calls for: Use the supported Add Device workflow with the intended ADOM, correct management IP and authenticated FortiGate authorization, confirm FGFM communication and review the initial import report before declaring it managed.
Use the supported Retrieve Config operation for an approved device and compare the retrieved snapshot with the existing device database and known revision history before deciding whether to adopt differences. This addresses “Retrieve the running FortiGate configuration to populate a new FortiManager revision”, where the governing principle is: Configuration retrieval observes actual device-side state and can create a new FortiManager revision; it does not automatically prove every locally changed setting was authorized or should become central policy. The stated case instead calls for: Use the supported Add Device workflow with the intended ADOM, correct management IP and authenticated FortiGate authorization, confirm FGFM communication and review the initial import report before declaring it managed.
Create a reviewed FortiManager system template for common permitted device settings, associate it with an approved device group, and validate per-device variables before a controlled install. This addresses “Apply a system template to standardize appropriate FortiGate device settings”, where the governing principle is: Provisioning templates support consistent settings across many devices, but differing interfaces and regional network addresses still require device-aware mappings rather than blind identical values. The stated case instead calls for: Use the supported Add Device workflow with the intended ADOM, correct management IP and authenticated FortiGate authorization, confirm FGFM communication and review the initial import report before declaring it managed.
Question 152
A bank is onboarding a newly deployed branch FortiGate and needs proof that it is communicating with the correct FortiManager ADOM. The engineer proposes the following change: Use the supported Add Device workflow with the intended ADOM, correct management IP and authenticated FortiGate authorization, confirm FGFM communication and review the initial import report before declaring it managed. Which mechanism explains why it works?
Answer & Explanations
Correct answer: D
A model device is a planned representation for preprovisioning and does not prove the future hardware is reachable; matching the real device securely is required before intended settings can be pushed and verified. That explains “Create a model device for a FortiGate not yet physically connected”, not the mechanism behind the described change. The relevant principle is: A named FortiGate entry is not equivalent to an authenticated live management relationship; FortiManager must establish supported communications and reconcile the device configuration with the central database.
Configuration retrieval observes actual device-side state and can create a new FortiManager revision; it does not automatically prove every locally changed setting was authorized or should become central policy. That explains “Retrieve the running FortiGate configuration to populate a new FortiManager revision”, not the mechanism behind the described change. The relevant principle is: A named FortiGate entry is not equivalent to an authenticated live management relationship; FortiManager must establish supported communications and reconcile the device configuration with the central database.
Provisioning templates support consistent settings across many devices, but differing interfaces and regional network addresses still require device-aware mappings rather than blind identical values. That explains “Apply a system template to standardize appropriate FortiGate device settings”, not the mechanism behind the described change. The relevant principle is: A named FortiGate entry is not equivalent to an authenticated live management relationship; FortiManager must establish supported communications and reconcile the device configuration with the central database.
A named FortiGate entry is not equivalent to an authenticated live management relationship; FortiManager must establish supported communications and reconcile the device configuration with the central database. The corresponding implementation is: Use the supported Add Device workflow with the intended ADOM, correct management IP and authenticated FortiGate authorization, confirm FGFM communication and review the initial import report before declaring it managed.
Question 153
A bank is onboarding a newly deployed branch FortiGate and needs proof that it is communicating with the correct FortiManager ADOM. After implementing this change—Use the supported Add Device workflow with the intended ADOM, correct management IP and authenticated FortiGate authorization, confirm FGFM communication and review the initial import report before declaring it managed.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: B
Change a harmless test setting directly on a staging FortiGate, retrieve configuration in FortiManager, inspect the revised record and document whether to accept or revert the local change. That would help test “Retrieve the running FortiGate configuration to populate a new FortiManager revision”, not the outcome required in this scenario. The relevant acceptance check is: Register a staging firewall with FortiManager access allowed, inspect the device's serial number and managed status, retrieve its initial configuration and confirm the intended ADOM owns it.
Register a staging firewall with FortiManager access allowed, inspect the device's serial number and managed status, retrieve its initial configuration and confirm the intended ADOM owns it. This check is decisive because a named FortiGate entry is not equivalent to an authenticated live management relationship; FortiManager must establish supported communications and reconcile the device configuration with the central database.
Assign a template to two staging FortiGates with different management addresses, preview intended changes, install only approved settings and confirm each device retains its unique required identity. That would help test “Apply a system template to standardize appropriate FortiGate device settings”, not the outcome required in this scenario. The relevant acceptance check is: Register a staging firewall with FortiManager access allowed, inspect the device's serial number and managed status, retrieve its initial configuration and confirm the intended ADOM owns it.
Create a model FortiGate in a lab ADOM, associate a provisioning template, attach a matching simulated device identity, and confirm it transitions to live managed status without unexpected object differences. That would help test “Create a model device for a FortiGate not yet physically connected”, not the outcome required in this scenario. The relevant acceptance check is: Register a staging firewall with FortiManager access allowed, inspect the device's serial number and managed status, retrieve its initial configuration and confirm the intended ADOM owns it.
Question 154
A bank is onboarding a newly deployed branch FortiGate and needs proof that it is communicating with the correct FortiManager ADOM. Which proposed shortcut most directly risks unmanaged firewall falsely counted as centrally protected after its FortiManager record was never authenticated and should therefore be rejected?
Answer & Explanations
Correct answer: C
Press Retrieve Config after an unreviewed local change and declare all modifications approved corporate policy merely because the management database now contains them. That shortcut risks unauthorized local changes legitimized when retrieved device configuration is mistaken for reviewed intent. Here the specific shortcut is: Create an arbitrary offline device row with a plausible hostname and mark registration successful without reaching the FortiGate or checking management authorization.
Record an unverified wildcard model entry and install firewall policies as though its network interfaces and serial number had already been checked against deployed hardware. That shortcut risks misapplied branch provisioning when placeholder device identity is mistaken for authenticated installed equipment. Here the specific shortcut is: Create an arbitrary offline device row with a plausible hostname and mark registration successful without reaching the FortiGate or checking management authorization.
Create an arbitrary offline device row with a plausible hostname and mark registration successful without reaching the FortiGate or checking management authorization. The foreseeable failure is unmanaged firewall falsely counted as centrally protected after its FortiManager record was never authenticated. The safer response is: Use the supported Add Device workflow with the intended ADOM, correct management IP and authenticated FortiGate authorization, confirm FGFM communication and review the initial import report before declaring it managed.
Copy one gateway's entire network interface configuration blindly to a fleet of remote branches and assume identical static IP addresses cannot create conflicts. That shortcut risks widespread branch management outages after an unparameterized shared template overwrites unique network settings. Here the specific shortcut is: Create an arbitrary offline device row with a plausible hostname and mark registration successful without reaching the FortiGate or checking management authorization.
Question 155
A bank is onboarding a newly deployed branch FortiGate and needs proof that it is communicating with the correct FortiManager ADOM. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: A
Use the supported Add Device workflow with the intended ADOM, correct management IP and authenticated FortiGate authorization, confirm FGFM communication and review the initial import report before declaring it managed. Confirm it through this test: Register a staging firewall with FortiManager access allowed, inspect the device's serial number and managed status, retrieve its initial configuration and confirm the intended ADOM owns it. A named FortiGate entry is not equivalent to an authenticated live management relationship; FortiManager must establish supported communications and reconcile the device configuration with the central database.
The test would be relevant: Register a staging firewall with FortiManager access allowed, inspect the device's serial number and managed status, retrieve its initial configuration and confirm the intended ADOM owns it. But the offered implementation—Use a supported FortiManager model device entry with an approved blueprint and correct serial or authorization data, then bind the physical FortiGate when it comes online and reconcile actual configuration.—addresses “Create a model device for a FortiGate not yet physically connected”. The action needed here is: Use the supported Add Device workflow with the intended ADOM, correct management IP and authenticated FortiGate authorization, confirm FGFM communication and review the initial import report before declaring it managed.
This action/test pair addresses “Apply a system template to standardize appropriate FortiGate device settings”. Create a reviewed FortiManager system template for common permitted device settings, associate it with an approved device group, and validate per-device variables before a controlled install. Assign a template to two staging FortiGates with different management addresses, preview intended changes, install only approved settings and confirm each device retains its unique required identity. The case instead calls for: Use the supported Add Device workflow with the intended ADOM, correct management IP and authenticated FortiGate authorization, confirm FGFM communication and review the initial import report before declaring it managed.
The action is applicable: Use the supported Add Device workflow with the intended ADOM, correct management IP and authenticated FortiGate authorization, confirm FGFM communication and review the initial import report before declaring it managed. But its proposed test—Create a model FortiGate in a lab ADOM, associate a provisioning template, attach a matching simulated device identity, and confirm it transitions to live managed status without unexpected object differences.—addresses “Create a model device for a FortiGate not yet physically connected”. This requirement is confirmed instead by: Register a staging firewall with FortiManager access allowed, inspect the device's serial number and managed status, retrieve its initial configuration and confirm the intended ADOM owns it.
Question 156
A university is adding a laboratory firewall and wants the operator to distinguish a pending device inventory entry from a registered managed device. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: D
Discover a FortiGate HA cluster using supported FortiManager procedures, verify cluster identity and member status, and use an appropriate cluster target when managing shared policy and device configuration. This addresses “Register and manage a FortiGate HA cluster as a consistent logical target”, where the governing principle is: Multiple FortiGate HA member serial numbers do not necessarily represent independent production policy targets; a cluster has shared identity, synchronization state and supported installation behavior that must be understood. The stated case instead calls for: Use the supported Add Device workflow with the intended ADOM, correct management IP and authenticated FortiGate authorization, confirm FGFM communication and review the initial import report before declaring it managed.
Author a reviewed FortiManager CLI script using syntax compatible with the target FortiOS version, choose explicit devices or a restricted device group, and validate the intended scope before executing. This addresses “Execute a FortiManager CLI script only on approved FortiGate targets”, where the governing principle is: Central scripts can change many managed firewalls efficiently, so a correct command still creates risk if it runs against the wrong ADOM, firmware version or device selection. The stated case instead calls for: Use the supported Add Device workflow with the intended ADOM, correct management IP and authenticated FortiGate authorization, confirm FGFM communication and review the initial import report before declaring it managed.
Create FortiManager device groups for operational rollouts inside an approved ADOM, use them as scheduling or target aids, and maintain ADOM-level access controls separately. This addresses “Organize registered FortiGates into device groups without confusing ADOM isolation”, where the governing principle is: Device groups help administrators organize and select devices but do not replace ADOM database boundaries; a shared group label cannot prevent unauthorized object modification across customers. The stated case instead calls for: Use the supported Add Device workflow with the intended ADOM, correct management IP and authenticated FortiGate authorization, confirm FGFM communication and review the initial import report before declaring it managed.
The question is set in this situation: A university is adding a laboratory firewall and wants the operator to distinguish a pending device inventory entry from a registered managed device. Use the supported Add Device workflow with the intended ADOM, correct management IP and authenticated FortiGate authorization, confirm FGFM communication and review the initial import report before declaring it managed. A named FortiGate entry is not equivalent to an authenticated live management relationship; FortiManager must establish supported communications and reconcile the device configuration with the central database. Verify the result with this test: Register a staging firewall with FortiManager access allowed, inspect the device's serial number and managed status, retrieve its initial configuration and confirm the intended ADOM owns it.
Question 157
A university is adding a laboratory firewall and wants the operator to distinguish a pending device inventory entry from a registered managed device. The engineer proposes the following change: Use the supported Add Device workflow with the intended ADOM, correct management IP and authenticated FortiGate authorization, confirm FGFM communication and review the initial import report before declaring it managed. Which mechanism explains why it works?
Answer & Explanations
Correct answer: D
Central scripts can change many managed firewalls efficiently, so a correct command still creates risk if it runs against the wrong ADOM, firmware version or device selection. That explains “Execute a FortiManager CLI script only on approved FortiGate targets”, not the mechanism behind the described change. The relevant principle is: A named FortiGate entry is not equivalent to an authenticated live management relationship; FortiManager must establish supported communications and reconcile the device configuration with the central database.
Multiple FortiGate HA member serial numbers do not necessarily represent independent production policy targets; a cluster has shared identity, synchronization state and supported installation behavior that must be understood. That explains “Register and manage a FortiGate HA cluster as a consistent logical target”, not the mechanism behind the described change. The relevant principle is: A named FortiGate entry is not equivalent to an authenticated live management relationship; FortiManager must establish supported communications and reconcile the device configuration with the central database.
Device groups help administrators organize and select devices but do not replace ADOM database boundaries; a shared group label cannot prevent unauthorized object modification across customers. That explains “Organize registered FortiGates into device groups without confusing ADOM isolation”, not the mechanism behind the described change. The relevant principle is: A named FortiGate entry is not equivalent to an authenticated live management relationship; FortiManager must establish supported communications and reconcile the device configuration with the central database.
The question is set in this situation: A university is adding a laboratory firewall and wants the operator to distinguish a pending device inventory entry from a registered managed device. A named FortiGate entry is not equivalent to an authenticated live management relationship; FortiManager must establish supported communications and reconcile the device configuration with the central database. The corresponding implementation is: Use the supported Add Device workflow with the intended ADOM, correct management IP and authenticated FortiGate authorization, confirm FGFM communication and review the initial import report before declaring it managed.
Question 158
A university is adding a laboratory firewall and wants the operator to distinguish a pending device inventory entry from a registered managed device. After implementing this change—Use the supported Add Device workflow with the intended ADOM, correct management IP and authenticated FortiGate authorization, confirm FGFM communication and review the initial import report before declaring it managed.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: C
Run a harmless diagnostic or reversible configuration script on two lab FortiGates, inspect the target list and per-device status, and confirm an unselected gateway has no resulting change. That would help test “Execute a FortiManager CLI script only on approved FortiGate targets”, not the outcome required in this scenario. The relevant acceptance check is: Register a staging firewall with FortiManager access allowed, inspect the device's serial number and managed status, retrieve its initial configuration and confirm the intended ADOM owns it.
Build a sample group of three staged branch FortiGates, target a harmless approved update, and show an administrator outside the ADOM remains unable to edit the group's policy package. That would help test “Organize registered FortiGates into device groups without confusing ADOM isolation”, not the outcome required in this scenario. The relevant acceptance check is: Register a staging firewall with FortiManager access allowed, inspect the device's serial number and managed status, retrieve its initial configuration and confirm the intended ADOM owns it.
The question is set in this situation: A university is adding a laboratory firewall and wants the operator to distinguish a pending device inventory entry from a registered managed device. Register a staging firewall with FortiManager access allowed, inspect the device's serial number and managed status, retrieve its initial configuration and confirm the intended ADOM owns it. This check is decisive because a named FortiGate entry is not equivalent to an authenticated live management relationship; FortiManager must establish supported communications and reconcile the device configuration with the central database.
Add a staged two-member FortiGate cluster, inspect primary and secondary member information, install one harmless policy change through the proper managed target, and check both members remain healthy. That would help test “Register and manage a FortiGate HA cluster as a consistent logical target”, not the outcome required in this scenario. The relevant acceptance check is: Register a staging firewall with FortiManager access allowed, inspect the device's serial number and managed status, retrieve its initial configuration and confirm the intended ADOM owns it.
Question 159
A university is adding a laboratory firewall and wants the operator to distinguish a pending device inventory entry from a registered managed device. Which proposed shortcut most directly risks unmanaged firewall falsely counted as centrally protected after its FortiManager record was never authenticated and should therefore be rejected?
Answer & Explanations
Correct answer: B
Treat each HA member as an unrelated branch firewall and independently apply conflicting production policies without checking cluster state or central management identity. That shortcut risks cluster synchronization conflict and traffic disruption caused by independently managing devices that belong to one HA cluster. Here the specific shortcut is: Create an arbitrary offline device row with a plausible hostname and mark registration successful without reaching the FortiGate or checking management authorization.
The question is set in this situation: A university is adding a laboratory firewall and wants the operator to distinguish a pending device inventory entry from a registered managed device. Create an arbitrary offline device row with a plausible hostname and mark registration successful without reaching the FortiGate or checking management authorization. The foreseeable failure is unmanaged firewall falsely counted as centrally protected after its FortiManager record was never authenticated. The safer response is: Use the supported Add Device workflow with the intended ADOM, correct management IP and authenticated FortiGate authorization, confirm FGFM communication and review the initial import report before declaring it managed.
Schedule an unreviewed administrator-level CLI script against every FortiManager device across all customers because it worked once on a single test box. That shortcut risks mass configuration drift after a valid command is executed against unapproved devices. Here the specific shortcut is: Create an arbitrary offline device row with a plausible hostname and mark registration successful without reaching the FortiGate or checking management authorization.
Place two tenants in a single unrestricted ADOM and claim that creating separate device groups guarantees legal customer data isolation and separate object administration. That shortcut risks tenant policy exposure after incorrectly treating FortiManager device groups as security boundaries. Here the specific shortcut is: Create an arbitrary offline device row with a plausible hostname and mark registration successful without reaching the FortiGate or checking management authorization.
Question 160
A university is adding a laboratory firewall and wants the operator to distinguish a pending device inventory entry from a registered managed device. 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 university is adding a laboratory firewall and wants the operator to distinguish a pending device inventory entry from a registered managed device. Use the supported Add Device workflow with the intended ADOM, correct management IP and authenticated FortiGate authorization, confirm FGFM communication and review the initial import report before declaring it managed. Confirm it through this test: Register a staging firewall with FortiManager access allowed, inspect the device's serial number and managed status, retrieve its initial configuration and confirm the intended ADOM owns it. A named FortiGate entry is not equivalent to an authenticated live management relationship; FortiManager must establish supported communications and reconcile the device configuration with the central database.
The test would be relevant: Register a staging firewall with FortiManager access allowed, inspect the device's serial number and managed status, retrieve its initial configuration and confirm the intended ADOM owns it. But the offered implementation—Discover a FortiGate HA cluster using supported FortiManager procedures, verify cluster identity and member status, and use an appropriate cluster target when managing shared policy and device configuration.—addresses “Register and manage a FortiGate HA cluster as a consistent logical target”. The action needed here is: Use the supported Add Device workflow with the intended ADOM, correct management IP and authenticated FortiGate authorization, confirm FGFM communication and review the initial import report before declaring it managed.
This action/test pair addresses “Organize registered FortiGates into device groups without confusing ADOM isolation”. Create FortiManager device groups for operational rollouts inside an approved ADOM, use them as scheduling or target aids, and maintain ADOM-level access controls separately. Build a sample group of three staged branch FortiGates, target a harmless approved update, and show an administrator outside the ADOM remains unable to edit the group's policy package. The case instead calls for: Use the supported Add Device workflow with the intended ADOM, correct management IP and authenticated FortiGate authorization, confirm FGFM communication and review the initial import report before declaring it managed.
The action is applicable: Use the supported Add Device workflow with the intended ADOM, correct management IP and authenticated FortiGate authorization, confirm FGFM communication and review the initial import report before declaring it managed. But its proposed test—Add a staged two-member FortiGate cluster, inspect primary and secondary member information, install one harmless policy change through the proper managed target, and check both members remain healthy.—addresses “Register and manage a FortiGate HA cluster as a consistent logical target”. This requirement is confirmed instead by: Register a staging firewall with FortiManager access allowed, inspect the device's serial number and managed status, retrieve its initial configuration and confirm the intended ADOM owns it.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- Fortinet FCP_FMG_AD-7.6 Practice Test 14 - 10 Questions (Last Reviewed 07-Nov-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 15 - 10 Questions (Last Reviewed 06-Nov-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 16 - 10 Questions (Last Reviewed 05-Nov-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 17 - 10 Questions (Last Reviewed 04-Nov-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 18 - 10 Questions (Last Reviewed 03-Nov-2026)