Question 490
At Falcon Security MSP, an infrastructure review by the provider services group is evaluating customer tenant connectivity across a managed multitenant edge platform during a regional modernization (FT-B-06-01). The review finds that an application appears on the wrong WAN and engineers modify SLA targets without confirming its matching rule. Any correction must respect this operating requirement: one customer cannot see or change another customer network. Which corrective approach best resolves the observed issue while meeting the operating constraint?
Explanation
Correct Answer
The observed problem is that an application appears on the wrong WAN and engineers modify SLA targets without confirming its matching rule. Trace the session against SD-WAN service matching and selected member before tuning thresholds as part of Falcon Security MSP's customer tenant connectivity update (FT-B-06-01), while enforcing the constraint that one customer cannot see or change another customer network. A successful implementation must be checked rather than assumed: In a controlled a managed multitenant edge platform acceptance test, The diagnostic record identifies the actual matched rule and path for the session; the outcome is recorded under Falcon Security MSP's rollout (FT-B-06-01). The technical reason is that Matching and quality-based member choice are separate stages of SD-WAN processing.
Incorrect Answers
The source case reports that an application appears on the wrong WAN and engineers modify SLA targets without confirming its matching rule. The offered alternative is useful for: SD-WAN rule strategy determines how eligible path metrics affect selection. In this case the decisive mechanism is: Matching and quality-based member choice are separate stages of SD-WAN processing. The specific action is “Trace the session against SD-WAN service matching and selected member before tuning thresholds; test both primary and backup paths”.
The source case reports that an application appears on the wrong WAN and engineers modify SLA targets without confirming its matching rule. “Reorder and scope the more specific application or destination rule ahead of the generic fallback; confirm the dependent routing state” addresses the technical dependency: First-match steering policy design can make generic rules shadow intended exceptions. The reported problem instead follows: Matching and quality-based member choice are separate stages of SD-WAN processing. The more direct correction is “Trace the session against SD-WAN service matching and selected member before tuning thresholds; test both primary and backup paths”.
The source case reports that an application appears on the wrong WAN and engineers modify SLA targets without confirming its matching rule. This option would change the control governed by: Loopback-based routing can decouple control-plane identity from one underlay interface. That does not resolve the present failure, where matching and quality-based member choice are separate stages of SD-WAN processing. The applicable response is “Trace the session against SD-WAN service matching and selected member before tuning thresholds; test both primary and backup paths”.