Question 540
A team proposes to close this Fortinet incident: A branch policy refers to an obsolete SD-WAN member even after a new member has been added to its zone. Which verification should it require?
Explanation
Correct Answer
That result demonstrates end-to-end success rather than a saved configuration. The focused action is: Update the targeted rule's preferred candidate list and check the live member IDs. The mechanism at issue is: Rule membership preferences and eligible interfaces require updating during link replacement.
Incorrect Answers
The related but distinct situation is “After resolving New SaaS sessions use an unexpected member because application classification needs early packets before the application is recognized”. The check verifies the actual business or network path after the step: Review application learning and first-packet matching behavior alongside the chosen strategy. For the stated problem, “New eligible sessions choose the approved replacement link” addresses the central condition.
This choice addresses a different case in the same task group: An SD-WAN policy sets one carrier as preferred but operators assume preference guarantees selection even when the member is down. The present situation is: A branch policy refers to an obsolete SD-WAN member even after a new member has been added to its zone. Its decisive proof is: New eligible sessions choose the approved replacement link.
This alternative addresses the separate case “For this FortiSASE or SD-WAN problem, A voice traffic rule uses a lowest-cost strategy even when one eligible member violates voice latency requirements”. This is the specific acceptance result for the remediation: Choose a strategy that prioritizes members meeting the configured voice SLA. The deciding requirement here is “New eligible sessions choose the approved replacement link”.