Question 520
A Fortinet SD-WAN/FortiSASE operations team encounters the following situation: A 200-site deployment uses FortiManager, but each operator has manually defined different health-check objects for the same application class. Which sustained control would best prevent this same failure from recurring?
Explanation
Correct Answer
This guard addresses the recurring failure mode demonstrated by the case: Uncontrolled manual configuration creates inconsistent steering behavior across sites. It guards the same affected workflow, rather than merely checking that some other service works. A successful controlled outcome would be: Representative branches show equivalent monitoring logic with only approved local deviations.
Incorrect Answers
This control is relevant to another scenario in the stated requirement, specifically: An engineering team pushes a new SD-WAN zone naming convention, yet FortiManager install previews show multiple dependent policies would become unresolved. It would not prevent the present mechanism: Uncontrolled manual configuration creates inconsistent steering behavior across sites. Prevention must be linked to that actual failure mode rather than a generic adjacent control.
This control is relevant to another scenario in the stated requirement, specifically: A new region's FortiSASE policy has been deployed, but the central team's dashboard does not distinguish SASE issues from SD-WAN member failures. It would not prevent the present mechanism: Uncontrolled manual configuration creates inconsistent steering behavior across sites. Prevention must be linked to that actual failure mode rather than a generic adjacent control.
This control is relevant to another scenario in the stated requirement, specifically: A regional office changes an SD-WAN policy locally, but the centralized FortiManager template later silently restores the old preferred member. It would not prevent the present mechanism: Uncontrolled manual configuration creates inconsistent steering behavior across sites. Prevention must be linked to that actual failure mode rather than a generic adjacent control.