Run documented filesystem integrity checks and restore affected management databases when justified. This can be appropriate when after unexpected power loss, FortiManager displays inconsistent database errors in installation tasks. It does not directly address the present situation, where the required correction is adjust the maintenance schedule and task concurrency based on observed system capacity.

Test outbound FortiGuard and proxy connectivity independently of FGFM device sessions. This can be appropriate when a FortiManager cannot download updates after a proxy configuration change, while device management over FGFM remains healthy. It does not directly address the present situation, where the required correction is adjust the maintenance schedule and task concurrency based on observed system capacity.

Use the supported replacement-device workflow and update the registered managed identity. This can be appropriate when a firewall replacement boots successfully, yet FortiManager continues sending tasks to the failed old serial. It does not directly address the present situation, where the required correction is adjust the maintenance schedule and task concurrency based on observed system capacity.

Relying on tenants to copy mandatory rules manually can yield inconsistent global controls. That consequence is more specific to an enterprise requires every tenant ADOM policy to start with centrally mandated deny rules. For this case, the most direct exposure is global package schema incompatibility can prevent assignment to a target ADOM.

Assuming unlimited global packages per local package can create invalid configuration design. That consequence is more specific to an administrator attempts to assign two separate global policy packages to one individual local policy package simultaneously. For this case, the most direct exposure is global package schema incompatibility can prevent assignment to a target ADOM.

Duplicating mandatory objects manually can lead to mismatched organization-wide controls. That consequence is more specific to a provider wants to share a mandatory address object across customer ADOMs but maintain tenant-specific optional objects. For this case, the most direct exposure is global package schema incompatibility can prevent assignment to a target ADOM.

The staged rollout completes with stable management CPU, memory and disk headroom. That observation is relevant for the separate case a central management appliance exhausts resources during a firmware rollout because all managed devices were scheduled at once. Here the decisive evidence is management connections remain stable under the monitored test period with expected keepalives.

The replacement serial receives the approved policy package and appears online. That observation is relevant for the separate case a firewall replacement boots successfully, yet FortiManager continues sending tasks to the failed old serial. Here the decisive evidence is management connections remain stable under the monitored test period with expected keepalives.

Support evidence identifies the precise subsystem and time of the reproducible fault. That observation is relevant for the separate case an administrator reviews an unfamiliar FortiManager error but only has a screenshot of the management GUI. Here the decisive evidence is management connections remain stable under the monitored test period with expected keepalives.

The matching traffic hits the reviewed deny rule before broader permission is considered. That observation is relevant for the separate case a security engineer adds a deny rule under a broad permissive rule but sees no change in traffic decisions. Here the decisive evidence is the FortiGate running configuration and controlled traffic reflect the intended inspection behavior.

A per-device mapping report shows exactly one approved physical or zone mapping for each site. That observation is relevant for the separate case a policy package includes two similarly named interface mappings and engineers are unsure which target uses each one. Here the decisive evidence is the FortiGate running configuration and controlled traffic reflect the intended inspection behavior.

The policy review includes recent measured usage context for each candidate rule. That observation is relevant for the separate case a network team wants to compare expected policy use across several branches but never reviews rule hit counts. Here the decisive evidence is the FortiGate running configuration and controlled traffic reflect the intended inspection behavior.

The chosen revision remains listed after the automated retention cleanup runs. That observation is relevant for the separate case an ADOM revision was automatically purged even though the audit team needed to preserve it. Here the decisive evidence is the investigation identifies the correct snapshot for firewall device settings versus shared policy objects.

The required baseline exists as a separate identifiable ADOM revision. That observation is relevant for the separate case a policy change is made and deployed but the team forgets whether it created a new ADOM snapshot. Here the decisive evidence is the investigation identifies the correct snapshot for firewall device settings versus shared policy objects.

The relevant baseline snapshot has traceable creator and change-context information. That observation is relevant for the separate case a SOC team asks who created a policy baseline revision before a high-risk maintenance event. Here the decisive evidence is the investigation identifies the correct snapshot for firewall device settings versus shared policy objects.

Script execution history shows successful configuration on precisely the intended gateways. That observation is relevant for the separate case an engineer plans to change the same NTP server on 60 gateways using manual command-line sessions. Here the decisive evidence is task Monitor shows no further executions against the retired device group.

The run log contains required device diagnostic output and shows no configuration changes. That observation is relevant for the separate case a network engineer needs a controlled one-time diagnostic command across several managed firewalls without saving a permanent policy. Here the decisive evidence is task Monitor shows no further executions against the retired device group.

