Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 19
Question 180
A national insurer orders branch equipment and wants to stage FortiManager configuration safely without claiming disconnected model devices are live. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: B
The action is applicable: 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. But its proposed test—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.—addresses “Apply a system template to standardize appropriate FortiGate device settings”. This requirement is confirmed instead by: 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.
The question is set in this situation: A national insurer orders branch equipment and wants to stage FortiManager configuration safely without claiming disconnected model devices are live. 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. Confirm it through this 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. 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 test would be relevant: 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. But the offered implementation—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.—addresses “Apply a system template to standardize appropriate FortiGate device settings”. The action needed here is: 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 action/test pair addresses “Move a FortiManager provisioning template between compatible ADOMs safely”. Copy a reviewed system template into another supported ADOM while validating version compatibility, referenced interfaces and device-specific variables before assigning it to the destination tenant. Copy a sample template from an internal lab ADOM to a separate test tenant, compare object references and target compatibility, and test deployment to one noncritical firewall. The case instead calls for: 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.
Question 181
A logistics fleet uses FortiManager templates to standardize DNS and administrator restrictions across geographically distributed FortiGates. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: B
Check FortiManager platform and license device-management capacity against the expected number of registered devices, confirm supported scale and reserve room for HA clusters and planned growth. This addresses “Account for FortiManager managed device capacity and entitlement before expansion”, where the governing principle is: Central management limits are not removed by renaming devices or adding ADOMs; exceeding supported capacity can block new registrations and make a deployment plan operationally invalid. The stated case instead calls for: 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.
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. 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. Verify the result with this test: 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.
Open FortiManager's device revision comparison for an affected FortiGate, identify only the business-relevant lines that diverge, and choose a reviewed restoration rather than reverting all device settings automatically. This addresses “Use FortiManager configuration comparison before restoring a previous gateway revision”, where the governing principle is: Historical revisions provide evidence of particular changes, but reversing unrelated authorized edits can introduce new outages; a selective diagnosis is essential before invoking a broad revert operation. The stated case instead calls for: 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.
Review FortiManager's import wizard report for existing gateway policies, interfaces and dependent objects, resolve missing references and decide whether to preserve or replace local configuration before installing central changes. This addresses “Reconcile an imported configuration report before first FortiManager policy installation”, where the governing principle is: Import moves a snapshot of current FortiGate policy into central management scope; unreadable objects or interface mappings can produce later install errors when local and intended central databases differ. The stated case instead calls for: 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.
Question 182
A logistics fleet uses FortiManager templates to standardize DNS and administrator restrictions across geographically distributed FortiGates. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: A
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 corresponding implementation is: 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.
Central management limits are not removed by renaming devices or adding ADOMs; exceeding supported capacity can block new registrations and make a deployment plan operationally invalid. That explains “Account for FortiManager managed device capacity and entitlement before expansion”, not the mechanism behind the described change. The relevant 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.
Historical revisions provide evidence of particular changes, but reversing unrelated authorized edits can introduce new outages; a selective diagnosis is essential before invoking a broad revert operation. That explains “Use FortiManager configuration comparison before restoring a previous gateway revision”, not the mechanism behind the described change. The relevant 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.
Import moves a snapshot of current FortiGate policy into central management scope; unreadable objects or interface mappings can produce later install errors when local and intended central databases differ. That explains “Reconcile an imported configuration report before first FortiManager policy installation”, not the mechanism behind the described change. The relevant 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.
Question 183
A logistics fleet uses FortiManager templates to standardize DNS and administrator restrictions across geographically distributed FortiGates. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: D
Review current managed-device count and licensing on an authorized FortiManager instance, add a lab device within the approved capacity, and document a scale decision before exceeding it. That would help test “Account for FortiManager managed device capacity and entitlement before expansion”, not the outcome required in this scenario. The relevant acceptance check is: 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.
Import a staging gateway with a known local rule and custom address object, compare the central package and mappings with its running state, and record a reviewed no-surprise install plan. That would help test “Reconcile an imported configuration report before first FortiManager policy installation”, not the outcome required in this scenario. The relevant acceptance check is: 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.
Compare two stored revisions for a lab device with both an intentional description edit and a needed route fix, verify the cause and restore only an approved baseline where appropriate. That would help test “Use FortiManager configuration comparison before restoring a previous gateway revision”, not the outcome required in this scenario. The relevant acceptance check is: 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.
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. This check is decisive because 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.
Question 184
A logistics fleet uses FortiManager templates to standardize DNS and administrator restrictions across geographically distributed FortiGates. Which proposed shortcut most directly risks widespread branch management outages after an unparameterized shared template overwrites unique network settings and should therefore be rejected?
Answer & Explanations
Correct answer: C
Assume creating dozens of ADOMs multiplies a FortiManager appliance's licensed device count indefinitely without purchasing capacity or verifying platform limits. That shortcut risks failed enterprise expansion when central device-management scale is assumed unlimited. Here the specific shortcut is: Copy one gateway's entire network interface configuration blindly to a fleet of remote branches and assume identical static IP addresses cannot create conflicts.
Select the oldest available device revision and force an unrestricted rollback of a branch firewall without checking whether it contains required routing and security updates. That shortcut risks branch connectivity loss after restoring an obsolete configuration in response to one isolated drift symptom. Here the specific shortcut is: Copy one gateway's entire network interface configuration blindly to a fleet of remote branches and assume identical static IP addresses cannot create conflicts.
Copy one gateway's entire network interface configuration blindly to a fleet of remote branches and assume identical static IP addresses cannot create conflicts. The foreseeable failure is widespread branch management outages after an unparameterized shared template overwrites unique network settings. The safer response is: 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.
Install an empty default FortiManager package over a production FortiGate immediately after registration without checking which live rules the import wizard recognized. That shortcut risks unexpected disruption to permitted traffic after uncontrolled replacement of existing firewall rules during onboarding. Here the specific shortcut is: Copy one gateway's entire network interface configuration blindly to a fleet of remote branches and assume identical static IP addresses cannot create conflicts.
Question 185
A logistics fleet uses FortiManager templates to standardize DNS and administrator restrictions across geographically distributed FortiGates. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: D
The test would be relevant: 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. But the offered implementation—Review FortiManager's import wizard report for existing gateway policies, interfaces and dependent objects, resolve missing references and decide whether to preserve or replace local configuration before installing central changes.—addresses “Reconcile an imported configuration report before first FortiManager policy installation”. The action needed here is: 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.
The action is applicable: 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. But its proposed test—Import a staging gateway with a known local rule and custom address object, compare the central package and mappings with its running state, and record a reviewed no-surprise install plan.—addresses “Reconcile an imported configuration report before first FortiManager policy installation”. This requirement is confirmed instead by: 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.
This action/test pair addresses “Account for FortiManager managed device capacity and entitlement before expansion”. Check FortiManager platform and license device-management capacity against the expected number of registered devices, confirm supported scale and reserve room for HA clusters and planned growth. Review current managed-device count and licensing on an authorized FortiManager instance, add a lab device within the approved capacity, and document a scale decision before exceeding it. The case instead calls for: 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.
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. Confirm it through this test: 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. 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.
Question 186
A hospital network is rolling out consistent settings but each clinic gateway has a different WAN configuration and must avoid duplicate addresses. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: C
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: 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.
When a FortiGate initiates management to FortiManager, verify the configured central-management target, interface administrative access, routing and permitted FGFM session before changing unrelated firewall security policy. This addresses “Troubleshoot FortiGate initiated registration using correct FGFM reachability”, where the governing principle is: FortiGate and FortiManager require a supported FGFM control-plane connection; ordinary internet connectivity or reachability to the HTTPS login page does not establish device registration and configuration synchronization. The stated case instead calls for: 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.
The question is set in this situation: A hospital network is rolling out consistent settings but each clinic gateway has a different WAN configuration and must avoid duplicate addresses. 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. 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. Verify the result with this test: 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.
Read the actual FortiManager script task log and device-side command output, identify target authentication, mode or unsupported syntax problems, and rerun only after repairing the demonstrated issue. This addresses “Investigate a FortiManager script failure using per-device task results”, where the governing principle is: A global task may include successful and failed targets; executing the same script repeatedly without examining the FortiGate error can introduce duplicate changes while leaving the real issue unresolved. The stated case instead calls for: 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.
Question 187
A hospital network is rolling out consistent settings but each clinic gateway has a different WAN configuration and must avoid duplicate addresses. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: A
The question is set in this situation: A hospital network is rolling out consistent settings but each clinic gateway has a different WAN configuration and must avoid duplicate addresses. 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 corresponding implementation is: 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.
FortiGate and FortiManager require a supported FGFM control-plane connection; ordinary internet connectivity or reachability to the HTTPS login page does not establish device registration and configuration synchronization. That explains “Troubleshoot FortiGate initiated registration using correct FGFM reachability”, not the mechanism behind the described change. The relevant 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.
A global task may include successful and failed targets; executing the same script repeatedly without examining the FortiGate error can introduce duplicate changes while leaving the real issue unresolved. That explains “Investigate a FortiManager script failure using per-device task results”, not the mechanism behind the described change. The relevant 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.
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: 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.
Question 188
A hospital network is rolling out consistent settings but each clinic gateway has a different WAN configuration and must avoid duplicate addresses. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: B
Trigger a controlled unsupported command on one staging FortiGate, locate the failed command and status in FortiManager task output, correct it and prove a narrow retry succeeds. That would help test “Investigate a FortiManager script failure using per-device task results”, not the outcome required in this scenario. The relevant acceptance check is: 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 question is set in this situation: A hospital network is rolling out consistent settings but each clinic gateway has a different WAN configuration and must avoid duplicate addresses. 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. This check is decisive because 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.
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: 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.
From a staged FortiGate inspect its configured FortiManager address and FGFM connectivity, view the incoming authorization request on FortiManager, and confirm registration only after approval. That would help test “Troubleshoot FortiGate initiated registration using correct FGFM reachability”, not the outcome required in this scenario. The relevant acceptance check is: 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.
Question 189
A hospital network is rolling out consistent settings but each clinic gateway has a different WAN configuration and must avoid duplicate addresses. Which proposed shortcut most directly risks widespread branch management outages after an unparameterized shared template overwrites unique network settings and should therefore be rejected?
Answer & Explanations
Correct answer: D
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: Copy one gateway's entire network interface configuration blindly to a fleet of remote branches and assume identical static IP addresses cannot create conflicts.
Ignore all script execution logs and rerun a failed bulk configuration job against every branch until the central dashboard stops displaying a warning. That shortcut risks repeated undesired changes and persistent failures from treating a script task error as a harmless notification. Here the specific shortcut is: Copy one gateway's entire network interface configuration blindly to a fleet of remote branches and assume identical static IP addresses cannot create conflicts.
Open unrelated browser ports across the network and assume any FortiGate that can ping the FortiManager management IP has already enrolled in central management. That shortcut risks failed device enrollment despite apparent IP reachability because the FGFM channel or authorization was not established. Here the specific shortcut is: Copy one gateway's entire network interface configuration blindly to a fleet of remote branches and assume identical static IP addresses cannot create conflicts.
The question is set in this situation: A hospital network is rolling out consistent settings but each clinic gateway has a different WAN configuration and must avoid duplicate addresses. Copy one gateway's entire network interface configuration blindly to a fleet of remote branches and assume identical static IP addresses cannot create conflicts. The foreseeable failure is widespread branch management outages after an unparameterized shared template overwrites unique network settings. The safer response is: 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.
Question 190
A hospital network is rolling out consistent settings but each clinic gateway has a different WAN configuration and must avoid duplicate addresses. 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 hospital network is rolling out consistent settings but each clinic gateway has a different WAN configuration and must avoid duplicate addresses. 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. Confirm it through this test: 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. 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.
This action/test pair addresses “Create a model device for a FortiGate not yet physically connected”. 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. 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. The case instead calls for: 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.
The action is applicable: 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. But its proposed test—From a staged FortiGate inspect its configured FortiManager address and FGFM connectivity, view the incoming authorization request on FortiManager, and confirm registration only after approval.—addresses “Troubleshoot FortiGate initiated registration using correct FGFM reachability”. This requirement is confirmed instead by: 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 test would be relevant: 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. But the offered implementation—When a FortiGate initiates management to FortiManager, verify the configured central-management target, interface administrative access, routing and permitted FGFM session before changing unrelated firewall security policy.—addresses “Troubleshoot FortiGate initiated registration using correct FGFM reachability”. The action needed here is: 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.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- 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)
- Fortinet FCP_FMG_AD-7.6 Practice Test 19 - 10 Questions (Last Reviewed 02-Nov-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 20 - 10 Questions (Last Reviewed 01-Nov-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 21 - 10 Questions (Last Reviewed 31-Oct-2026)