Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 38
Question 370
A managed services team is preparing policy deployment to two FortiGate form factors and must reconcile their WAN and internal interface maps. 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 managed services team is preparing policy deployment to two FortiGate form factors and must reconcile their WAN and internal interface maps. 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. Confirm it through this 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. 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 action is applicable: 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. But its proposed 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.—addresses “Distinguish the FortiManager ADOM object database from device-level configuration records”. This requirement is confirmed instead by: 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.
This action/test pair addresses “Choose a FortiManager policy package for a shared branch access standard”. 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. 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 case instead calls for: 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.
The test would be relevant: 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. But the offered implementation—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.—addresses “Distinguish the FortiManager ADOM object database from device-level configuration records”. The action needed here is: 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.
Question 371
A university's FortiManager ADOM has accumulated hundreds of objects and administrators want to reduce clutter without disrupting a legacy permitted rule. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: D
Acquire the supported ADOM, policy package or per-policy lock scope required by the FortiManager workspace mode and document the intended change boundary to limit unnecessary blocking of unrelated administrators. This addresses “Choose ADOM or policy package lock scope appropriate to the change”, where the governing principle is: A broad ADOM lock can protect consistency but impede independent change tickets, while a narrower supported lock may safely permit unrelated edits under the chosen workspace mode. The stated case instead calls for: 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.
Define consistent FortiManager policy and object metadata fields for owners, change tickets and classification, populate them during review, and keep actual rule actions and targets separately validated. This addresses “Apply FortiManager meta fields to control business context without treating metadata as policy”, where the governing principle is: Meta fields enrich management records and workflow traceability; a descriptive 'approved' tag cannot itself enforce firewall authorization or install a rule on a FortiGate. The stated case instead calls for: 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.
Define approved ADOM-level metadata variables and map their values to applicable objects or policy context according to FortiManager's supported feature semantics before installing packages across distinct device targets. This addresses “Use ADOM-level metadata variables to parameterize repeated policy content”, where the governing principle is: A variable is resolved within a defined management scope and supported configuration context; a variable with the wrong value or scope can produce a syntactically correct but unintended site-specific rule. The stated case instead calls for: 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.
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. 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. Verify the result with this test: 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.
Question 372
A university's FortiManager ADOM has accumulated hundreds of objects and administrators want to reduce clutter without disrupting a legacy permitted rule. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: B
A broad ADOM lock can protect consistency but impede independent change tickets, while a narrower supported lock may safely permit unrelated edits under the chosen workspace mode. That explains “Choose ADOM or policy package lock scope appropriate to the change”, not the mechanism behind the described change. The relevant 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.
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 corresponding implementation is: 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.
A variable is resolved within a defined management scope and supported configuration context; a variable with the wrong value or scope can produce a syntactically correct but unintended site-specific rule. That explains “Use ADOM-level metadata variables to parameterize repeated policy content”, not the mechanism behind the described change. The relevant 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.
Meta fields enrich management records and workflow traceability; a descriptive 'approved' tag cannot itself enforce firewall authorization or install a rule on a FortiGate. That explains “Apply FortiManager meta fields to control business context without treating metadata as policy”, not the mechanism behind the described change. The relevant 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.
Question 373
A university's FortiManager ADOM has accumulated hundreds of objects and administrators want to reduce clutter without disrupting a legacy permitted rule. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: C
Open two lab packages under one ADOM, lock only the intended scope, verify a competing edit is denied where needed and unrelated approved work remains possible when supported. That would help test “Choose ADOM or policy package lock scope appropriate to the change”, not the outcome required in this scenario. The relevant acceptance check is: 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.
Add a sample rule with required owner and ticket fields, query the metadata and compare its unchanged permit/deny behavior before and after the administrative label is updated. That would help test “Apply FortiManager meta fields to control business context without treating metadata as policy”, not the outcome required in this scenario. The relevant acceptance check is: 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.
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. This check is decisive because 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.
Set separate lab ADOM variable values for two fictional clients, preview a package deployment and confirm the generated object references do not cross customer boundaries. That would help test “Use ADOM-level metadata variables to parameterize repeated policy content”, not the outcome required in this scenario. The relevant acceptance check is: 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.
Question 374
A university's FortiManager ADOM has accumulated hundreds of objects and administrators want to reduce clutter without disrupting a legacy permitted rule. Which proposed shortcut most directly risks failed installs or changed access decisions after careless cleanup of referenced central policy objects and should therefore be rejected?
Answer & Explanations
Correct answer: D
Set a policy object's custom field to Secure and claim that this automatically activates IPS inspection or limits traffic even though the actual security policy did not change. That shortcut risks false security assurance after using management labels as a substitute for enforceable firewall configuration. Here the specific shortcut is: Delete every object sharing an IP subnet because a naming report flags duplicates, without inspecting security policy, dynamic mappings or template dependencies.
Claim that a read-only object label grants exclusive policy editing authority and skip required workspace locks during concurrent policy modifications. That shortcut risks accidental edit conflicts or avoidable maintenance delays after choosing no lock or overly broad lock scope. Here the specific shortcut is: Delete every object sharing an IP subnet because a naming report flags duplicates, without inspecting security policy, dynamic mappings or template dependencies.
Use one unreviewed global variable to inject a customer subnet into every ADOM and assume each tenant's policy automatically inherits an independent correct value. That shortcut risks cross-tenant policy misconfiguration after applying central metadata variables without explicit scope validation. Here the specific shortcut is: Delete every object sharing an IP subnet because a naming report flags duplicates, without inspecting security policy, dynamic mappings or template dependencies.
Delete every object sharing an IP subnet because a naming report flags duplicates, without inspecting security policy, dynamic mappings or template dependencies. The foreseeable failure is failed installs or changed access decisions after careless cleanup of referenced central policy objects. The safer response is: 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.
Question 375
A university's FortiManager ADOM has accumulated hundreds of objects and administrators want to reduce clutter without disrupting a legacy permitted rule. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: B
The test would be relevant: 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. But the offered implementation—Define consistent FortiManager policy and object metadata fields for owners, change tickets and classification, populate them during review, and keep actual rule actions and targets separately validated.—addresses “Apply FortiManager meta fields to control business context without treating metadata as policy”. The action needed here is: 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.
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. Confirm it through this test: 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. 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.
This action/test pair addresses “Use ADOM-level metadata variables to parameterize repeated policy content”. Define approved ADOM-level metadata variables and map their values to applicable objects or policy context according to FortiManager's supported feature semantics before installing packages across distinct device targets. Set separate lab ADOM variable values for two fictional clients, preview a package deployment and confirm the generated object references do not cross customer boundaries. The case instead calls for: 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.
The action is applicable: 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. But its proposed test—Add a sample rule with required owner and ticket fields, query the metadata and compare its unchanged permit/deny behavior before and after the administrative label is updated.—addresses “Apply FortiManager meta fields to control business context without treating metadata as policy”. This requirement is confirmed instead by: 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.
Question 376
A financial services administrator is investigating duplicate customer address entries and needs evidence that none are still used in global or assigned packages. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: A
The question is set in this situation: A financial services administrator is investigating duplicate customer address entries and needs evidence that none are still used in global or assigned packages. 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. 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. Verify the result with this test: 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.
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: 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.
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: 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.
When an Install Wizard detects unresolved objects, interface mappings or package syntax, inspect the specific validation message, correct the originating FortiManager database record and rerun validation before any installation. This addresses “Handle a FortiManager installation validation error before pushing policy”, where the governing principle is: A validation error means the generated target configuration may be incomplete; bypassing it or expanding a rule does not repair the underlying object mapping or unsupported feature. The stated case instead calls for: 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.
Question 377
A financial services administrator is investigating duplicate customer address entries and needs evidence that none are still used in global or assigned packages. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: A
The question is set in this situation: A financial services administrator is investigating duplicate customer address entries and needs evidence that none are still used in global or assigned packages. 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 corresponding implementation is: 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.
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: 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.
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: 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.
A validation error means the generated target configuration may be incomplete; bypassing it or expanding a rule does not repair the underlying object mapping or unsupported feature. That explains “Handle a FortiManager installation validation error before pushing policy”, not the mechanism behind the described change. The relevant 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.
Question 378
A financial services administrator is investigating duplicate customer address entries and needs evidence that none are still used in global or assigned packages. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: D
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: 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.
Create an intentionally missing interface mapping in a disposable package, inspect the exact validation failure, repair the mapping and demonstrate a clean preview and safe test install. That would help test “Handle a FortiManager installation validation error before pushing policy”, not the outcome required in this scenario. The relevant acceptance check is: 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.
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: 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 question is set in this situation: A financial services administrator is investigating duplicate customer address entries and needs evidence that none are still used in global or assigned packages. 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. This check is decisive because 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.
Question 379
A financial services administrator is investigating duplicate customer address entries and needs evidence that none are still used in global or assigned packages. Which proposed shortcut most directly risks failed installs or changed access decisions after careless cleanup of referenced central policy objects and should therefore be rejected?
Answer & Explanations
Correct answer: C
Ignore an install validation error for an unmapped interface and add a broad permit rule to production hoping the firewall will resolve the missing port automatically. That shortcut risks failed installation or unsafe workaround after treating object-mapping validation as a harmless notification. Here the specific shortcut is: Delete every object sharing an IP subnet because a naming report flags duplicates, without inspecting security policy, dynamic mappings or template dependencies.
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: Delete every object sharing an IP subnet because a naming report flags duplicates, without inspecting security policy, dynamic mappings or template dependencies.
The question is set in this situation: A financial services administrator is investigating duplicate customer address entries and needs evidence that none are still used in global or assigned packages. Delete every object sharing an IP subnet because a naming report flags duplicates, without inspecting security policy, dynamic mappings or template dependencies. The foreseeable failure is failed installs or changed access decisions after careless cleanup of referenced central policy objects. The safer response is: 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.
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: Delete every object sharing an IP subnet because a naming report flags duplicates, without inspecting security policy, dynamic mappings or template dependencies.
Question 380
A financial services administrator is investigating duplicate customer address entries and needs evidence that none are still used in global or assigned packages. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: B
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: 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.
The question is set in this situation: A financial services administrator is investigating duplicate customer address entries and needs evidence that none are still used in global or assigned packages. 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. Confirm it through this test: 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. 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 action is applicable: 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. 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: 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 test would be relevant: 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. 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: 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.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- 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)
- Fortinet FCP_FMG_AD-7.6 Practice Test 39 - 10 Questions (Last Reviewed 13-Oct-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 40 - 10 Questions (Last Reviewed 12-Oct-2026)