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 39

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?

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

Answer & Explanations

Correct answer: B

A.

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.

B.

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.

C.

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.

D.

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.

Question 381

A government network team wants every central rule associated with a risk owner and approved change identifier for audit reporting. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. 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.
  2. 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.
  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. After restoring or choosing an approved FortiManager ADOM revision, preview and explicitly install the corresponding policy package to affected target devices and verify their actual enforced revision.

Answer & Explanations

Correct answer: B

A.

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

B.

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. Meta fields enrich management records and workflow traceability; a descriptive 'approved' tag cannot itself enforce firewall authorization or install a rule on a FortiGate. Verify the result with this 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.

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

D.

After restoring or choosing an approved FortiManager ADOM revision, preview and explicitly install the corresponding policy package to affected target devices and verify their actual enforced revision. This addresses “Reconcile ADOM revision recovery with package installation state on managed FortiGates”, where the governing principle is: An ADOM revision changes central database content; existing FortiGates do not automatically roll back running policies merely because an older management snapshot was selected. The stated case instead calls for: 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.

Question 382

A government network team wants every central rule associated with a risk owner and approved change identifier for audit reporting. The engineer proposes the following change: 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. Which mechanism explains why it works?

  1. Meta fields enrich management records and workflow traceability; a descriptive 'approved' tag cannot itself enforce firewall authorization or install a rule on a FortiGate.
  2. 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.
  3. 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.
  4. An ADOM revision changes central database content; existing FortiGates do not automatically roll back running policies merely because an older management snapshot was selected.

Answer & Explanations

Correct answer: A

A.

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

B.

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: Meta fields enrich management records and workflow traceability; a descriptive 'approved' tag cannot itself enforce firewall authorization or install a rule on a FortiGate.

C.

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: Meta fields enrich management records and workflow traceability; a descriptive 'approved' tag cannot itself enforce firewall authorization or install a rule on a FortiGate.

D.

An ADOM revision changes central database content; existing FortiGates do not automatically roll back running policies merely because an older management snapshot was selected. That explains “Reconcile ADOM revision recovery with package installation state on managed FortiGates”, not the mechanism behind the described change. The relevant principle is: Meta fields enrich management records and workflow traceability; a descriptive 'approved' tag cannot itself enforce firewall authorization or install a rule on a FortiGate.

Question 383

A government network team wants every central rule associated with a risk owner and approved change identifier for audit reporting. After implementing this change—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.—which test most directly validates its intended outcome?

  1. Restore a test ADOM revision, confirm the central package version changed, inspect a staged FortiGate's still-running old policy, then install and verify the approved restored package.
  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. 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.
  4. 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.

Answer & Explanations

Correct answer: D

A.

Restore a test ADOM revision, confirm the central package version changed, inspect a staged FortiGate's still-running old policy, then install and verify the approved restored package. That would help test “Reconcile ADOM revision recovery with package installation state on managed FortiGates”, not the outcome required in this scenario. The relevant acceptance check is: 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.

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

C.

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

D.

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. This check is decisive because meta fields enrich management records and workflow traceability; a descriptive 'approved' tag cannot itself enforce firewall authorization or install a rule on a FortiGate.

Question 384

A government network team wants every central rule associated with a risk owner and approved change identifier for audit reporting. Which proposed shortcut most directly risks false security assurance after using management labels as a substitute for enforceable firewall configuration and should therefore be rejected?

  1. Delete every object sharing an IP subnet because a naming report flags duplicates, without inspecting security policy, dynamic mappings or template dependencies.
  2. Install a policy package using an unmapped generic interface label across all models and assume FortiManager magically substitutes every local port correctly.
  3. 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.
  4. Restore a previous ADOM revision and report every gateway instantly rolled back even though no installation tasks or device policy checks were performed.

Answer & Explanations

Correct answer: C

A.

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

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

C.

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. The foreseeable failure is false security assurance after using management labels as a substitute for enforceable firewall configuration. The safer response is: 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.

D.

Restore a previous ADOM revision and report every gateway instantly rolled back even though no installation tasks or device policy checks were performed. That shortcut risks incorrect change records after management database restoration is confused with actual firewall enforcement rollback. Here the specific shortcut is: 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.

Question 385

A government network team wants every central rule associated with a risk owner and approved change identifier for audit reporting. 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: 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: 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: 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.
  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: 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.

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

B.

The action is applicable: 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. 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: 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.

C.

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. Confirm it through this 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. Meta fields enrich management records and workflow traceability; a descriptive 'approved' tag cannot itself enforce firewall authorization or install a rule on a FortiGate.

D.

The test would be relevant: 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. 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: 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.

Question 386

A logistics MSP uses custom metadata to track which customers own address objects but must demonstrate metadata does not alter the data plane. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. 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.
  2. 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.
  3. 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.
  4. Run FortiManager's supported policy import wizard for the selected managed device, reconcile interface mappings and address/service objects, review import warnings and create a package for explicit later approval and installation.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: A logistics MSP uses custom metadata to track which customers own address objects but must demonstrate metadata does not alter the data plane. 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. Meta fields enrich management records and workflow traceability; a descriptive 'approved' tag cannot itself enforce firewall authorization or install a rule on a FortiGate. Verify the result with this 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.

