Practice Exams:

Fortinet FCP_FMG_AD-7.6 Dumps

EXAM: Fortinet NSE 5 - FortiManager 7.6 Administrator
Verified By Experts
Premium Bundle
$49.99

FCP_FMG_AD-7.6 Premium ETE File


  • Premium File 62 Questions & Answers
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Fortinet FCP_FMG_AD-7.6 Practice Test 42

Question 410

A university is reviewing a policy change for two FortiGate clusters and wants to detect invalid object references or shadowed access rules before deployment. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: 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. Verify: 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.
  2. Implement: 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. Verify: 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.
  3. Implement: 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. Verify: 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.
  4. Implement: 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. Verify: 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.

Answer & Explanations

Correct answer: D

A.

The action is applicable: 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. But its proposed 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.—addresses “Detect unused and duplicate FortiManager objects before policy cleanup”. This requirement is confirmed instead by: 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.

B.

This action/test pair addresses “Apply FortiManager meta fields to control business context without treating metadata as policy”. 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. 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. The case instead calls for: 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.

C.

The test would be relevant: 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. But the offered implementation—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.—addresses “Detect unused and duplicate FortiManager objects before policy cleanup”. The action needed here is: 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.

D.

The question is set in this situation: A university is reviewing a policy change for two FortiGate clusters and wants to detect invalid object references or shadowed access rules before deployment. 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. Confirm it through this 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. 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.

Question 411

A retailer needs a temporary vendor connection for one location but all stores use a common FortiManager policy package. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. 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.
  2. 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.
  3. 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.
  4. 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.

Answer & Explanations

Correct answer: C

A.

Create a centrally reviewed policy package in the correct ADOM, associate only the intended FortiGate installation targets, and validate per-device interface and object mappings before installation. 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: 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.

B.

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: 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.

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. 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. Verify the result with 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.

D.

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: 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 412

A retailer needs a temporary vendor connection for one location but all stores use a common FortiManager policy package. The engineer proposes the following change: 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. Which mechanism explains why it works?

  1. 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.
  2. 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.
  3. 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.
  4. 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.

Answer & Explanations

Correct answer: A

A.

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 corresponding implementation 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.

B.

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: 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.

C.

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: 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.

D.

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: 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.

Question 413

A retailer needs a temporary vendor connection for one location but all stores use a common FortiManager policy package. After implementing this change—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.—which test most directly validates its intended outcome?

  1. 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.
  2. 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.
  3. 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.
  4. 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.

Answer & Explanations

Correct answer: D

A.

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: 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.

B.

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 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.

C.

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 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.

D.

In a lab assign a single branch-specific rule only to one of two package targets, compare the generated firewall configurations and confirm the other gateway does not receive the exception. This check is decisive because 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.

Question 414

A retailer needs a temporary vendor connection for one location but all stores use a common FortiManager policy package. Which proposed shortcut most directly risks overly broad access when a site-specific rule is deployed to every firewall in a shared package and should therefore be rejected?

  1. Create a shared rule in FortiManager and assume every registered firewall instantly enforces it regardless of policy-package assignment or the Install Wizard.
  2. 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.
  3. Make an internet-access exception on one shared FortiManager package and assume its description automatically limits installation to the requesting branch.
  4. Assume a device database interface description edit automatically updates every ADOM policy package and all customer object definitions without an installation or synchronization step.

Answer & Explanations

Correct answer: C

A.

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: Make an internet-access exception on one shared FortiManager package and assume its description automatically limits installation to the requesting branch.

B.

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: Make an internet-access exception on one shared FortiManager package and assume its description automatically limits installation to the requesting branch.

C.

Make an internet-access exception on one shared FortiManager package and assume its description automatically limits installation to the requesting branch. The foreseeable failure is overly broad access when a site-specific rule is deployed to every firewall in a shared package. The safer response 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.

D.

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: Make an internet-access exception on one shared FortiManager package and assume its description automatically limits installation to the requesting branch.

Question 415

A retailer needs a temporary vendor connection for one location but all stores use a common FortiManager policy package. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: 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. Verify: 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.
  2. Implement: 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. Verify: 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.
  3. Implement: 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. Verify: 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.
  4. Implement: 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. Verify: 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.

Answer & Explanations

Correct answer: B

A.

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—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: 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.

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. 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.

C.

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—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: 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.

D.

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: 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 416

A hospital's remote clinic must get an approved diagnostic access rule while the other clinics remain under the original restrictive policy. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. 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.
  2. Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified.
  3. 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.
  4. 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.

Answer & Explanations

Correct answer: A

A.

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. 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. Verify the result with 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.

B.

Use FortiManager's ADOM revision history and available comparison tools to identify specific policy or object differences and decide whether targeted correction or full ADOM restoration is justified. This addresses “Compare two FortiManager ADOM revisions to isolate a shared object change”, where the governing principle is: Comparing central snapshots distinguishes authorized changes from accidental object drift; blindly restoring an older snapshot may erase independent legitimate edits made later in the same ADOM. The stated 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.

