Question 370
In a production design review, A branch application is classified under a generic SD-WAN rule before a later business-critical rule can match it. Which next technical step addresses the actual constraint?
Explanation
Correct Answer
Start with the documented issue, not a broad workaround. Review top-down rule priority and move the narrow authorized application rule ahead of the catchall. The rationale is: SD-WAN traffic steering depends on rule lookup order and actual match criteria. Confirm the resulting state: Test application sessions match the business rule rather than the generic rule.
Incorrect Answers
This option serves the scenario “A policy owner expects existing long-running sessions to move immediately after changing a preferred SD-WAN member”. The focused remedy is: Test supported session reevaluation rules and plan an acceptable migration window. The present scenario is distinguished by “Review top-down rule priority and move the narrow authorized application rule ahead of the catchall”.
The suggested action is the untested workaround in the scenario. It fails to account for this requirement: SD-WAN traffic steering depends on rule lookup order and actual match criteria. Use the scoped change: Review top-down rule priority and move the narrow authorized application rule ahead of the catchall.
The related but distinct situation is “An application steering report lists the expected rule but the path changed at a time not covered by current SLA charts”. Correlate SD-WAN rule history, SLA events and session timestamps in analytics. For the stated problem, “Review top-down rule priority and move the narrow authorized application rule ahead of the catchall” addresses the central condition.