Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 43
Question 420
A hospital's remote clinic must get an approved diagnostic access rule while the other clinics remain under the original restrictive policy. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: C
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: 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.
The action is applicable: 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. 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: 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.
The question is set in this situation: A hospital's remote clinic must get an approved diagnostic access rule while the other clinics remain under the original restrictive policy. 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. Confirm it through this 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. 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 test would be relevant: 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. 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: 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.
Question 421
A managed security provider wants to explain why two FortiGates show the same policy object but different local interface settings in FortiManager. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: B
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: 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.
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. 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. Verify the result with this test: 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.
Use FortiManager policy checks and relevant object validations to inspect shadowed, inconsistent or invalid rules and referenced interfaces, then resolve significant issues before installing to production targets. This addresses “Run FortiManager policy check before approving a package installation”, where the governing principle is: A syntactically saved rule may never match because a broader earlier rule captures traffic; checking effective policy logic prevents false assumptions that a newly written rule changes enforcement. The stated case instead calls for: 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.
Run FortiManager's supported policy import wizard for the selected managed device, reconcile interface mappings and address/service objects, review import warnings and create a package for explicit later approval and installation. This addresses “Import existing FortiGate policy into a reviewed FortiManager policy package”, where the governing principle is: A policy import captures device-side rules into central database scope; it is distinct from copying configuration to the gateway, and unresolved references can cause problems during later installs. The stated case instead calls for: 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.
Question 422
A managed security provider wants to explain why two FortiGates show the same policy object but different local interface settings in FortiManager. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: D
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: 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.
A policy import captures device-side rules into central database scope; it is distinct from copying configuration to the gateway, and unresolved references can cause problems during later installs. That explains “Import existing FortiGate policy into a reviewed FortiManager policy package”, not the mechanism behind the described change. The relevant 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.
A syntactically saved rule may never match because a broader earlier rule captures traffic; checking effective policy logic prevents false assumptions that a newly written rule changes enforcement. That explains “Run FortiManager policy check before approving a package installation”, not the mechanism behind the described change. The relevant 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.
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 corresponding implementation is: 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.
Question 423
A managed security provider wants to explain why two FortiGates show the same policy object but different local interface settings in FortiManager. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: A
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. This check is decisive because 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.
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: 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.
Add a narrowly scoped deny beneath a broad allow in a lab package, use the available policy analysis and simulated traffic to reveal the shadowed behavior, then revise approved rule order. That would help test “Run FortiManager policy check before approving a package installation”, not the outcome required in this scenario. The relevant acceptance check is: 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.
Import a staging FortiGate containing one custom address and service, compare its running rules to the new package, fix a deliberate interface mapping warning and document that no install occurred merely from import. That would help test “Import existing FortiGate policy into a reviewed FortiManager policy package”, not the outcome required in this scenario. The relevant acceptance check is: 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.
Question 424
A managed security provider wants to explain why two FortiGates show the same policy object but different local interface settings in FortiManager. Which proposed shortcut most directly risks inconsistent manager and gateway state after confusing shared policy objects with device-specific configuration 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: Assume a device database interface description edit automatically updates every ADOM policy package and all customer object definitions without an installation or synchronization step.
Save a new deny rule at the end of a policy list and assume it always overrides an earlier matching allow because its description says High Priority. That shortcut risks unintended permitted access after an ineffective shadowed security rule is installed without verification. Here the specific shortcut is: Assume a device database interface description edit automatically updates every ADOM policy package and all customer object definitions without an installation or synchronization step.
Assume a device database interface description edit automatically updates every ADOM policy package and all customer object definitions without an installation or synchronization step. The foreseeable failure is inconsistent manager and gateway state after confusing shared policy objects with device-specific configuration. The safer response is: 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.
Accept every failed mapping in an import report and then install the incomplete package over production before comparing it with the existing gateway policy. That shortcut risks loss of valid access rules after an incomplete first import is treated as ready for installation. Here the specific shortcut is: Assume a device database interface description edit automatically updates every ADOM policy package and all customer object definitions without an installation or synchronization step.
Question 425
A managed security provider wants to explain why two FortiGates show the same policy object but different local interface settings in FortiManager. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: D
The test would be relevant: 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. But the offered implementation—Use FortiManager policy checks and relevant object validations to inspect shadowed, inconsistent or invalid rules and referenced interfaces, then resolve significant issues before installing to production targets.—addresses “Run FortiManager policy check before approving a package installation”. The action needed here is: 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 action/test pair addresses “Verify per-policy installation targets rather than relying on package-wide assumptions”. 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. 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. The case instead calls for: 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.
The action is applicable: 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. But its proposed test—Add a narrowly scoped deny beneath a broad allow in a lab package, use the available policy analysis and simulated traffic to reveal the shadowed behavior, then revise approved rule order.—addresses “Run FortiManager policy check before approving a package installation”. This requirement is confirmed instead by: 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.
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. Confirm it through this test: 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. 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.
Question 426
A university network team is diagnosing a stale shared service object and needs to locate whether the difference resides in the ADOM or on a single device. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: B
Define a suitable dynamic mapping for a centrally shared policy object and configure distinct authorized values per target FortiGate without copying private branch subnets into one universal static object. This addresses “Use FortiManager dynamic objects for per-device address differences”, where the governing principle is: Dynamic objects let a common logical name resolve to different device-specific values at installation; leaving a mapping undefined or treating it as globally identical can send traffic to the wrong destination. The stated case instead calls for: 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.
The question is set in this situation: A university network team is diagnosing a stale shared service object and needs to locate whether the difference resides in the ADOM or on a single device. 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. 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. Verify the result with this test: 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.
Compare FortiManager's intended package and device database with recent approved local FortiGate changes, retrieve or reconcile legitimate differences, and preview the installation impact before pushing central configuration. This addresses “Avoid accidental overwrite of local FortiGate changes during central policy installation”, where the governing principle is: A FortiManager install can replace selected device-side settings with centrally managed intended state; ignoring authorized emergency local edits can make a later normal installation undo critical recovery changes. The stated case instead calls for: 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.
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: 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.
Question 427
A university network team is diagnosing a stale shared service object and needs to locate whether the difference resides in the ADOM or on a single device. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: A
The question is set in this situation: A university network team is diagnosing a stale shared service object and needs to locate whether the difference resides in the ADOM or on a single device. 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 corresponding implementation is: 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.
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: 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.
A FortiManager install can replace selected device-side settings with centrally managed intended state; ignoring authorized emergency local edits can make a later normal installation undo critical recovery changes. That explains “Avoid accidental overwrite of local FortiGate changes during central policy installation”, not the mechanism behind the described change. The relevant 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.
Dynamic objects let a common logical name resolve to different device-specific values at installation; leaving a mapping undefined or treating it as globally identical can send traffic to the wrong destination. That explains “Use FortiManager dynamic objects for per-device address differences”, not the mechanism behind the described change. The relevant 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.
Question 428
A university network team is diagnosing a stale shared service object and needs to locate whether the difference resides in the ADOM or on a single device. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: C
Add a harmless approved local rule in a staging firewall, compare central package and device revisions, import or translate it to managed policy, then install and confirm the exception is preserved. That would help test “Avoid accidental overwrite of local FortiGate changes during central policy installation”, not the outcome required in this scenario. The relevant acceptance check is: 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.
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: 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 question is set in this situation: A university network team is diagnosing a stale shared service object and needs to locate whether the difference resides in the ADOM or on a single device. 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. This check is decisive because 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.
Map a logical internal-network object to two different lab branch subnets, preview the installed package for each FortiGate and verify the generated addresses match the site. That would help test “Use FortiManager dynamic objects for per-device address differences”, not the outcome required in this scenario. The relevant acceptance check is: 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.
Question 429
A university network team is diagnosing a stale shared service object and needs to locate whether the difference resides in the ADOM or on a single device. Which proposed shortcut most directly risks inconsistent manager and gateway state after confusing shared policy objects with device-specific configuration 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: Assume a device database interface description edit automatically updates every ADOM policy package and all customer object definitions without an installation or synchronization step.
Set every branch object's address to the first store's network and assume FortiManager automatically discovers the correct site-specific values from an identical object name. That shortcut risks cross-site routing errors or unintended access after failing to map a shared dynamic object for each target device. Here the specific shortcut is: Assume a device database interface description edit automatically updates every ADOM policy package and all customer object definitions without an installation or synchronization step.
Run an unchanged old policy package after a branch emergency change and assume FortiManager always merges every local edit without review or possible overwrite. That shortcut risks unexpected site outage when central management overwrites an authorized local change that was never reconciled. Here the specific shortcut is: Assume a device database interface description edit automatically updates every ADOM policy package and all customer object definitions without an installation or synchronization step.
The question is set in this situation: A university network team is diagnosing a stale shared service object and needs to locate whether the difference resides in the ADOM or on a single device. Assume a device database interface description edit automatically updates every ADOM policy package and all customer object definitions without an installation or synchronization step. The foreseeable failure is inconsistent manager and gateway state after confusing shared policy objects with device-specific configuration. The safer response is: 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.
Question 430
A university network team is diagnosing a stale shared service object and needs to locate whether the difference resides in the ADOM or on a single device. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: C
This action/test pair addresses “Map normalized FortiManager policy interfaces to differing FortiGate port names”. 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. 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. The case instead calls for: 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.
The test would be relevant: 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. But the offered implementation—Define a suitable dynamic mapping for a centrally shared policy object and configure distinct authorized values per target FortiGate without copying private branch subnets into one universal static object.—addresses “Use FortiManager dynamic objects for per-device address differences”. The action needed here is: 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.
The question is set in this situation: A university network team is diagnosing a stale shared service object and needs to locate whether the difference resides in the ADOM or on a single device. 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. Confirm it through this test: 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. 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 action is applicable: 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. But its proposed test—Map a logical internal-network object to two different lab branch subnets, preview the installed package for each FortiGate and verify the generated addresses match the site.—addresses “Use FortiManager dynamic objects for per-device address differences”. This requirement is confirmed instead by: 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.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- Fortinet FCP_FMG_AD-7.6 Practice Test 41 - 10 Questions (Last Reviewed 11-Oct-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 42 - 10 Questions (Last Reviewed 10-Oct-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 43 - 10 Questions (Last Reviewed 09-Oct-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 44 - 10 Questions (Last Reviewed 08-Oct-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 45 - 10 Questions (Last Reviewed 07-Oct-2026)