Fortinet FCP_FMG_AD-7.6 Practice Test 36

Question 350

The change ticket requires the management team to use one logical interface name across FortiGates with different physical port names. Which capability should lead the solution?

Interface-mapping changes and revision control
Normalized interface for shared policy
Zone mapping for managed firewalls
Normalized interface missing-map alert

Explanation

Correct Answer

Normalized interface for shared policy fits this operational requirement: use one logical interface name across FortiGates with different physical port names. The implementation begins by ensuring that administrators define a normalized interface and map it to each target's actual interface; success is confirmed when shared policy compiles to the correct local interface on each FortiGate.

Incorrect Answers

Interface-mapping changes and revision control is suited to a different task: preserve a tested site's port mapping through a centralized policy update. It does not directly meet the specified goal to use one logical interface name across FortiGates with different physical port names; selecting it would address a different management function.

Zone mapping for managed firewalls is suited to a different task: abstract a common security zone across FortiGates using different interface membership. It does not directly meet the specified goal to use one logical interface name across FortiGates with different physical port names; selecting it would address a different management function.

Normalized interface missing-map alert is suited to a different task: identify an install failure caused by an unmapped policy interface. It does not directly meet the specified goal to use one logical interface name across FortiGates with different physical port names; selecting it would address a different management function.

Question 351

The change record says Global package change impact review should prevent one shared policy edit from silently affecting unrelated managed sites. Which result demonstrates that the intended state was reached?

Assigned ADOM policy compilation resolves approved shared object references
Shared policy installation and update-package synchronization remain separately observable
Generated policy places common header rules before and footer rules after ADOM-specific rules
Impact assessment names all intended ADOMs and installation targets

Explanation

Correct Answer

The resulting evidence is specific to Global package change impact review: impact assessment names all intended ADOMs and installation targets. It demonstrates the requirement to prevent one shared policy edit from silently affecting unrelated managed sites, rather than merely showing a configuration record was saved.

Incorrect Answers

This result would help verify Global object availability for ADOM policy and its different task to reuse controlled organization-wide object definitions across assigned ADOMs. It does not establish that the requested Global package change impact review outcome has been achieved.

This result would help verify Global policy versus FortiGuard configuration and its different task to choose the correct management plane for security rules rather than signature service updates. It does not establish that the requested Global package change impact review outcome has been achieved.

This result would help verify Global policy header and footer ordering and its different task to guarantee that common security controls occupy a predetermined position around local rules. It does not establish that the requested Global package change impact review outcome has been achieved.

Question 352

For the documented requirement to describe common intended device provisioning settings before enrollment, the operator proposes Device blueprint for standardized models. Which installation or setup action belongs to this choice?

Review device assignment and install preview for the template-backed change
Copy the template into a compatible destination ADOM
Create a compatible system template and assign intended devices
Associate a supported blueprint with the intended model device class

Explanation

Correct Answer

The specific preparation for Device blueprint for standardized models is to associate a supported blueprint with the intended model device class. This addresses the stated need to describe common intended device provisioning settings before enrollment, and later acceptance is demonstrated when new model device inherits the approved blueprint choices.

Incorrect Answers

That step belongs to Template installation target check, used to prevent a shared settings template from modifying the wrong firewall. It is not the mechanism-specific setup for Device blueprint for standardized models required to describe common intended device provisioning settings before enrollment.

That step belongs to Copy system templates across ADOMs, used to reuse an approved baseline without rebuilding it in each management tenant. It is not the mechanism-specific setup for Device blueprint for standardized models required to describe common intended device provisioning settings before enrollment.

That step belongs to System template for shared baseline, used to reuse a common device setting across multiple managed FortiGates. It is not the mechanism-specific setup for Device blueprint for standardized models required to describe common intended device provisioning settings before enrollment.

Question 353

An administrator reports success using Policy import after local FortiGate change to reconcile out-of-band local firewall rule changes into central management. Which control-specific limitation still applies?

