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 37

Question 360

A regional insurer wants to push identical policy intent while ensuring the target network resolves correctly for each registered FortiGate. Which combined implementation and verification plan is the best match for this workload?

  1. 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: 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. Implement: Define a suitable dynamic mapping for a centrally shared policy object and configure distinct authorized values per target FortiGate without copying private branch subnets into one universal static object. Verify: Map a logical internal-network object to two different lab branch subnets, preview the installed package for each FortiGate and verify the generated addresses match the site.
  3. 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: Map a logical internal-network object to two different lab branch subnets, preview the installed package for each FortiGate and verify the generated addresses match the site.
  4. Implement: Define a suitable dynamic mapping for a centrally shared policy object and configure distinct authorized values per target FortiGate without copying private branch subnets into one universal static object. 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.

This action/test pair addresses “Map normalized FortiManager policy interfaces to differing FortiGate port names”. Configure the intended interface mapping for each target firewall so policy packages referencing normalized logical interfaces resolve to the real supported FortiGate ports at installation. Preview one branch package targeting a FortiGate with wan1 and another with a differently named uplink, verify mapped interface values and run controlled permitted/denied traffic tests after install. The case instead calls for: Define a suitable dynamic mapping for a centrally shared policy object and configure distinct authorized values per target FortiGate without copying private branch subnets into one universal static object.

B.

The question is set in this situation: A regional insurer wants to push identical policy intent while ensuring the target network resolves correctly for each registered FortiGate. Define a suitable dynamic mapping for a centrally shared policy object and configure distinct authorized values per target FortiGate without copying private branch subnets into one universal static object. Confirm it through this test: Map a logical internal-network object to two different lab branch subnets, preview the installed package for each FortiGate and verify the generated addresses match the site. Dynamic objects let a common logical name resolve to different device-specific values at installation; leaving a mapping undefined or treating it as globally identical can send traffic to the wrong destination.

C.

The test would be relevant: Map a logical internal-network object to two different lab branch subnets, preview the installed package for each FortiGate and verify the generated addresses match the site. But the offered implementation—Create a centrally reviewed policy package in the correct ADOM, associate only the intended FortiGate installation targets, and validate per-device interface and object mappings before installation.—addresses “Choose a FortiManager policy package for a shared branch access standard”. The action needed here is: Define a suitable dynamic mapping for a centrally shared policy object and configure distinct authorized values per target FortiGate without copying private branch subnets into one universal static object.

D.

The action is applicable: Define a suitable dynamic mapping for a centrally shared policy object and configure distinct authorized values per target FortiGate without copying private branch subnets into one universal static object. But its proposed test—Build a lab package with one permitted and one denied service, assign two approved gateways, preview and install, then confirm an unrelated test firewall is unchanged.—addresses “Choose a FortiManager policy package for a shared branch access standard”. This requirement is confirmed instead by: Map a logical internal-network object to two different lab branch subnets, preview the installed package for each FortiGate and verify the generated addresses match the site.

Question 361

A hospital's replacement branch appliance uses different physical port names from the older model, but central security wants to reuse the same approved policy package. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. Inspect FortiManager session and lock ownership before closing a stale session or releasing an ADOM lock, document the intended change status and preserve or intentionally discard uncommitted work through the supported procedure.
  2. 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.
  3. 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.
  4. 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.

Answer & Explanations

Correct answer: B

A.

Inspect FortiManager session and lock ownership before closing a stale session or releasing an ADOM lock, document the intended change status and preserve or intentionally discard uncommitted work through the supported procedure. This addresses “Release abandoned workspace locks without silently discarding valid changes”, where the governing principle is: A stuck workspace lock may block progress, but force-releasing it without examining pending edits can either lose an authorized change or expose concurrent edits to conflict. The stated 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.

B.

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

C.

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

D.

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

A hospital's replacement branch appliance uses different physical port names from the older model, but central security wants to reuse the same approved policy package. The engineer proposes the following change: 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. Which mechanism explains why it works?

  1. 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.
  2. 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.
  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 stuck workspace lock may block progress, but force-releasing it without examining pending edits can either lose an authorized change or expose concurrent edits to conflict.

Answer & Explanations

Correct answer: A

A.

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

B.

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

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

D.

A stuck workspace lock may block progress, but force-releasing it without examining pending edits can either lose an authorized change or expose concurrent edits to conflict. That explains “Release abandoned workspace locks without silently discarding valid changes”, not the mechanism behind the described change. The relevant 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.

Question 363

A hospital's replacement branch appliance uses different physical port names from the older model, but central security wants to reuse the same approved policy package. After implementing this change—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.—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. 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.
  3. Create a harmless locked session, simulate an administrator disconnect, identify the lock and draft state, and use the authorized recovery procedure while verifying the committed policy remains correct.
  4. 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.

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

B.

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

C.

Create a harmless locked session, simulate an administrator disconnect, identify the lock and draft state, and use the authorized recovery procedure while verifying the committed policy remains correct. That would help test “Release abandoned workspace locks without silently discarding valid changes”, not the outcome required in this scenario. The relevant acceptance check is: 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.

D.

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

Question 364

A hospital's replacement branch appliance uses different physical port names from the older model, but central security wants to reuse the same approved policy package. Which proposed shortcut most directly risks broken connectivity or bypassed filtering after shared policy interfaces resolve incorrectly on target FortiGates and should therefore be rejected?

  1. 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.
  2. Delete every workspace session after one user disconnects and assume all authorized unpublished rule modifications will be preserved automatically.
  3. Install a policy package using an unmapped generic interface label across all models and assume FortiManager magically substitutes every local port correctly.
  4. 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.

