Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 35
Question 340
An MSP is reconciling one customer firewall that differs from the FortiManager device database despite having a recent successful policy installation. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: C
The action is applicable: When FortiManager reports a device configuration status of modified or out of sync, compare the central device database, last retrieved revision and actual FortiGate state before deciding whether to retrieve or reinstall. But its proposed test—Create a benign device-side change and an unrelated ADOM object change in a lab, verify which revision histories update and demonstrate independent scope for each recovery decision.—addresses “Distinguish an automatic device configuration revision from an ADOM policy revision”. This requirement is confirmed instead by: Introduce a controlled local configuration change on a test FortiGate, review device status and revision differences, then retrieve or restore as approved and confirm synchronized status.
This action/test pair addresses “Use FortiManager configuration comparison before restoring a previous gateway revision”. 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. 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. The case instead calls for: When FortiManager reports a device configuration status of modified or out of sync, compare the central device database, last retrieved revision and actual FortiGate state before deciding whether to retrieve or reinstall.
The question is set in this situation: An MSP is reconciling one customer firewall that differs from the FortiManager device database despite having a recent successful policy installation. When FortiManager reports a device configuration status of modified or out of sync, compare the central device database, last retrieved revision and actual FortiGate state before deciding whether to retrieve or reinstall. Confirm it through this test: Introduce a controlled local configuration change on a test FortiGate, review device status and revision differences, then retrieve or restore as approved and confirm synchronized status. The FortiManager device database is not identical to every current FortiGate setting until retrieval or installation succeeds; a status indicator alone does not identify which side is authoritative.
The test would be relevant: Introduce a controlled local configuration change on a test FortiGate, review device status and revision differences, then retrieve or restore as approved and confirm synchronized status. But the offered implementation—Inspect the source and timestamp of an automatic FortiManager device configuration revision and compare it with separately managed ADOM revisions so the scope of a rollback is documented accurately.—addresses “Distinguish an automatic device configuration revision from an ADOM policy revision”. The action needed here is: When FortiManager reports a device configuration status of modified or out of sync, compare the central device database, last retrieved revision and actual FortiGate state before deciding whether to retrieve or reinstall.
Question 341
A retail chain wants a common outbound policy on selected store FortiGates but must keep headquarters' separate security controls untouched. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: A
Create a centrally reviewed policy package in the correct ADOM, associate only the intended FortiGate installation targets, and validate per-device interface and object mappings before installation. Policy packages represent centrally managed access-control intent; a rule appearing in the ADOM editor does not prove it was assigned to the correct devices or installed in their running security policy. Verify the result with this test: Build a lab package with one permitted and one denied service, assign two approved gateways, preview and install, then confirm an unrelated test firewall is unchanged.
Edit shared firewall policy objects in the proper ADOM object database and separately examine device-specific configuration records, verifying how policy package installation renders the intended settings on a FortiGate. This addresses “Distinguish the FortiManager ADOM object database from device-level configuration records”, where the governing principle is: ADOM objects and packages express shared policy intent, while device-level databases store target-specific configuration state; a change to one database need not update the live device until installation or retrieval occurs. The stated case instead calls for: Create a centrally reviewed policy package in the correct ADOM, associate only the intended FortiGate installation targets, and validate per-device interface and object mappings before installation.
Set the intended supported installation target or per-policy scope for a FortiManager rule, review how it applies to individual managed FortiGates, and preview each target's resulting policy before committing installation. This addresses “Verify per-policy installation targets rather than relying on package-wide assumptions”, where the governing principle is: One centrally shared package may contain rules relevant only to particular branches; leaving rule targets overly broad can create unintended permissions even when the package assignment itself is correct. The stated case instead calls for: Create a centrally reviewed policy package in the correct ADOM, associate only the intended FortiGate installation targets, and validate per-device interface and object mappings before installation.
After a managed FortiGate is replaced or recovered, verify the new device identity, supported firmware and interface mappings, then perform an approved policy package reinstall and validate actual enforcement. This addresses “Reinstall a known approved FortiManager policy package after device replacement”, where the governing principle is: A previously approved package can restore intended filtering, but changed hardware ports, device serial numbers and target associations may require reconciliation before a safe reinstall. The stated case instead calls for: Create a centrally reviewed policy package in the correct ADOM, associate only the intended FortiGate installation targets, and validate per-device interface and object mappings before installation.
Question 342
A retail chain wants a common outbound policy on selected store FortiGates but must keep headquarters' separate security controls untouched. The engineer proposes the following change: Create a centrally reviewed policy package in the correct ADOM, associate only the intended FortiGate installation targets, and validate per-device interface and object mappings before installation. Which mechanism explains why it works?
Answer & Explanations
Correct answer: B
One centrally shared package may contain rules relevant only to particular branches; leaving rule targets overly broad can create unintended permissions even when the package assignment itself is correct. That explains “Verify per-policy installation targets rather than relying on package-wide assumptions”, not the mechanism behind the described change. The relevant principle is: Policy packages represent centrally managed access-control intent; a rule appearing in the ADOM editor does not prove it was assigned to the correct devices or installed in their running security policy.
Policy packages represent centrally managed access-control intent; a rule appearing in the ADOM editor does not prove it was assigned to the correct devices or installed in their running security policy. The corresponding implementation is: Create a centrally reviewed policy package in the correct ADOM, associate only the intended FortiGate installation targets, and validate per-device interface and object mappings before installation.
A previously approved package can restore intended filtering, but changed hardware ports, device serial numbers and target associations may require reconciliation before a safe reinstall. That explains “Reinstall a known approved FortiManager policy package after device replacement”, not the mechanism behind the described change. The relevant principle is: Policy packages represent centrally managed access-control intent; a rule appearing in the ADOM editor does not prove it was assigned to the correct devices or installed in their running security policy.
ADOM objects and packages express shared policy intent, while device-level databases store target-specific configuration state; a change to one database need not update the live device until installation or retrieval occurs. That explains “Distinguish the FortiManager ADOM object database from device-level configuration records”, not the mechanism behind the described change. The relevant principle is: Policy packages represent centrally managed access-control intent; a rule appearing in the ADOM editor does not prove it was assigned to the correct devices or installed in their running security policy.
Question 343
A retail chain wants a common outbound policy on selected store FortiGates but must keep headquarters' separate security controls untouched. After implementing this change—Create a centrally reviewed policy package in the correct ADOM, associate only the intended FortiGate installation targets, and validate per-device interface and object mappings before installation.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: D
In a lab assign a single branch-specific rule only to one of two package targets, compare the generated firewall configurations and confirm the other gateway does not receive the exception. That would help test “Verify per-policy installation targets rather than relying on package-wide assumptions”, not the outcome required in this scenario. The relevant acceptance check is: Build a lab package with one permitted and one denied service, assign two approved gateways, preview and install, then confirm an unrelated test firewall is unchanged.
Bind a staged replacement FortiGate to its intended FortiManager device entry, preview the existing approved package and install it while testing both permitted and denied representative flows. That would help test “Reinstall a known approved FortiManager policy package after device replacement”, not the outcome required in this scenario. The relevant acceptance check is: Build a lab package with one permitted and one denied service, assign two approved gateways, preview and install, then confirm an unrelated test firewall is unchanged.
Modify a harmless ADOM service object and a separate test device setting, inspect both database views and install only the reviewed policy change while checking the resulting FortiGate state. That would help test “Distinguish the FortiManager ADOM object database from device-level configuration records”, not the outcome required in this scenario. The relevant acceptance check is: Build a lab package with one permitted and one denied service, assign two approved gateways, preview and install, then confirm an unrelated test firewall is unchanged.
Build a lab package with one permitted and one denied service, assign two approved gateways, preview and install, then confirm an unrelated test firewall is unchanged. This check is decisive because policy packages represent centrally managed access-control intent; a rule appearing in the ADOM editor does not prove it was assigned to the correct devices or installed in their running security policy.
Question 344
A retail chain wants a common outbound policy on selected store FortiGates but must keep headquarters' separate security controls untouched. Which proposed shortcut most directly risks unexpected branch exposure or missing controls after confusing central policy authoring with installation target coverage and should therefore be rejected?
Answer & Explanations
Correct answer: C
Make an internet-access exception on one shared FortiManager package and assume its description automatically limits installation to the requesting branch. That shortcut risks overly broad access when a site-specific rule is deployed to every firewall in a shared package. Here the specific shortcut is: Create a shared rule in FortiManager and assume every registered firewall instantly enforces it regardless of policy-package assignment or the Install Wizard.
Assume a device database interface description edit automatically updates every ADOM policy package and all customer object definitions without an installation or synchronization step. That shortcut risks inconsistent manager and gateway state after confusing shared policy objects with device-specific configuration. Here the specific shortcut is: Create a shared rule in FortiManager and assume every registered firewall instantly enforces it regardless of policy-package assignment or the Install Wizard.
Create a shared rule in FortiManager and assume every registered firewall instantly enforces it regardless of policy-package assignment or the Install Wizard. The foreseeable failure is unexpected branch exposure or missing controls after confusing central policy authoring with installation target coverage. The safer response is: Create a centrally reviewed policy package in the correct ADOM, associate only the intended FortiGate installation targets, and validate per-device interface and object mappings before installation.
Ship a replacement firewall with factory-default permit behavior and assume FortiManager automatically installs every old policy as soon as the new device has the same hostname. That shortcut risks unprotected or disconnected branch when replacement hardware is assumed to inherit policy without authenticated management and installation. Here the specific shortcut is: Create a shared rule in FortiManager and assume every registered firewall instantly enforces it regardless of policy-package assignment or the Install Wizard.
Question 345
A retail chain wants a common outbound policy on selected store FortiGates but must keep headquarters' separate security controls untouched. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: D
This action/test pair addresses “Distinguish the FortiManager ADOM object database from device-level configuration records”. Edit shared firewall policy objects in the proper ADOM object database and separately examine device-specific configuration records, verifying how policy package installation renders the intended settings on a FortiGate. Modify a harmless ADOM service object and a separate test device setting, inspect both database views and install only the reviewed policy change while checking the resulting FortiGate state. The case instead calls for: Create a centrally reviewed policy package in the correct ADOM, associate only the intended FortiGate installation targets, and validate per-device interface and object mappings before installation.
The action is applicable: Create a centrally reviewed policy package in the correct ADOM, associate only the intended FortiGate installation targets, and validate per-device interface and object mappings before installation. But its proposed test—In a lab assign a single branch-specific rule only to one of two package targets, compare the generated firewall configurations and confirm the other gateway does not receive the exception.—addresses “Verify per-policy installation targets rather than relying on package-wide assumptions”. This requirement is confirmed instead by: Build a lab package with one permitted and one denied service, assign two approved gateways, preview and install, then confirm an unrelated test firewall is unchanged.
The test would be relevant: Build a lab package with one permitted and one denied service, assign two approved gateways, preview and install, then confirm an unrelated test firewall is unchanged. But the offered implementation—Set the intended supported installation target or per-policy scope for a FortiManager rule, review how it applies to individual managed FortiGates, and preview each target's resulting policy before committing installation.—addresses “Verify per-policy installation targets rather than relying on package-wide assumptions”. The action needed here is: Create a centrally reviewed policy package in the correct ADOM, associate only the intended FortiGate installation targets, and validate per-device interface and object mappings before installation.
Create a centrally reviewed policy package in the correct ADOM, associate only the intended FortiGate installation targets, and validate per-device interface and object mappings before installation. Confirm it through this test: Build a lab package with one permitted and one denied service, assign two approved gateways, preview and install, then confirm an unrelated test firewall is unchanged. Policy packages represent centrally managed access-control intent; a rule appearing in the ADOM editor does not prove it was assigned to the correct devices or installed in their running security policy.
Question 346
A hospital security team is introducing a standard branch package and needs proof that policy deployment reaches only approved clinical sites. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: B
Configure the intended interface mapping for each target firewall so policy packages referencing normalized logical interfaces resolve to the real supported FortiGate ports at installation. This addresses “Map normalized FortiManager policy interfaces to differing FortiGate port names”, where the governing principle is: Physical interface names and zone membership differ across appliance models; central policy rules cannot be deployed safely when a logical interface mapping is absent or points to the wrong data path. The stated case instead calls for: Create a centrally reviewed policy package in the correct ADOM, associate only the intended FortiGate installation targets, and validate per-device interface and object mappings before installation.
The question is set in this situation: A hospital security team is introducing a standard branch package and needs proof that policy deployment reaches only approved clinical sites. Create a centrally reviewed policy package in the correct ADOM, associate only the intended FortiGate installation targets, and validate per-device interface and object mappings before installation. Policy packages represent centrally managed access-control intent; a rule appearing in the ADOM editor does not prove it was assigned to the correct devices or installed in their running security policy. Verify the result with this test: Build a lab package with one permitted and one denied service, assign two approved gateways, preview and install, then confirm an unrelated test firewall is unchanged.
Use FortiManager's supported object usage and duplicate analysis to identify candidates, verify all policy references and the intended ADOM scope, then remove or consolidate only approved items. This addresses “Detect unused and duplicate FortiManager objects before policy cleanup”, where the governing principle is: An unused or duplicate-looking object may still matter to another policy package or device-specific mapping; visibility into references helps avoid deleting a dependency needed for installation. The stated case instead calls for: Create a centrally reviewed policy package in the correct ADOM, associate only the intended FortiGate installation targets, and validate per-device interface and object mappings before installation.
After restoring or choosing an approved FortiManager ADOM revision, preview and explicitly install the corresponding policy package to affected target devices and verify their actual enforced revision. This addresses “Reconcile ADOM revision recovery with package installation state on managed FortiGates”, where the governing principle is: An ADOM revision changes central database content; existing FortiGates do not automatically roll back running policies merely because an older management snapshot was selected. The stated case instead calls for: Create a centrally reviewed policy package in the correct ADOM, associate only the intended FortiGate installation targets, and validate per-device interface and object mappings before installation.
Question 347
A hospital security team is introducing a standard branch package and needs proof that policy deployment reaches only approved clinical sites. The engineer proposes the following change: Create a centrally reviewed policy package in the correct ADOM, associate only the intended FortiGate installation targets, and validate per-device interface and object mappings before installation. Which mechanism explains why it works?
Answer & Explanations
Correct answer: A
The question is set in this situation: A hospital security team is introducing a standard branch package and needs proof that policy deployment reaches only approved clinical sites. Policy packages represent centrally managed access-control intent; a rule appearing in the ADOM editor does not prove it was assigned to the correct devices or installed in their running security policy. The corresponding implementation is: Create a centrally reviewed policy package in the correct ADOM, associate only the intended FortiGate installation targets, and validate per-device interface and object mappings before installation.
Physical interface names and zone membership differ across appliance models; central policy rules cannot be deployed safely when a logical interface mapping is absent or points to the wrong data path. That explains “Map normalized FortiManager policy interfaces to differing FortiGate port names”, not the mechanism behind the described change. The relevant principle is: Policy packages represent centrally managed access-control intent; a rule appearing in the ADOM editor does not prove it was assigned to the correct devices or installed in their running security policy.
An unused or duplicate-looking object may still matter to another policy package or device-specific mapping; visibility into references helps avoid deleting a dependency needed for installation. That explains “Detect unused and duplicate FortiManager objects before policy cleanup”, not the mechanism behind the described change. The relevant principle is: Policy packages represent centrally managed access-control intent; a rule appearing in the ADOM editor does not prove it was assigned to the correct devices or installed in their running security policy.
An ADOM revision changes central database content; existing FortiGates do not automatically roll back running policies merely because an older management snapshot was selected. That explains “Reconcile ADOM revision recovery with package installation state on managed FortiGates”, not the mechanism behind the described change. The relevant principle is: Policy packages represent centrally managed access-control intent; a rule appearing in the ADOM editor does not prove it was assigned to the correct devices or installed in their running security policy.
Question 348
A hospital security team is introducing a standard branch package and needs proof that policy deployment reaches only approved clinical sites. After implementing this change—Create a centrally reviewed policy package in the correct ADOM, associate only the intended FortiGate installation targets, and validate per-device interface and object mappings before installation.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: C
In a disposable ADOM create two equal test address objects and an actually referenced third, inspect usage and duplicate views, then confirm deleting the approved unused one does not break validation. That would help test “Detect unused and duplicate FortiManager objects before policy cleanup”, not the outcome required in this scenario. The relevant acceptance check is: Build a lab package with one permitted and one denied service, assign two approved gateways, preview and install, then confirm an unrelated test firewall is unchanged.
Preview one branch package targeting a FortiGate with wan1 and another with a differently named uplink, verify mapped interface values and run controlled permitted/denied traffic tests after install. That would help test “Map normalized FortiManager policy interfaces to differing FortiGate port names”, not the outcome required in this scenario. The relevant acceptance check is: Build a lab package with one permitted and one denied service, assign two approved gateways, preview and install, then confirm an unrelated test firewall is unchanged.
The question is set in this situation: A hospital security team is introducing a standard branch package and needs proof that policy deployment reaches only approved clinical sites. Build a lab package with one permitted and one denied service, assign two approved gateways, preview and install, then confirm an unrelated test firewall is unchanged. This check is decisive because policy packages represent centrally managed access-control intent; a rule appearing in the ADOM editor does not prove it was assigned to the correct devices or installed in their running security policy.
Restore a test ADOM revision, confirm the central package version changed, inspect a staged FortiGate's still-running old policy, then install and verify the approved restored package. That would help test “Reconcile ADOM revision recovery with package installation state on managed FortiGates”, not the outcome required in this scenario. The relevant acceptance check is: Build a lab package with one permitted and one denied service, assign two approved gateways, preview and install, then confirm an unrelated test firewall is unchanged.
Question 349
A hospital security team is introducing a standard branch package and needs proof that policy deployment reaches only approved clinical sites. Which proposed shortcut most directly risks unexpected branch exposure or missing controls after confusing central policy authoring with installation target coverage and should therefore be rejected?
Answer & Explanations
Correct answer: D
Install a policy package using an unmapped generic interface label across all models and assume FortiManager magically substitutes every local port correctly. That shortcut risks broken connectivity or bypassed filtering after shared policy interfaces resolve incorrectly on target FortiGates. Here the specific shortcut is: Create a shared rule in FortiManager and assume every registered firewall instantly enforces it regardless of policy-package assignment or the Install Wizard.
Restore a previous ADOM revision and report every gateway instantly rolled back even though no installation tasks or device policy checks were performed. That shortcut risks incorrect change records after management database restoration is confused with actual firewall enforcement rollback. Here the specific shortcut is: Create a shared rule in FortiManager and assume every registered firewall instantly enforces it regardless of policy-package assignment or the Install Wizard.
Delete every object sharing an IP subnet because a naming report flags duplicates, without inspecting security policy, dynamic mappings or template dependencies. That shortcut risks failed installs or changed access decisions after careless cleanup of referenced central policy objects. Here the specific shortcut is: Create a shared rule in FortiManager and assume every registered firewall instantly enforces it regardless of policy-package assignment or the Install Wizard.
The question is set in this situation: A hospital security team is introducing a standard branch package and needs proof that policy deployment reaches only approved clinical sites. Create a shared rule in FortiManager and assume every registered firewall instantly enforces it regardless of policy-package assignment or the Install Wizard. The foreseeable failure is unexpected branch exposure or missing controls after confusing central policy authoring with installation target coverage. The safer response is: Create a centrally reviewed policy package in the correct ADOM, associate only the intended FortiGate installation targets, and validate per-device interface and object mappings before installation.
Question 350
A hospital security team is introducing a standard branch package and needs proof that policy deployment reaches only approved clinical sites. 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 security team is introducing a standard branch package and needs proof that policy deployment reaches only approved clinical sites. Create a centrally reviewed policy package in the correct ADOM, associate only the intended FortiGate installation targets, and validate per-device interface and object mappings before installation. Confirm it through this test: Build a lab package with one permitted and one denied service, assign two approved gateways, preview and install, then confirm an unrelated test firewall is unchanged. Policy packages represent centrally managed access-control intent; a rule appearing in the ADOM editor does not prove it was assigned to the correct devices or installed in their running security policy.
The action is applicable: Create a centrally reviewed policy package in the correct ADOM, associate only the intended FortiGate installation targets, and validate per-device interface and object mappings before installation. But its proposed test—Preview one branch package targeting a FortiGate with wan1 and another with a differently named uplink, verify mapped interface values and run controlled permitted/denied traffic tests after install.—addresses “Map normalized FortiManager policy interfaces to differing FortiGate port names”. This requirement is confirmed instead by: Build a lab package with one permitted and one denied service, assign two approved gateways, preview and install, then confirm an unrelated test firewall is unchanged.
The test would be relevant: Build a lab package with one permitted and one denied service, assign two approved gateways, preview and install, then confirm an unrelated test firewall is unchanged. But the offered implementation—Configure the intended interface mapping for each target firewall so policy packages referencing normalized logical interfaces resolve to the real supported FortiGate ports at installation.—addresses “Map normalized FortiManager policy interfaces to differing FortiGate port names”. The action needed here is: Create a centrally reviewed policy package in the correct ADOM, associate only the intended FortiGate installation targets, and validate per-device interface and object mappings before installation.
This action/test pair addresses “Detect unused and duplicate FortiManager objects before policy cleanup”. Use FortiManager's supported object usage and duplicate analysis to identify candidates, verify all policy references and the intended ADOM scope, then remove or consolidate only approved items. In a disposable ADOM create two equal test address objects and an actually referenced third, inspect usage and duplicate views, then confirm deleting the approved unused one does not break validation. The case instead calls for: Create a centrally reviewed policy package in the correct ADOM, associate only the intended FortiGate installation targets, and validate per-device interface and object mappings before installation.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- Fortinet FCP_FMG_AD-7.6 Practice Test 33 - 10 Questions (Last Reviewed 19-Oct-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 34 - 10 Questions (Last Reviewed 18-Oct-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 35 - 10 Questions (Last Reviewed 17-Oct-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 36 - 10 Questions (Last Reviewed 16-Oct-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 37 - 10 Questions (Last Reviewed 15-Oct-2026)