Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 36
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.
Question 351
A logistics company shares a standardized policy between branches using overlapping conceptual network names but different private address ranges. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: C
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: 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.
Use FortiManager's policy installation preview and validation to inspect intended commands, target devices and object/interface resolution, then obtain approval before deploying a package. This addresses “Preview a FortiManager Install Wizard plan before changing a FortiGate”, where the governing principle is: The central package editor expresses desired state; the Install Wizard translates it into target-specific configuration and may reveal missing mappings or unexpected changes that are not visible from the package name. The stated case instead calls for: 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.
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. 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. Verify the result with this 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.
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: 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.
Question 352
A logistics company shares a standardized policy between branches using overlapping conceptual network names but different private address ranges. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: B
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: 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.
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 corresponding implementation is: 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.
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: 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 central package editor expresses desired state; the Install Wizard translates it into target-specific configuration and may reveal missing mappings or unexpected changes that are not visible from the package name. That explains “Preview a FortiManager Install Wizard plan before changing a FortiGate”, not the mechanism behind the described change. The relevant 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.
Question 353
A logistics company shares a standardized policy between branches using overlapping conceptual network names but different private address ranges. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: C
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: 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.
Preview a staging package with a dynamic object for two FortiGate targets, compare each generated change, install to one test device and confirm its actual policy counters. That would help test “Preview a FortiManager Install Wizard plan before changing a FortiGate”, not the outcome required in this scenario. The relevant acceptance check is: 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.
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. This check is decisive because 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.
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: 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.
Question 354
A logistics company shares a standardized policy between branches using overlapping conceptual network names but different private address ranges. Which proposed shortcut most directly risks cross-site routing errors or unintended access after failing to map a shared dynamic object for each target device and should therefore be rejected?
Answer & Explanations
Correct answer: B
Click Install All as soon as an ADOM package saves and assume the wizard cannot generate any unexpected per-device configuration changes. That shortcut risks network exposure or traffic disruption after deploying unchecked generated policy differences. Here the specific shortcut is: 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.
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. The foreseeable failure is cross-site routing errors or unintended access after failing to map a shared dynamic object for each target device. The safer response is: 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.
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: 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.
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: 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.
Question 355
A logistics company shares a standardized policy between branches using overlapping conceptual network names but different private address ranges. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: D
The action is applicable: 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. 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: 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.
The test would be relevant: 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. 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: 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 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: 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.
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. Confirm it through this 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. 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.
Question 356
A regional insurer wants to push identical policy intent while ensuring the target network resolves correctly for each registered FortiGate. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: A
The question is set in this situation: A regional insurer wants to push identical policy intent while ensuring the target network resolves correctly for each registered FortiGate. 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. 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. Verify the result with this 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.
Create a supported ADOM revision snapshot of current policy packages and objects before an approved large-scale edit, label the revision with change context, and verify a rollback path. This addresses “Capture a FortiManager ADOM revision before a shared policy reorganization”, where the governing principle is: An ADOM revision records central policy/object state at a point in time; a device configuration revision for one FortiGate cannot replace the broader ADOM snapshot used to recover shared packages. The stated case instead calls for: 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.
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 addresses “Choose a FortiManager policy package for a shared branch access standard”, where the governing 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. The stated case instead calls for: 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.
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: 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.
Question 357
A regional insurer wants to push identical policy intent while ensuring the target network resolves correctly for each registered FortiGate. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: C
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: 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.
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. That explains “Choose a FortiManager policy package for a shared branch access standard”, not the mechanism behind the described change. The relevant 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 question is set in this situation: A regional insurer wants to push identical policy intent while ensuring the target network resolves correctly for each registered FortiGate. 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 corresponding implementation is: 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.
An ADOM revision records central policy/object state at a point in time; a device configuration revision for one FortiGate cannot replace the broader ADOM snapshot used to recover shared packages. That explains “Capture a FortiManager ADOM revision before a shared policy reorganization”, not the mechanism behind the described change. The relevant 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.
Question 358
A regional insurer wants to push identical policy intent while ensuring the target network resolves correctly for each registered FortiGate. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: D
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. That would help test “Choose a FortiManager policy package for a shared branch access standard”, not the outcome required in this scenario. The relevant acceptance check is: 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.
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: 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.
Save an ADOM revision, alter a harmless shared object and package order in a lab, inspect the differences and restore only an approved central baseline without affecting unrelated device-only settings. That would help test “Capture a FortiManager ADOM revision before a shared policy reorganization”, not the outcome required in this scenario. The relevant acceptance check is: 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.
The question is set in this situation: A regional insurer wants to push identical policy intent while ensuring the target network resolves correctly for each registered FortiGate. 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. This check is decisive because 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.
Question 359
A regional insurer wants to push identical policy intent while ensuring the target network resolves correctly for each registered FortiGate. Which proposed shortcut most directly risks cross-site routing errors or unintended access after failing to map a shared dynamic object for each target device and should therefore be rejected?
Answer & Explanations
Correct answer: A
The question is set in this situation: A regional insurer wants to push identical policy intent while ensuring the target network resolves correctly for each registered FortiGate. 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. The foreseeable failure is cross-site routing errors or unintended access after failing to map a shared dynamic object for each target device. The safer response is: 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.
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: 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.
Before restructuring a customer ADOM delete its policy packages and count on a single branch FortiGate revision history to recreate every central object automatically. That shortcut risks permanent loss of shared policy context after an ADOM-wide change without an appropriate central revision. Here the specific shortcut is: 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.
Create a shared rule in FortiManager and assume every registered firewall instantly enforces it regardless of policy-package assignment or the Install Wizard. That shortcut risks unexpected branch exposure or missing controls after confusing central policy authoring with installation target coverage. Here the specific shortcut is: 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.
Question 360
A regional insurer wants to push identical policy intent while ensuring the target network resolves correctly for each registered FortiGate. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: B
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: 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.
The question is set in this situation: A regional insurer wants to push identical policy intent while ensuring the target network resolves correctly for each registered FortiGate. 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. Confirm it through this 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. 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 test would be relevant: 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. But the offered implementation—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.—addresses “Choose a FortiManager policy package for a shared branch access standard”. The action needed here is: 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.
The action is applicable: 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. But its proposed 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.—addresses “Choose a FortiManager policy package for a shared branch access standard”. This requirement is confirmed instead by: 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.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- 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)
- Fortinet FCP_FMG_AD-7.6 Practice Test 38 - 10 Questions (Last Reviewed 14-Oct-2026)