Fortinet FCP_FMG_AD-7.6 Practice Test 50

Question 490

A FortiManager incident involves FortiManager HA heartbeat state: the team cannot determine whether the HA backup has lost contact with the primary. What targeted troubleshooting check is appropriate?

Check peer identity, reachability and HA settings when a backup does not join
Inspect VRRP mode and routing reachability when takeover requires intervention
Investigate suspended sync or an unreachable peer when pending module data persists
Check the HA path and peer connectivity when the cluster state is Down

Explanation

Correct Answer

This is the focused troubleshooting check for FortiManager HA heartbeat state: check the HA path and peer connectivity when the cluster state is Down. It tests the failure most relevant to the goal to determine whether the HA backup has lost contact with the primary before unrelated settings are changed.

Incorrect Answers

That check is relevant to a fault in FortiManager primary and secondary roles used to provide a recoverable manager control plane using a primary appliance and backup units. It does not directly isolate the described FortiManager HA heartbeat state failure to determine whether the HA backup has lost contact with the primary.

That check is relevant to a fault in FortiManager automatic HA failover mode used to use the supported automatic VRRP-based failover behavior rather than a manual promotion process. It does not directly isolate the described FortiManager HA heartbeat state failure to determine whether the HA backup has lost contact with the primary.

That check is relevant to a fault in FortiManager HA synchronization counters used to prove central policy data replication before depending on a standby for recovery. It does not directly isolate the described FortiManager HA heartbeat state failure to determine whether the HA backup has lost contact with the primary.

Question 491

The operator attempted Scoped API policy-package lookup to retrieve installation target information without editing unrelated ADOM objects, but the expected result is absent. What is the most specific next diagnostic check?

Inspect incorrect ADOM path and permissions when the queried package is absent
Inspect session expiry and login result when a previously working operation fails
Inspect key validity and profile scope on authentication failure
Inspect the profile's API permission when the GUI login works but JSON calls are denied

Explanation

Correct Answer

This is the focused troubleshooting check for Scoped API policy-package lookup: inspect incorrect ADOM path and permissions when the queried package is absent. It tests the failure most relevant to the goal to retrieve installation target information without editing unrelated ADOM objects before unrelated settings are changed.

Incorrect Answers

That check is relevant to a fault in Session-authenticated JSON API login used to use short-lived session IDs for interactive automation. It does not directly isolate the described Scoped API policy-package lookup failure to retrieve installation target information without editing unrelated ADOM objects.

That check is relevant to a fault in REST API administrator key used to authenticate a noninteractive integration without repeated session login. It does not directly isolate the described Scoped API policy-package lookup failure to retrieve installation target information without editing unrelated ADOM objects.

That check is relevant to a fault in JSON API access permission used to allow approved automation to call FortiManager administrative methods. It does not directly isolate the described Scoped API policy-package lookup failure to retrieve installation target information without editing unrelated ADOM objects.

Question 492

A FortiManager incident involves FortiGate-initiated management request: the team cannot approve a firewall that connects to FortiManager seeking central management. What targeted troubleshooting check is appropriate?

Validate CSV columns and duplicate serials when some records do not import
Inspect both member firmware and cluster identity when only one member appears
Check that model details match the actual later serial and platform
Review the FortiGate configured manager address and pending authorization state

Explanation

Correct Answer

This is the focused troubleshooting check for FortiGate-initiated management request: review the FortiGate configured manager address and pending authorization state. It tests the failure most relevant to the goal to approve a firewall that connects to FortiManager seeking central management before unrelated settings are changed.

Incorrect Answers

That check is relevant to a fault in CSV-based offline device onboarding used to add several preplanned inventory entries without manually clicking every record. It does not directly isolate the described FortiGate-initiated management request failure to approve a firewall that connects to FortiManager seeking central management.

That check is relevant to a fault in FortiGate HA cluster device registration used to manage a FortiGate cluster with both members represented centrally. It does not directly isolate the described FortiGate-initiated management request failure to approve a firewall that connects to FortiManager seeking central management.

