The operations center at a logistics hub disagrees about which SaaS path degraded this morning. Which capability settles that disagreement?
Select an answer to reveal the explanation.
Short Explanation
The argument at the dock is which road into town slowed down this morning. You settle it with WAN Insights for the SaaS paths the hub actually used. A configuration archive, one access-switch poll, or a page load that does not record the path cannot name that road.
Full Explanation
The operations center disagrees about which SaaS path degraded this morning, and WAN Insights is the view of path and experience toward those SaaS and WAN destinations. Settling the disagreement requires the paths that were in use, not a backup or a single local counter. A device-configuration archive from the previous week's backup shows how devices were saved then and does not show this morning's path experience. An SNMP poll of a single access switch at the hub stays on one local device and cannot rank SaaS paths against each other. A web transaction that does not record the WAN path can show that a page was slow and still leave the team arguing about which path degraded. The exam trap is using a page timer or a switch poll as if it identified the SaaS path. In production, use WAN Insights to list the SaaS paths from the hub across this morning and mark the destination whose experience dropped. A saved configuration can explain a later change-control question, but it does not name the path that degraded today.