B.

Set the intended supported installation target or per-policy scope for a FortiManager rule, review how it applies to individual managed FortiGates, and preview each target's resulting policy before committing installation. This addresses “Verify per-policy installation targets rather than relying on package-wide assumptions”, where the governing principle is: One centrally shared package may contain rules relevant only to particular branches; leaving rule targets overly broad can create unintended permissions even when the package assignment itself is correct. The stated case instead calls for: 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.

C.

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

D.

Run FortiManager's supported policy import wizard for the selected managed device, reconcile interface mappings and address/service objects, review import warnings and create a package for explicit later approval and installation. This addresses “Import existing FortiGate policy into a reviewed FortiManager policy package”, where the governing principle is: A policy import captures device-side rules into central database scope; it is distinct from copying configuration to the gateway, and unresolved references can cause problems during later installs. The stated case instead calls for: 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.

Question 387

A logistics MSP uses custom metadata to track which customers own address objects but must demonstrate metadata does not alter the data plane. The engineer proposes the following change: 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. 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. Meta fields enrich management records and workflow traceability; a descriptive 'approved' tag cannot itself enforce firewall authorization or install a rule on a FortiGate.
  3. 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.
  4. A policy import captures device-side rules into central database scope; it is distinct from copying configuration to the gateway, and unresolved references can cause problems during later installs.

Answer & Explanations

Correct answer: B

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. 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: Meta fields enrich management records and workflow traceability; a descriptive 'approved' tag cannot itself enforce firewall authorization or install a rule on a FortiGate.

B.

The question is set in this situation: A logistics MSP uses custom metadata to track which customers own address objects but must demonstrate metadata does not alter the data plane. 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 corresponding implementation is: 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.

C.

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: Meta fields enrich management records and workflow traceability; a descriptive 'approved' tag cannot itself enforce firewall authorization or install a rule on a FortiGate.

D.

A policy import captures device-side rules into central database scope; it is distinct from copying configuration to the gateway, and unresolved references can cause problems during later installs. That explains “Import existing FortiGate policy into a reviewed FortiManager policy package”, not the mechanism behind the described change. The relevant principle is: Meta fields enrich management records and workflow traceability; a descriptive 'approved' tag cannot itself enforce firewall authorization or install a rule on a FortiGate.

Question 388

A logistics MSP uses custom metadata to track which customers own address objects but must demonstrate metadata does not alter the data plane. After implementing this change—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.—which test most directly validates its intended outcome?

  1. 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.
  2. 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. Import a staging FortiGate containing one custom address and service, compare its running rules to the new package, fix a deliberate interface mapping warning and document that no install occurred merely from import.
  4. 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.

Answer & Explanations

Correct answer: D

A.

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

B.

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

C.

Import a staging FortiGate containing one custom address and service, compare its running rules to the new package, fix a deliberate interface mapping warning and document that no install occurred merely from import. That would help test “Import existing FortiGate policy into a reviewed FortiManager policy package”, not the outcome required in this scenario. The relevant acceptance check is: 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.

D.

The question is set in this situation: A logistics MSP uses custom metadata to track which customers own address objects but must demonstrate metadata does not alter the data plane. 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. This check is decisive because meta fields enrich management records and workflow traceability; a descriptive 'approved' tag cannot itself enforce firewall authorization or install a rule on a FortiGate.

Question 389

A logistics MSP uses custom metadata to track which customers own address objects but must demonstrate metadata does not alter the data plane. Which proposed shortcut most directly risks false security assurance after using management labels as a substitute for enforceable firewall configuration 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. 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.
  3. 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.
  4. Accept every failed mapping in an import report and then install the incomplete package over production before comparing it with the existing gateway policy.

Answer & Explanations

Correct answer: C

A.

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

B.

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

C.

The question is set in this situation: A logistics MSP uses custom metadata to track which customers own address objects but must demonstrate metadata does not alter the data plane. 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. The foreseeable failure is false security assurance after using management labels as a substitute for enforceable firewall configuration. The safer response is: 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.

D.

Accept every failed mapping in an import report and then install the incomplete package over production before comparing it with the existing gateway policy. That shortcut risks loss of valid access rules after an incomplete first import is treated as ready for installation. Here the specific shortcut is: 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.

Question 390

A logistics MSP uses custom metadata to track which customers own address objects but must demonstrate metadata does not alter the data plane. 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: 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.
  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: 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 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: 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.

Answer & Explanations

Correct answer: B

A.

The test would be relevant: 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. 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 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.

B.

The question is set in this situation: A logistics MSP uses custom metadata to track which customers own address objects but must demonstrate metadata does not alter the data plane. 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. Confirm it through this 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. Meta fields enrich management records and workflow traceability; a descriptive 'approved' tag cannot itself enforce firewall authorization or install a rule on a FortiGate.

C.

The action is applicable: 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. 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: 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.

D.

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

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