That check is relevant to a fault in Offline model device registration used to prepare central policy and device settings for hardware not yet connected. It does not directly isolate the described FortiGate-initiated management request failure to approve a firewall that connects to FortiManager seeking central management.

Question 493

The team configured Workflow session submission for the purpose to route a prepared policy change to a designated approval group. What verified state indicates success?

That rule is exclusive while other unlocked policy items remain available
Only package lock owner can change that package until release
Authorized editor can acquire the package without lost approved changes
Submitted session appears awaiting or receiving the required approval

Explanation

Correct Answer

The resulting evidence is specific to Workflow session submission: submitted session appears awaiting or receiving the required approval. It demonstrates the requirement to route a prepared policy change to a designated approval group, rather than merely showing a configuration record was saved.

Incorrect Answers

This result would help verify Workspace-mode individual policy lock and its different task to prevent simultaneous edits to one sensitive rule while another rule can be edited. It does not establish that the requested Workflow session submission outcome has been achieved.

This result would help verify Workspace-mode per-package lock and its different task to let an administrator edit one package without blocking colleagues on unrelated packages. It does not establish that the requested Workflow session submission outcome has been achieved.

This result would help verify Session cleanup after failed editor disconnect and its different task to recover a policy package from a stale writer lock safely. It does not establish that the requested Workflow session submission outcome has been achieved.

Question 494

After configuring Per-policy installation target to deploy a special rule only to a chosen subset within a shared policy package, an administrator observes an unexpected outcome. Which check should be prioritized?

Inspect install targets when a package is offered to an unintended FortiGate
Inspect the rule's per-policy target mapping when an exception appears missing
Compare duplicated package revisions when site policies drift
Examine failed install task if status remains pending after submission

Explanation

Correct Answer

This is the focused troubleshooting check for Per-policy installation target: inspect the rule's per-policy target mapping when an exception appears missing. It tests the failure most relevant to the goal to deploy a special rule only to a chosen subset within a shared policy package before unrelated settings are changed.

Incorrect Answers

That check is relevant to a fault in Policy package installation target used to restrict a change to FortiGates for which it was reviewed. It does not directly isolate the described Per-policy installation target failure to deploy a special rule only to a chosen subset within a shared policy package.

That check is relevant to a fault in Consolidated package strategy used to reduce repetitive changes for devices with essentially identical access policies. It does not directly isolate the described Per-policy installation target failure to deploy a special rule only to a chosen subset within a shared policy package.

That check is relevant to a fault in Policy package status before rollout used to determine whether edits have been installed to the assigned FortiGates. It does not directly isolate the described Per-policy installation target failure to deploy a special rule only to a chosen subset within a shared policy package.

Question 495

For the documented requirement to diagnose a valid policy package sent to an unintended branch gateway, the operator proposes Wrong installation target in package. Which installation or setup action belongs to this choice?

Restore FGFM connectivity and device authorization before rerunning installation
Check package installation targets and each device's ADOM ownership before re-install
Compare generated CLI and feature support against the target device firmware and ADOM version
Identify the device and package lock owner and acquire correct lock under change control

Explanation

Correct Answer

The specific preparation for Wrong installation target in package is to check package installation targets and each device's ADOM ownership before re-install. This addresses the stated need to diagnose a valid policy package sent to an unintended branch gateway, and later acceptance is demonstrated when targeted gateway and generated device policy match the approved change ticket.

Incorrect Answers

That step belongs to Policy install fails on offline device, used to prevent repeated policy pushes to a FortiGate with an unavailable management channel. It is not the mechanism-specific setup for Wrong installation target in package required to diagnose a valid policy package sent to an unintended branch gateway.

That step belongs to Install reports unsupported FortiOS command, used to stop deployment that would push unsupported syntax to a managed FortiGate firmware version. It is not the mechanism-specific setup for Wrong installation target in package required to diagnose a valid policy package sent to an unintended branch gateway.

That step belongs to Workspace lock ownership resolution, used to restore an authorized installation workflow when Workspace mode denies needed edits or installation. It is not the mechanism-specific setup for Wrong installation target in package required to diagnose a valid policy package sent to an unintended branch gateway.