Importing policy is not the same operation as installing a new package to the FortiGate
Import mapping concerns policy references, not the FortiGate physical switch port configuration
A wizard completion screen alone is not proof every rule was imported
Retrieving device config alone does not update the ADOM policy package

Explanation

Correct Answer

The stated scope boundary specifically qualifies Policy import after local FortiGate change: retrieving device config alone does not update the ADOM policy package. The control is appropriate for the operational need to reconcile out-of-band local firewall rule changes into central management, but should not be credited with unrelated behavior.

Incorrect Answers

That caveat describes Policy import wizard for managed FortiGate in a different management scenario, which addresses bring existing device-side access rules into the FortiManager policy database. It is not the specific limitation of Policy import after local FortiGate change requested in this design review.

That caveat describes Import wizard interface mapping review in a different management scenario, which addresses prevent device-specific interfaces from being lost during policy import. It is not the specific limitation of Policy import after local FortiGate change requested in this design review.

That caveat describes Import summary and report in a different management scenario, which addresses distinguish successful policy import from silent partial failure. It is not the specific limitation of Policy import after local FortiGate change requested in this design review.

Question 354

The change record says Revision rollback selection after incident should avoid reversing legitimate newer changes while attempting to recover a known good device configuration. Which result demonstrates that the intended state was reached?

A supported conversion and retrieve reconcile the configuration without unsupported command errors
Selected rollback restores exactly the intended configuration delta
Targeted differences are identified and reconciled through an approved retrieve or install
Discrepancy is attributed to the correct database before choosing retrieve or import

Explanation

Correct Answer

The resulting evidence is specific to Revision rollback selection after incident: selected rollback restores exactly the intended configuration delta. It demonstrates the requirement to avoid reversing legitimate newer changes while attempting to recover a known good device configuration, rather than merely showing a configuration record was saved.

Incorrect Answers

This result would help verify Out-of-sync after firmware or ADOM upgrade and its different task to distinguish a version-conversion issue from a lost FGFM tunnel after a firmware change. It does not establish that the requested Revision rollback selection after incident outcome has been achieved.

This result would help verify Device database out-of-sync status and its different task to investigate a managed FortiGate whose actual configuration diverged from its FortiManager device database. It does not establish that the requested Revision rollback selection after incident outcome has been achieved.

This result would help verify Device database versus ADOM policy database and its different task to find why device configuration reports current while an ADOM firewall rule is absent. It does not establish that the requested Revision rollback selection after incident outcome has been achieved.

Question 355

After configuring Out-of-sync after firmware or ADOM upgrade to distinguish a version-conversion issue from a lost FGFM tunnel after a firmware change, an administrator observes an unexpected outcome. Which check should be prioritized?

Inspect latest device revision and configuration status before overwriting a valid local change
Inspect source database and package revision when views disagree
Review conversion logs when the device is reachable but central settings fail to compile
Inspect change timestamps and admin audit records when device status shifts unexpectedly

Explanation

Correct Answer

This is the focused troubleshooting check for Out-of-sync after firmware or ADOM upgrade: review conversion logs when the device is reachable but central settings fail to compile. It tests the failure most relevant to the goal to distinguish a version-conversion issue from a lost FGFM tunnel after a firmware change before unrelated settings are changed.

Incorrect Answers

That check is relevant to a fault in Device database out-of-sync status used to investigate a managed FortiGate whose actual configuration diverged from its FortiManager device database. It does not directly isolate the described Out-of-sync after firmware or ADOM upgrade failure to distinguish a version-conversion issue from a lost FGFM tunnel after a firmware change.

That check is relevant to a fault in Device database versus ADOM policy database used to find why device configuration reports current while an ADOM firewall rule is absent. It does not directly isolate the described Out-of-sync after firmware or ADOM upgrade failure to distinguish a version-conversion issue from a lost FGFM tunnel after a firmware change.

That check is relevant to a fault in Unexpected local FortiGate configuration edit used to detect manual changes introduced outside the approved FortiManager workflow. It does not directly isolate the described Out-of-sync after firmware or ADOM upgrade failure to distinguish a version-conversion issue from a lost FGFM tunnel after a firmware change.

