Cloud OnRamp for SaaS uses one gateway site. That site's internet exit fails, and every branch loses its SaaS probe. Branch local exits are not allowed. What should be added?
Select an answer to reveal the explanation.
Short Explanation
Every branch was using one gateway's internet door, and that door closed. You add a second gateway site with its own internet exit. Another probe aimed at the dead exit does not bring the score back.
Full Explanation
Cloud OnRamp for SaaS gateways need a working internet exit to probe and to carry the application. This design has one gateway, its exit failed, and branches are not allowed to break out locally, so every probe dies together. Add a second gateway site that has its own internet exit. A second probe on the failed exit has nowhere to go. VPN 512 does not replace an internet exit. A strict SLA does not probe SaaS and does not create a gateway. Exam caveat: the new gateway has to be one the branches are allowed to use. A site that is up and left off the gateway list does not receive the failover. Operational check: with the first gateway's internet shut, OnRamp should still show a probe through the second gateway and the application should move there.