Question 790
At Bluehaven Telecom, an infrastructure review by the carrier access engineering group is evaluating customer support tool reachability across a metropolitan customer service network during a regional modernization (FT-B-01-01). The review finds that a broad all-destinations SD-WAN rule catches a payment SaaS flow before its latency-sensitive rule. Any correction must respect this operating requirement: service management data cannot cross tenant boundaries. Which corrective approach best resolves the observed issue while meeting the operating constraint?
Explanation
Correct Answer
The observed problem is that a broad all-destinations SD-WAN rule catches a payment SaaS flow before its latency-sensitive rule. Reorder and scope the more specific application or destination rule ahead of the generic fallback as part of Bluehaven Telecom's customer support tool reachability update (FT-B-01-01), while enforcing the constraint that service management data cannot cross tenant boundaries. A successful implementation must be checked rather than assumed: In a controlled a metropolitan customer service network acceptance test, Rule diagnostics show the payment session matches the intended application-specific rule; the outcome is recorded under Bluehaven Telecom's rollout (FT-B-01-01). The technical reason is that First-match steering policy design can make generic rules shadow intended exceptions.
Incorrect Answers
The source case reports that a broad all-destinations SD-WAN rule catches a payment SaaS flow before its latency-sensitive rule. The offered alternative is useful for: Choose supported application or internet-service matching appropriate to the SaaS traffic; test both primary and backup paths. In this case the decisive mechanism is: First-match steering policy design can make generic rules shadow intended exceptions. The specific action is “Reorder and scope the more specific application or destination rule ahead of the generic fallback; confirm the dependent routing state”.
The source case reports that a broad all-destinations SD-WAN rule catches a payment SaaS flow before its latency-sensitive rule. “Create an appropriate explicit match if required and review implicit rule behavior; stage the change with an explicit backout plan” addresses the technical dependency: Implicit behavior applies when no higher-priority user-defined rule matches. The reported problem instead follows: First-match steering policy design can make generic rules shadow intended exceptions. The more direct correction is “Reorder and scope the more specific application or destination rule ahead of the generic fallback; confirm the dependent routing state”.
The source case reports that a broad all-destinations SD-WAN rule catches a payment SaaS flow before its latency-sensitive rule. This option would change the control governed by: Parameterized overlay deployment reduces duplicated manual configuration in large fabrics. That does not resolve the present failure, where first-match steering policy design can make generic rules shadow intended exceptions. The applicable response is “Reorder and scope the more specific application or destination rule ahead of the generic fallback; confirm the dependent routing state”.