Question 356

A FortiManager incident involves Backup restore validation for manager outage: the team cannot verify a FortiManager recovery copy before declaring the management system recoverable. What targeted troubleshooting check is appropriate?

Inspect swap/memory and running task history when services restart unexpectedly
Inspect database errors before rerunning policy imports when records are corrupt
Examine disk allocation and log growth when install tasks fail with filesystem write errors
Inspect backup version and compatibility when recovery omits policy objects

Explanation

Correct Answer

This is the focused troubleshooting check for Backup restore validation for manager outage: inspect backup version and compatibility when recovery omits policy objects. It tests the failure most relevant to the goal to verify a FortiManager recovery copy before declaring the management system recoverable before unrelated settings are changed.

Incorrect Answers

That check is relevant to a fault in FortiManager memory pressure used to distinguish memory exhaustion from unreachable devices when administrative sessions unexpectedly terminate. It does not directly isolate the described Backup restore validation for manager outage failure to verify a FortiManager recovery copy before declaring the management system recoverable.

That check is relevant to a fault in Database integrity after abrupt shutdown used to recover cleanly from a manager power loss that leaves databases inconsistent. It does not directly isolate the described Backup restore validation for manager outage failure to verify a FortiManager recovery copy before declaring the management system recoverable.

That check is relevant to a fault in High FortiManager disk utilization used to recover management tasks failing because logs, reports or databases have consumed available storage. It does not directly isolate the described Backup restore validation for manager outage failure to verify a FortiManager recovery copy before declaring the management system recoverable.

Question 357

The team configured GUI entry to the assigned ADOM for the purpose to open the correct management tenant after authentication. What verified state indicates success?

Subsequent GUI login requires the new administrative password
Virtual unit license status is valid and administrative setup can proceed
A FortiManager Setup wizard appears for the newly initialized appliance
Administrator selects the target ADOM and sees its devices and policy view

Explanation

Correct Answer

The resulting evidence is specific to GUI entry to the assigned ADOM: administrator selects the target ADOM and sees its devices and policy view. It demonstrates the requirement to open the correct management tenant after authentication, rather than merely showing a configuration record was saved.

Incorrect Answers

This result would help verify First administrative password change and its different task to remove the factory login exposure before shared administration begins. It does not establish that the requested GUI entry to the assigned ADOM outcome has been achieved.

This result would help verify FortiManager VM initial licensing and its different task to activate a newly deployed virtual manager before normal GUI administration. It does not establish that the requested GUI entry to the assigned ADOM outcome has been achieved.

This result would help verify FortiManager first-login setup wizard and its different task to complete a new management appliance onboarding before managing FortiGates. It does not establish that the requested GUI entry to the assigned ADOM outcome has been achieved.

Question 358

The team configured FortiManager local FDS activation for the purpose to reduce external update network use for many managed FortiGate devices. What verified state indicates success?

Client rating requests are serviced through the configured manager address
Managed FortiGates retrieve supported updates from the intended local manager service
The offline FDS offers the explicitly imported valid package versions to clients
The local package inventory shows expected newer update content

Explanation

Correct Answer

The resulting evidence is specific to FortiManager local FDS activation: managed FortiGates retrieve supported updates from the intended local manager service. It demonstrates the requirement to reduce external update network use for many managed FortiGate devices, rather than merely showing a configuration record was saved.

Incorrect Answers

This result would help verify FortiGuard rating-service override and its different task to steer supported FortiGate rating lookups toward a centrally hosted local FortiManager endpoint. It does not establish that the requested FortiManager local FDS activation outcome has been achieved.

This result would help verify Closed-network FDS package import and its different task to keep a supported isolated FortiManager update environment functional without direct Internet FDN connectivity. It does not establish that the requested FortiManager local FDS activation outcome has been achieved.

This result would help verify FortiGuard antivirus and IPS package download and its different task to maintain locally available AV and IPS update content for managed devices. It does not establish that the requested FortiManager local FDS activation outcome has been achieved.

Question 359