A reviewer can trace the new script revision to a validated target and outcome. That observation is relevant for the separate case an engineer edits a saved script without updating its documented purpose and target risk. Here the decisive evidence is task Monitor shows no further executions against the retired device group.

Restrict administrative access to approved management networks while preserving gateway FGFM reachability. This can be appropriate when a company places FortiManager in a dedicated management segment but opens its GUI to all public networks for convenience. It does not directly address the present situation, where the required correction is configure supported translated reachability and gateway manager addressing for the NATed central server.

Verify the correct public or translated manager endpoint and permitted FGFM path through the NAT device. This can be appropriate when a FortiGate behind a branch NAT device cannot establish central management to FortiManager at headquarters. It does not directly address the present situation, where the required correction is configure supported translated reachability and gateway manager addressing for the NATed central server.

Keep FortiManager on the management plane and retain FortiGate data-plane packet forwarding. This can be appropriate when an enterprise incorrectly treats FortiManager as the live traffic gateway and routes branch user packets through its management interface. It does not directly address the present situation, where the required correction is configure supported translated reachability and gateway manager addressing for the NATed central server.

Stale member inventory can mislead future provisioning and maintenance actions. That consequence is more specific to a FortiGate HA cluster adds a replacement secondary member, but FortiManager still displays the old member inventory. For this case, the most direct exposure is separate unmanaged records for one HA pair can create inconsistent member targeting.

An incorrect identity match may leave the intended blueprint unused or applied incorrectly. That consequence is more specific to an offline model device has no known serial number and the selected onboarding method requires a serial match. For this case, the most direct exposure is separate unmanaged records for one HA pair can create inconsistent member targeting.

Duplicate model identity metadata can cause ambiguous registration and provisioning results. That consequence is more specific to an offline branch uses a model device entry, but two appliances share a reused blueprint identifier in a batch import. For this case, the most direct exposure is separate unmanaged records for one HA pair can create inconsistent member targeting.

Import review reconciles device-side configuration with central ADOM policy databases. This mechanism instead applies when a policy import finishes but the device's latest configuration still contains objects not represented in FortiManager. The current correction relies on install Wizard validation reports target-specific problems requiring corrective action.

Configuration deployment and functional policy acceptance are separate verification stages. This mechanism instead applies when an installation completes without task errors but users still report blocked traffic that the new rule should permit. The current correction relies on install Wizard validation reports target-specific problems requiring corrective action.

FortiManager can reinstall an existing managed package when the device requires resynchronization. This mechanism instead applies when a production gateway has an approved policy package that needs reinstallation after an out-of-band device restore. The current correction relies on install Wizard validation reports target-specific problems requiring corrective action.

Refresh device information and update the dynamic interface mapping to the current interface identity. This can be appropriate when a FortiGate's interface is renamed locally, leaving a centrally managed policy with an outdated interface mapping. It does not directly address the present situation, where the required correction is use an appropriate dynamic address object with per-device mapping rather than one fixed value everywhere.

Use the unused-object analysis and check cross-package references before removal. This can be appropriate when an object cleanup plan proposes deleting all address objects that are not shown in the first policy table. It does not directly address the present situation, where the required correction is use an appropriate dynamic address object with per-device mapping rather than one fixed value everywhere.

Define supported ADOM metadata variables and map approved values for affected devices. This can be appropriate when a multi-site policy uses one object placeholder for location-specific DNS hosts. It does not directly address the present situation, where the required correction is use an appropriate dynamic address object with per-device mapping rather than one fixed value everywhere.

Authorized users can manage intended devices through the active member after controlled failover. That observation is relevant for the separate case an enterprise plans to test FortiManager HA but has not checked how administrative sessions reconnect to the promoted unit. Here the decisive evidence is pending data reaches the expected synchronized state before a planned changeover.

Pending-module count decreases and the secondary reaches an acceptable synchronized state. That observation is relevant for the separate case a secondary FortiManager reports a large pending module synchronization backlog during peak network usage. Here the decisive evidence is pending data reaches the expected synchronized state before a planned changeover.

System Settings HA reports expected peer roles and healthy cluster reachability. That observation is relevant for the separate case two FortiManager appliances must protect centralized policy administration from a single management-server failure. Here the decisive evidence is pending data reaches the expected synchronized state before a planned changeover.