Cloud OnRamp for SaaS scores both Salesforce and Webex as better on the local exit. The store needs Salesforce local and Webex kept on the gateway. What keeps Webex on the gateway?
Select an answer to reveal the explanation.
Short Explanation
The measurement wants both applications on the local exit, and you need them split. You pin Webex to the gateway with a data policy and let Salesforce follow OnRamp. Turning OnRamp off does not keep one application local and the other at the gateway.
Full Explanation
Cloud OnRamp for SaaS steers each enabled application by its score. Both scores prefer the local exit, so both would go local. A data policy that matches Webex and sets the gateway path overrides that score for Webex only. Salesforce can keep following OnRamp. Disabling OnRamp removes both scores. It does not preserve a split. A strict voice SLA acts on loss for traffic in a voice list. It is not how you hold one SaaS application on the gateway while another stays local. VPN 512 is management. Putting Webex clients there does not select the gateway. Exam caveat: put the Webex pin in a sequence that is not swallowed by a broader rule sending all SaaS local. Operational check: Salesforce should egress the local internet interface, and Webex should follow the gateway TLOC.