The team chose System template for shared baseline for the purpose to reuse a common device setting across multiple managed FortiGates. Which boundary on this control must remain explicit in the design?

Zero-touch model preparation does not prove first-boot connectivity
Blueprints do not authenticate an untrusted FortiGate automatically
System templates do not replace policy packages for complete firewall access rules
Copying a template is not equivalent to copying devices or all their installed policies

Explanation

Correct Answer

The stated scope boundary specifically qualifies System template for shared baseline: system templates do not replace policy packages for complete firewall access rules. The control is appropriate for the operational need to reuse a common device setting across multiple managed FortiGates, but should not be credited with unrelated behavior.

Incorrect Answers

That caveat describes Template provisioning to a model device in a different management scenario, which addresses prepare network settings before a newly ordered FortiGate is online. It is not the specific limitation of System template for shared baseline requested in this design review.

That caveat describes Device blueprint for standardized models in a different management scenario, which addresses describe common intended device provisioning settings before enrollment. It is not the specific limitation of System template for shared baseline requested in this design review.

That caveat describes Copy system templates across ADOMs in a different management scenario, which addresses reuse an approved baseline without rebuilding it in each management tenant. It is not the specific limitation of System template for shared baseline requested in this design review.

Question 360

An issue persists after implementing Policy-package editing after lock release for the goal to restore safe concurrent editing following an approved workspace change. Which focused investigation best isolates this failure?

Check whether another administrator holds the package lock if editing is blocked
Check stale sessions or lock ownership after the original editor logs out
Inspect lock owner and session if a permitted operator sees read-only controls
Examine session submission and approval state if changes are not accepted

Explanation

Correct Answer

This is the focused troubleshooting check for Policy-package editing after lock release: check stale sessions or lock ownership after the original editor logs out. It tests the failure most relevant to the goal to restore safe concurrent editing following an approved workspace change before unrelated settings are changed.

Incorrect Answers

That check is relevant to a fault in Individual policy-package lock used to let administrators safely edit different packages within one ADOM. It does not directly isolate the described Policy-package editing after lock release failure to restore safe concurrent editing following an approved workspace change.

That check is relevant to a fault in ADOM workspace lock used to prevent conflicting concurrent changes across a shared ADOM during an approved change. It does not directly isolate the described Policy-package editing after lock release failure to restore safe concurrent editing following an approved workspace change.

That check is relevant to a fault in Workflow change session used to require submitted approval before a policy change moves through team controls. It does not directly isolate the described Policy-package editing after lock release failure to restore safe concurrent editing following an approved workspace change.

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

Fortinet FCP_FMG_AD-7.6 Practice Test 34 - 10 Questions (Last Reviewed 03-Oct-2026)
Fortinet FCP_FMG_AD-7.6 Practice Test 35 - 10 Questions (Last Reviewed 02-Oct-2026)
Fortinet FCP_FMG_AD-7.6 Practice Test 36 - 10 Questions (Last Reviewed 01-Oct-2026)
Fortinet FCP_FMG_AD-7.6 Practice Test 37 - 10 Questions (Last Reviewed 30-Sep-2026)
Fortinet FCP_FMG_AD-7.6 Practice Test 38 - 10 Questions (Last Reviewed 29-Sep-2026)

Pass Your Fortinet FCP_FMG_AD-7.6 Exam Easy!

Question 350

Explanation

Correct Answer

Incorrect Answers

Question 351

Explanation

Correct Answer

Incorrect Answers

Question 352

Explanation

Correct Answer

Incorrect Answers

Question 353

Explanation

Correct Answer

Incorrect Answers

Question 354

Explanation

Correct Answer

Incorrect Answers

Question 355

Explanation

Correct Answer

Incorrect Answers

Question 356

Explanation

Correct Answer

Incorrect Answers

Question 357

Explanation

Correct Answer

Incorrect Answers

Question 358

Explanation

Correct Answer

Incorrect Answers

Question 359

Explanation

Correct Answer

Incorrect Answers

Question 360

Explanation

Correct Answer

Incorrect Answers

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