Answer & Explanations

Correct answer: C

A.

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: Install a policy package using an unmapped generic interface label across all models and assume FortiManager magically substitutes every local port correctly.

B.

Delete every workspace session after one user disconnects and assume all authorized unpublished rule modifications will be preserved automatically. That shortcut risks lost approved drafts or conflicting policy edits after uncontrolled workspace lock recovery. Here the specific shortcut is: Install a policy package using an unmapped generic interface label across all models and assume FortiManager magically substitutes every local port correctly.

C.

Install a policy package using an unmapped generic interface label across all models and assume FortiManager magically substitutes every local port correctly. The foreseeable failure is broken connectivity or bypassed filtering after shared policy interfaces resolve incorrectly on target FortiGates. The safer response 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.

D.

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: Install a policy package using an unmapped generic interface label across all models and assume FortiManager magically substitutes every local port correctly.

Question 365

A hospital's replacement branch appliance uses different physical port names from the older model, but central security wants to reuse the same approved policy package. Which combined implementation and verification plan is the best match for this workload?

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

A.

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—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.—addresses “Use ADOM-level metadata variables to parameterize repeated policy content”. 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.

B.

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.

C.

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—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.—addresses “Use ADOM-level metadata variables to parameterize repeated policy content”. 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.

D.

This action/test pair addresses “Run FortiManager policy check before approving a package installation”. 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. 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. 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.

Question 366

A managed services team is preparing policy deployment to two FortiGate form factors and must reconcile their WAN and internal interface maps. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. Inspect FortiManager's package status, installation logs and managed FortiGate revision to confirm the intended policy actually reached the correct target, and investigate any out-of-sync status before closing the change ticket.
  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. 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.
  4. 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.

Answer & Explanations

Correct answer: D

A.

Inspect FortiManager's package status, installation logs and managed FortiGate revision to confirm the intended policy actually reached the correct target, and investigate any out-of-sync status before closing the change ticket. This addresses “Confirm FortiManager package status after a successful installation”, where the governing principle is: A successful central submission is not proof every gateway accepted and enforced the generated policy; per-device execution and database synchronization states provide necessary evidence. The stated 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.

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

C.

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

D.

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

Question 367

A managed services team is preparing policy deployment to two FortiGate form factors and must reconcile their WAN and internal interface maps. The engineer proposes the following change: 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. Which mechanism explains why it works?

  1. 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.
  2. 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.
  3. 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.
  4. A successful central submission is not proof every gateway accepted and enforced the generated policy; per-device execution and database synchronization states provide necessary evidence.

Answer & Explanations

Correct answer: A

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

B.

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

C.

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

D.

A successful central submission is not proof every gateway accepted and enforced the generated policy; per-device execution and database synchronization states provide necessary evidence. That explains “Confirm FortiManager package status after a successful installation”, not the mechanism behind the described change. The relevant 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.

Question 368

A managed services team is preparing policy deployment to two FortiGate form factors and must reconcile their WAN and internal interface maps. After implementing this change—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.—which test most directly validates its intended outcome?

  1. Install a harmless lab policy to two gateways, disconnect one during the task, verify only one successful result and reconcile the failed target after connectivity returns.
  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. 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. 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: C

A.

Install a harmless lab policy to two gateways, disconnect one during the task, verify only one successful result and reconcile the failed target after connectivity returns. That would help test “Confirm FortiManager package status after a successful installation”, not the outcome required in this scenario. The relevant acceptance check is: 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.

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

C.

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

D.

Build a lab package with one permitted and one denied service, assign two approved gateways, preview and install, then confirm an unrelated test firewall is unchanged. That would help test “Choose a FortiManager policy package for a shared branch access standard”, not the outcome required in this scenario. The relevant acceptance check is: 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.

Question 369

A managed services team is preparing policy deployment to two FortiGate form factors and must reconcile their WAN and internal interface maps. Which proposed shortcut most directly risks broken connectivity or bypassed filtering after shared policy interfaces resolve incorrectly on target FortiGates and should therefore be rejected?

  1. Assume a device database interface description edit automatically updates every ADOM policy package and all customer object definitions without an installation or synchronization step.
  2. Close a change ticket after the Install Wizard task is queued and report all customer gateways compliant without checking per-device success and installed revision.
  3. Install a policy package using an unmapped generic interface label across all models and assume FortiManager magically substitutes every local port correctly.
  4. Create a shared rule in FortiManager and assume every registered firewall instantly enforces it regardless of policy-package assignment or the Install Wizard.

Answer & Explanations

Correct answer: C

A.

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: Install a policy package using an unmapped generic interface label across all models and assume FortiManager magically substitutes every local port correctly.

B.

Close a change ticket after the Install Wizard task is queued and report all customer gateways compliant without checking per-device success and installed revision. That shortcut risks false audit evidence and inconsistent network filtering after installation task state is mistaken for device enforcement. Here the specific shortcut is: Install a policy package using an unmapped generic interface label across all models and assume FortiManager magically substitutes every local port correctly.

C.

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. Install a policy package using an unmapped generic interface label across all models and assume FortiManager magically substitutes every local port correctly. The foreseeable failure is broken connectivity or bypassed filtering after shared policy interfaces resolve incorrectly on target FortiGates. The safer response 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.

D.

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: Install a policy package using an unmapped generic interface label across all models and assume FortiManager magically substitutes every local port correctly.

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?

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

Answer & Explanations

Correct answer: A

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.

B.

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.

C.

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.

D.

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.

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