A manufacturer is turning up a new WAN circuit and wants to compare the SaaS path and experience before and after the cut. Which capability supports that comparison?
Select an answer to reveal the explanation.
Short Explanation
You compare the old morning drive and the new road with the same commute, not with a photo of the garage. WAN Insights is how you compare SaaS path and experience across a circuit cut. A backup from the night before, one core-switch poll, or a page load that ignores the path cannot make that comparison.
Full Explanation
A new WAN circuit should be judged by SaaS path and experience before and after the cut, and WAN Insights is the capability aimed at that path and experience. The comparison needs the same destinations observed on the path, not a snapshot of how devices were configured the night before. A device-configuration archive records how devices were set and does not measure experience on either circuit. An SNMP poll of one core switch during the change shows local device counters and does not compare provider paths toward SaaS. A web-only transaction that ignores the WAN path can time a page twice and still not show whether the new circuit changed the path. The exam trap is declaring the cut a success from a saved configuration or a single switch poll. In production, compare WAN Insights for the same SaaS destinations on the old circuit and on the new circuit, and keep the destination set constant. A page timer that ignores the path can stay as a separate check, but it does not identify which circuit carried the session.