A branch uses Cloud OnRamp for SaaS for Microsoft 365 with dual Internet transports and a gateway site offering a cleaner path. Probes show the local Internet path degrading while the gateway path stays excellent. Which Cloud OnRamp for SaaS behavior selects the best exit for the application?
Select an answer to reveal the explanation.
Short Explanation
You have two routes to Microsoft 365, so you want the one delivering the better experience. Continuous probing compares their performance and shifts your traffic to the gateway when the local Internet path degrades.
Full Explanation
Cloud OnRamp for SaaS is the right choice because it continuously probes Microsoft 365 from branch Internet transports and candidate gateway sites, compares actual SaaS performance, and directs the flow through the best-performing exit. With the local Internet path degrading and the gateway path staying excellent, probe-based selection lets the gateway take over dynamically. An application-aware routing policy that selects the highest-quality local DIA link compares local Internet links but does not include the remote gateway exit, so it cannot choose the better path in this scenario. Assigning Microsoft 365 to a manually configured preferred gateway provides static breakout, not probe-driven selection; it cannot adapt if measurements later favor another exit. BFD loss and latency monitoring evaluates SD-WAN transport tunnel health rather than application-specific cloud performance, so a tunnel may look healthy while Microsoft 365 performs poorly. For exams, distinguish transport or overlay path selection from SaaS-aware exit selection: Cloud OnRamp for SaaS uses cloud-application probes to compare DIA and gateway paths. As a practical check, review Cloud OnRamp monitoring in SD-WAN Manager for probe scores by exit, the selected gateway, and the installed NAT path before changing policy or transport configuration.