Cloud OnRamp for SaaS should probe a local exit for staff SaaS in one service VPN. The only internet exit is attached to the guest VPN. Staff probes never start. What is missing for the staff VPN?
Select an answer to reveal the explanation.
Short Explanation
The only internet door is on the guest side of the building. You give the staff VPN a local exit it is allowed to use, so OnRamp can probe staff SaaS. Shutting the guest VPN does not hand that exit to the staff.
Full Explanation
Cloud OnRamp for SaaS probes a local exit only from the VPN that can use it. Staff SaaS is in a different service VPN from the guest exit, so no staff probe starts. Add a local internet exit for the staff VPN, with NAT if the exit needs it. A second guest exit stays with the guests. OnRamp does not automatically share it with every service VPN. Shutting the guest VPN removes the guest exit. It does not move it. A voice SLA does not create a probe for a VPN that has no exit. Exam caveat: the exit has to be a real DIA path. An interface in the staff VPN that cannot reach the application still produces no useful probe. Operational check: a staff probe should appear on the new exit, and guest traffic should still use the guest exit.