Question 560
A post-change incident involves this scenario: A FortiGate high-availability pair is onboarded but FortiManager's inventory does not reflect the expected cluster members. What failure mechanism best explains the concern?
Explanation
Correct Answer
This mechanism explains the problem. The appropriate correction is: Register and manage the HA cluster using the supported FortiManager cluster-discovery workflow.
Incorrect Answers
That risk arises in a different situation: An operator wants to isolate FortiGate firewalls managed for a department without creating a separate full management appliance. This separate concern does not meet the requested action for Treating an HA cluster as unrelated standalone.
That risk arises in a different situation: A device was edited locally during an incident, and its configuration now differs from what FortiManager expects. The current action instead turns on Treating an HA cluster as unrelated standalone.
That risk arises in a different situation: A failed FortiGate HA member has been replaced, and FortiManager still associates device records with the old hardware. The primary requirement remains Treating an HA cluster as unrelated standalone, not that separate capability.