Question 496

Before applying Dynamic subnet object for branch networks for the goal to represent a site's LAN with one reusable logical object in a shared package, which explicitly described setup step belongs to this control?

Review per-target Install Preview for dynamic object substitutions
Review mappings and keep a single authorized value for the target scope
Set branch-specific subnet mappings under the dynamic object
Use device-based dynamic mappings instead of a universal fixed subnet

Explanation

Correct Answer

The specific preparation for Dynamic subnet object for branch networks is to set branch-specific subnet mappings under the dynamic object. This addresses the stated need to represent a site's LAN with one reusable logical object in a shared package, and later acceptance is demonstrated when each branch receives its own approved local subnet after installation.

Incorrect Answers

That step belongs to Device-specific object values in policy preview, used to verify object resolution before a multi-device deployment. It is not the mechanism-specific setup for Dynamic subnet object for branch networks required to represent a site's LAN with one reusable logical object in a shared package.

That step belongs to Dynamic object mapping conflict cleanup, used to remove multiple inconsistent mappings for one FortiGate target. It is not the mechanism-specific setup for Dynamic subnet object for branch networks required to represent a site's LAN with one reusable logical object in a shared package.

That step belongs to Dynamic object versus static address distinction, used to decide when different branch sites require different address values under one rule. It is not the mechanism-specific setup for Dynamic subnet object for branch networks required to represent a site's LAN with one reusable logical object in a shared package.

Question 497

After deploying HA primary role priority observation to check which node is expected to become primary under a supported HA configuration, a reviewer requests operational evidence. Which result best satisfies the acceptance criterion?

Member table shows actual role for each FortiGate
FortiManager recognizes cluster members with expected firmware version
Expected cluster device entries appear as members come online
Cluster role view matches operational HA role and designated priority considerations

Explanation

Correct Answer

The resulting evidence is specific to HA primary role priority observation: cluster role view matches operational HA role and designated priority considerations. It demonstrates the requirement to check which node is expected to become primary under a supported HA configuration, rather than merely showing a configuration record was saved.

Incorrect Answers

This result would help verify FortiGate HA member role view and its different task to determine primary versus secondary members of a centrally managed firewall cluster. It does not establish that the requested HA primary role priority observation outcome has been achieved.

This result would help verify HA cluster firmware consistency and its different task to keep cluster registration from triggering a version conflict. It does not establish that the requested HA primary role priority observation outcome has been achieved.

This result would help verify HA cluster model device entry and its different task to prepare cluster inventory before both managed firewalls are online. It does not establish that the requested HA primary role priority observation outcome has been achieved.

Question 498

A managed environment will use FortiManager manual HA takeover to recover manager operations after primary failure where manual failover is configured. Which preparation check makes the chosen change viable?

Inspect synchronized and pending module data on the HA status page
Explicitly promote an approved secondary to primary under the documented procedure
Configure primary and secondary units and the required HA peer communication reachability
Inspect heartbeat reception and the cluster-status indicator at System Settings HA

Explanation

Correct Answer

The specific preparation for FortiManager manual HA takeover is to explicitly promote an approved secondary to primary under the documented procedure. This addresses the stated need to recover manager operations after primary failure where manual failover is configured, and later acceptance is demonstrated when the promoted appliance advertises Primary role and managed communication resumes.

Incorrect Answers

That step belongs to FortiManager HA synchronization counters, used to prove central policy data replication before depending on a standby for recovery. It is not the mechanism-specific setup for FortiManager manual HA takeover required to recover manager operations after primary failure where manual failover is configured.

That step belongs to FortiManager primary and secondary roles, used to provide a recoverable manager control plane using a primary appliance and backup units. It is not the mechanism-specific setup for FortiManager manual HA takeover required to recover manager operations after primary failure where manual failover is configured.

That step belongs to FortiManager HA heartbeat state, used to determine whether the HA backup has lost contact with the primary. It is not the mechanism-specific setup for FortiManager manual HA takeover required to recover manager operations after primary failure where manual failover is configured.

Question 499