C.

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: 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.

D.

Use FortiManager's supported object usage and duplicate analysis to identify candidates, verify all policy references and the intended ADOM scope, then remove or consolidate only approved items. This addresses “Detect unused and duplicate FortiManager objects before policy cleanup”, where the governing principle is: An unused or duplicate-looking object may still matter to another policy package or device-specific mapping; visibility into references helps avoid deleting a dependency needed for installation. The stated case instead calls for: 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 417

A hospital's remote clinic must get an approved diagnostic access rule while the other clinics remain under the original restrictive policy. The engineer proposes the following change: 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. Which mechanism explains why it works?

  1. 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.
  2. 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.
  3. 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.
  4. Comparing central snapshots distinguishes authorized changes from accidental object drift; blindly restoring an older snapshot may erase independent legitimate edits made later in the same ADOM.

Answer & Explanations

Correct answer: B

A.

An unused or duplicate-looking object may still matter to another policy package or device-specific mapping; visibility into references helps avoid deleting a dependency needed for installation. That explains “Detect unused and duplicate FortiManager objects before policy cleanup”, not the mechanism behind the described change. The relevant principle is: 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.

B.

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. 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 corresponding implementation 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.

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: 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.

D.

Comparing central snapshots distinguishes authorized changes from accidental object drift; blindly restoring an older snapshot may erase independent legitimate edits made later in the same ADOM. That explains “Compare two FortiManager ADOM revisions to isolate a shared object change”, not the mechanism behind the described change. The relevant 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.

Question 418

A hospital's remote clinic must get an approved diagnostic access rule while the other clinics remain under the original restrictive policy. After implementing this change—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.—which test most directly validates its intended outcome?

  1. 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.
  2. 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.
  3. Produce two lab ADOM revisions with separate service-object and rule-order edits, compare them and validate one selected rollback while keeping the unrelated approved change.
  4. 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.

Answer & Explanations

Correct answer: D

A.

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: 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.

B.

In a disposable ADOM create two equal test address objects and an actually referenced third, inspect usage and duplicate views, then confirm deleting the approved unused one does not break validation. That would help test “Detect unused and duplicate FortiManager objects before policy cleanup”, not the outcome required in this scenario. The relevant acceptance check is: 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.

C.

Produce two lab ADOM revisions with separate service-object and rule-order edits, compare them and validate one selected rollback while keeping the unrelated approved change. That would help test “Compare two FortiManager ADOM revisions to isolate a shared object change”, not the outcome required in this scenario. The relevant acceptance check is: 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.

D.

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. 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. This check is decisive because 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.

Question 419

A hospital's remote clinic must get an approved diagnostic access rule while the other clinics remain under the original restrictive policy. Which proposed shortcut most directly risks overly broad access when a site-specific rule is deployed to every firewall in a shared package and should therefore be rejected?

  1. Make an internet-access exception on one shared FortiManager package and assume its description automatically limits installation to the requesting branch.
  2. Install a policy package using an unmapped generic interface label across all models and assume FortiManager magically substitutes every local port correctly.
  3. Restore the first-ever ADOM revision whenever one object is wrong, without inspecting what valid subsequent business rules and device assignments will be removed.
  4. Delete every object sharing an IP subnet because a naming report flags duplicates, without inspecting security policy, dynamic mappings or template dependencies.

Answer & Explanations

Correct answer: A

A.

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. Make an internet-access exception on one shared FortiManager package and assume its description automatically limits installation to the requesting branch. The foreseeable failure is overly broad access when a site-specific rule is deployed to every firewall in a shared package. The safer response 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.

B.

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: Make an internet-access exception on one shared FortiManager package and assume its description automatically limits installation to the requesting branch.

C.

Restore the first-ever ADOM revision whenever one object is wrong, without inspecting what valid subsequent business rules and device assignments will be removed. That shortcut risks unnecessary interruption after a broad central rollback erases valid later policy changes. Here the specific shortcut is: Make an internet-access exception on one shared FortiManager package and assume its description automatically limits installation to the requesting branch.

D.

Delete every object sharing an IP subnet because a naming report flags duplicates, without inspecting security policy, dynamic mappings or template dependencies. That shortcut risks failed installs or changed access decisions after careless cleanup of referenced central policy objects. Here the specific shortcut is: Make an internet-access exception on one shared FortiManager package and assume its description automatically limits installation to the requesting branch.

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?

  1. Implement: 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. Verify: 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.
  2. Implement: 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. Verify: 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.
  3. Implement: 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. Verify: 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.
  4. Implement: 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. Verify: 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.

Answer & Explanations

Correct answer: C

A.

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.

B.

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.

C.

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.

D.

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.

Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests