A national retailer with 90 stores uses SD-WAN Manager to monitor Microsoft 365. Stores have uneven ISP quality and IT wants cloud probing from two hub sites to pick the best egress for SaaS. Local DIA alone lacks visibility. Which Cloud OnRamp for SaaS model should the engineer select to meet centralized probing requirements?
Select an answer to reveal the explanation.
Short Explanation
You've got uneven ISPs, so you want scouts checking the road ahead for you. The gateway-model uses your strong hubs to probe SaaS and direct stores to the winner.
Full Explanation
The gateway model with centralized probing is correct because SD-WAN Manager can designate two hub sites to actively run HTTP and DNS probes against Microsoft 365 gateways, calculate a Quality of Experience score, and then program branch routers to forward SaaS flows to the hub with the best egress path when local DIA quality is uneven and lacks visibility. The direct DIA approach with local branch probing is operationally valid for distributed internet exits and reduces tromboning, but it fails the centralization requirement because isolated branches cannot compare both hub egress paths and provide no consistent vantage point across 90 stores. The gateway visibility-only design with manual selection is also common for phased adoption and monitoring through SD-WAN Analytics, but it fails the steering requirement because it leaves best-egress choice to operators instead of enforcing automated Cloud OnRamp SaaS SLA policy. The IaaS-oriented hub probing design for AWS and Azure is standard for Cloud OnRamp for IaaS with cloud gateways, but it fails the workload fact because IaaS probes measure compute-region reachability rather than Microsoft 365 SaaS front-door performance and will not steer SaaS correctly. As an exam caveat, carefully distinguish Cloud OnRamp for SaaS direct versus gateway models and monitor versus active steering intent, since probing location and traffic action wording decides the answer. For a practical check, verify in SD-WAN Manager that Cloud OnRamp for SaaS is in gateway mode with two hubs assigned, confirm probe status and SaaS SLA scores, then validate branch forwarding and fallback when one hub degrades.