Question 360
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 architectural or operational principle best explains the appropriate correction?
Explanation
Correct Answer
The relevant design principle is: Matching and quality-based member choice are separate stages of SD-WAN processing. In this customer tenant connectivity decision, the control is assessed using observable network or policy state, not the engineer's assumption. The failure is that an application appears on the wrong WAN and engineers modify SLA targets without confirming its matching rule; the intended approach is to trace the session against SD-WAN service matching and selected member before tuning thresholds. The distinguishing confirmation is that The diagnostic record identifies the actual matched rule and path for the session.
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 proposed explanation concerns: FortiGate local-out traffic can have separate selection and routing considerations; do not infer authorization solely from connectivity. The reported symptom instead follows: Matching and quality-based member choice are separate stages of SD-WAN processing; avoid assuming a healthy session proves all services work.
The source case reports that an application appears on the wrong WAN and engineers modify SLA targets without confirming its matching rule. The alternative states a real but different technical principle: SD-WAN rule strategy determines how eligible path metrics affect selection; separate observed path selection from configuration intent. The facts in this question are explained by: Matching and quality-based member choice are separate stages of SD-WAN processing; avoid assuming a healthy session proves all services work.
The source case reports that an application appears on the wrong WAN and engineers modify SLA targets without confirming its matching rule. That principle controls the offered alternative: Policy route decisions can affect forwarding independently of the main static route preference; consider the specific security and routing boundary. It is not the causal distinction established here: Matching and quality-based member choice are separate stages of SD-WAN processing; avoid assuming a healthy session proves all services work.