For the documented requirement to open the correct management tenant after authentication, the operator proposes GUI entry to the assigned ADOM. Which installation or setup action belongs to this choice?

Enable ADOMs and grant the administrator access to the intended ADOM
Use a valid FortiCare account during the initial setup process
Connect a management workstation to the default management subnet and launch the initial GUI session
Assign an approved nondefault admin credential at setup

Explanation

Correct Answer

The specific preparation for GUI entry to the assigned ADOM is to enable ADOMs and grant the administrator access to the intended ADOM. This addresses the stated need to open the correct management tenant after authentication, and later acceptance is demonstrated when administrator selects the target ADOM and sees its devices and policy view.

Incorrect Answers

That step belongs to FortiCare registration step, used to satisfy the mandatory initial appliance registration task. It is not the mechanism-specific setup for GUI entry to the assigned ADOM required to open the correct management tenant after authentication.

That step belongs to FortiManager first-login setup wizard, used to complete a new management appliance onboarding before managing FortiGates. It is not the mechanism-specific setup for GUI entry to the assigned ADOM required to open the correct management tenant after authentication.

That step belongs to First administrative password change, used to remove the factory login exposure before shared administration begins. It is not the mechanism-specific setup for GUI entry to the assigned ADOM required to open the correct management tenant after authentication.

Question 500

A FortiManager team implemented FortiManager HA heartbeat state to determine whether the HA backup has lost contact with the primary. Which observed outcome most directly proves the change works?

HA role transfer occurs under the designated failure test without manual secondary promotion
The HA status page shows the intended primary and secondary units as cluster members
Synchronized module data is current and unexpected pending data reaches zero
The expected peer heartbeat is received and cluster status is Up

Explanation

Correct Answer

The resulting evidence is specific to FortiManager HA heartbeat state: the expected peer heartbeat is received and cluster status is Up. It demonstrates the requirement to determine whether the HA backup has lost contact with the primary, rather than merely showing a configuration record was saved.

Incorrect Answers

This result would help verify FortiManager automatic HA failover mode and its different task to use the supported automatic VRRP-based failover behavior rather than a manual promotion process. It does not establish that the requested FortiManager HA heartbeat state outcome has been achieved.

This result would help verify FortiManager primary and secondary roles and its different task to provide a recoverable manager control plane using a primary appliance and backup units. It does not establish that the requested FortiManager HA heartbeat state outcome has been achieved.

This result would help verify FortiManager HA synchronization counters and its different task to prove central policy data replication before depending on a standby for recovery. It does not establish that the requested FortiManager HA heartbeat state outcome has been achieved.

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

Fortinet FCP_FMG_AD-7.6 Practice Test 48 - 10 Questions (Last Reviewed 19-Sep-2026)
Fortinet FCP_FMG_AD-7.6 Practice Test 49 - 10 Questions (Last Reviewed 18-Sep-2026)
Fortinet FCP_FMG_AD-7.6 Practice Test 50 - 10 Questions (Last Reviewed 17-Sep-2026)
Fortinet FCP_FMG_AD-7.6 Practice Test 51 - 10 Questions (Last Reviewed 16-Sep-2026)
Fortinet FCP_FMG_AD-7.6 Practice Test 52 - 10 Questions (Last Reviewed 15-Sep-2026)

Pass Your Fortinet FCP_FMG_AD-7.6 Exam Easy!

Question 490

Explanation

Correct Answer

Incorrect Answers

Question 491

Explanation

Correct Answer

Incorrect Answers

Question 492

Explanation

Correct Answer

Incorrect Answers

Question 493

Explanation

Correct Answer

Incorrect Answers

Question 494

Explanation

Correct Answer

Incorrect Answers

Question 495

Explanation

Correct Answer

Incorrect Answers

Question 496

Explanation

Correct Answer

Incorrect Answers

Question 497

Explanation

Correct Answer

Incorrect Answers

Question 498

Explanation

Correct Answer

Incorrect Answers

Question 499

Explanation

Correct Answer

Incorrect Answers

Question 500

Explanation

Correct Answer

Incorrect Answers

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