A hospital campus wants the path and user experience to a SaaS payroll site across the WAN explained for leadership. Which view matches that question?
Select an answer to reveal the explanation.
Short Explanation
WAN Insights is the trip report for how you reach a cloud application, not a folder of saved router configs. You use it when the question is the SaaS payroll path and the experience across the WAN. Polling one access switch, or timing a page without looking at the path, does not brief leadership on that WAN experience.
Full Explanation
The leadership question is the path and experience to a SaaS payroll site that crosses the WAN. ThousandEyes WAN Insights is the view meant for path and experience toward SaaS and WAN destinations, so it matches the complaint directly. A device-configuration archive of the WAN routers stores how those routers are set, and a saved configuration is not the experience of reaching the payroll site. An SNMP poll of one access switch reports that switch, which is not the WAN path from the campus to the SaaS provider. A web-only transaction can load the payroll page and still skip the WAN path, so it cannot explain the path leadership asked about. Leadership asked how the campus reaches the payroll site across the WAN, and a page timer that stays on the transaction cannot stand in for that path. Exam caveat: WAN Insights is not a configuration backup and not a single-device poll; using it as either of those misses the SaaS and WAN question. Operational check: open the payroll SaaS destination in WAN Insights and confirm the view shows the WAN path and experience rather than a router archive or a single switch poll.