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.

Onboarding imports existing device state into FortiManager's device management database. This mechanism instead applies when a FortiGate has been discovered, but its import report shows inconsistent settings compared with the planned baseline. The current correction relies on template portability does not remove the need to validate destination-specific configuration.

FGFM is the control communication mechanism used for FortiGate and FortiManager management. This mechanism instead applies when a remote FortiGate has working user traffic but its FortiManager management session is disconnected. The current correction relies on template portability does not remove the need to validate destination-specific configuration.

Template provisioning can reuse configuration while preserving necessary device-specific differences. This mechanism instead applies when a provider wants a single baseline template to configure devices with different interface names and hardware platforms. The current correction relies on template portability does not remove the need to validate destination-specific configuration.

Validation and test traffic show the FQDN object matches only the intended authorized destination. That observation is relevant for the separate case an administrator prepares a policy package that contains an object referencing a deleted FQDN resource. Here the decisive evidence is installation preview includes exactly the intended devices for that rule and package.

The new rule refers to authorized local addresses and passes target-specific validation. That observation is relevant for the separate case an administrator copies a policy rule from another ADOM without updating addresses for the new location. Here the decisive evidence is installation preview includes exactly the intended devices for that rule and package.

Policy validation identifies a supported configuration for the upgraded device release. That observation is relevant for the separate case a customer upgrades FortiOS but its central package still contains features unsupported by the target's firmware. Here the decisive evidence is installation preview includes exactly the intended devices for that rule and package.

FortiManager feature and device limits depend on the installed license entitlement. This mechanism instead applies when a FortiManager virtual appliance starts but license activation has not been completed. The current correction relies on a complete migration includes dependent services beyond transferring configuration files.

FortiManager can perform core management in environments with restricted external connectivity. This mechanism instead applies when a deployment in a restricted network has no direct internet access but needs centrally managed device configuration. The current correction relies on a complete migration includes dependent services beyond transferring configuration files.

Certificate validation protects the identity of a privileged management interface. This mechanism instead applies when a new FortiManager installation receives an unexpected system certificate warning from an administrator workstation. The current correction relies on a complete migration includes dependent services beyond transferring configuration files.

Confirm the peer has current synchronized modules before initiating the approved failover procedure. This can be appropriate when a maintenance window requires promoting a secondary FortiManager with unconfirmed synchronized policy data. It does not directly address the present situation, where the required correction is check Module Data Synchronized and Pending Module Data values in the HA status details.

Include administrator access and management-task continuity in the HA acceptance plan. This can be appropriate when an enterprise plans to test FortiManager HA but has not checked how administrative sessions reconnect to the promoted unit. It does not directly address the present situation, where the required correction is check Module Data Synchronized and Pending Module Data values in the HA status details.

Distinguish management-server continuity checks from gateway traffic-path failover testing. This can be appropriate when an operations team confuses a FortiManager HA failover with FortiGate Cluster HA packet-forwarding behavior. It does not directly address the present situation, where the required correction is check Module Data Synchronized and Pending Module Data values in the HA status details.

Incorrect ADOM membership can expose customer configuration to unrelated administrators. That consequence is more specific to an administrator imports a FortiGate into the wrong tenant ADOM and later notices a policy scope mismatch. For this case, the most direct exposure is device registration by itself does not install a centralized firewall policy.

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 device registration by itself does not install a centralized firewall policy.

Blind cross-ADOM template reuse can overwrite valid local addresses or service values. That consequence is more specific to a provisioning engineer copies a system template from a retail ADOM into a finance ADOM without checking environment differences. For this case, the most direct exposure is device registration by itself does not install a centralized firewall policy.

Central object inventories can be shared by multiple policies and must be reference-checked. This mechanism instead applies when an object cleanup plan proposes deleting all address objects that are not shown in the first policy table. The current correction relies on centralized object management exposes dependencies between shared objects and policies.

FortiManager policy management depends on consistent object and security-profile references. This mechanism instead applies when a managed firewall requires IPS protection but the policy package references a profile missing from the ADOM object inventory. The current correction relies on centralized object management exposes dependencies between shared objects and policies.

Policy authoring in FortiManager and deployment onto a FortiGate are separate operations. This mechanism instead applies when a newly authored firewall rule is committed centrally but remains absent from the target FortiGate rulebase. The current correction relies on centralized object management exposes dependencies between shared objects and policies.

System templates supply reusable device-level baseline settings through FortiManager. This mechanism instead applies when a fleet of branch appliances requires identical DNS and NTP settings but is being configured by hand on every unit. The current correction relies on model device correlation depends on accurate unique device identifiers and deployment metadata.

FGFM is the control communication mechanism used for FortiGate and FortiManager management. This mechanism instead applies when a remote FortiGate has working user traffic but its FortiManager management session is disconnected. The current correction relies on model device correlation depends on accurate unique device identifiers and deployment metadata.

FortiGate uses configured central management endpoints to communicate with FortiManager. This mechanism instead applies when a new FortiGate cannot contact its FortiManager because the device was configured with the wrong central manager address. The current correction relies on model device correlation depends on accurate unique device identifiers and deployment metadata.

Obtain the ADOM-level lock required for device creation under the relevant workspace configuration. This can be appropriate when a team wants to create a new device in an unlocked ADOM while only a different package is locked. It does not directly address the present situation, where the required correction is check whether the device can be locked independently under the configured workspace and ADOM mode.

Identify the abandoned session and use the approved lock-release procedure with change recovery. This can be appropriate when an administrator disconnects while holding an ADOM lock and a peer cannot continue urgent work. It does not directly address the present situation, where the required correction is check whether the device can be locked independently under the configured workspace and ADOM mode.

Configure supported per-ADOM workspace settings and validate the behavior of each delegated tenant. This can be appropriate when an MSP wants each tenant ADOM to use a different editing collaboration model. It does not directly address the present situation, where the required correction is check whether the device can be locked independently under the configured workspace and ADOM mode.

A management session is established using the approved reachable endpoint across NAT. That observation is relevant for the separate case a FortiGate behind a branch NAT device cannot establish central management to FortiManager at headquarters. Here the decisive evidence is a trusted FGFM session persists between the correct devices despite the overlapping internal subnets.

User traffic follows intended FortiGate paths while FortiManager handles central configuration operations. That observation is relevant for the separate case an enterprise incorrectly treats FortiManager as the live traffic gateway and routes branch user packets through its management interface. Here the decisive evidence is a trusted FGFM session persists between the correct devices despite the overlapping internal subnets.

Remote gateways reach the intended manager and finish authorized device registration. That observation is relevant for the separate case FortiManager is located behind a data-center NAT device, and newly installed remote gateways cannot complete registration. Here the decisive evidence is a trusted FGFM session persists between the correct devices despite the overlapping internal subnets.

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 without checking the insertion block, teams may misunderstand rule precedence between global and local policy.

Overbroad global policy assignment can change unrelated customer traffic decisions. That consequence is more specific to a global policy rule is deployed to one customer, but another tenant's policy installation should remain unaffected. For this case, the most direct exposure is without checking the insertion block, teams may misunderstand rule precedence between global and local policy.

Global package schema incompatibility can prevent assignment to a target ADOM. That consequence is more specific to an ADOM is absent from the global-policy assignment dialog after its FortiOS version was upgraded. For this case, the most direct exposure is without checking the insertion block, teams may misunderstand rule precedence between global and local policy.