A bank network team wants a running stream of routing and reachability events rather than a study of one web page. Which assurance view matches that request?
Select an answer to reveal the explanation.
Short Explanation
You want the running incidents, not a single photograph of one lobby. The bank asked for a stream of routing and reachability events, so the matching view is the event-oriented one. The trap is a SaaS-path ranking, a laptop view, or a web-page study, each of which serves a different request.
Full Explanation
The request is explicit: a running stream of routing and reachability events, not a page study. The event-oriented view is the one built to list those events as they occur. A path-and-experience view that ranks which SaaS routes got worse this week answers a comparison of paths over time, which the bank did not ask for. An endpoint view of banker laptops, local gateways, and wireless answers whether a user device or its local network is the fault. A web-performance view of one slow online-banking page answers how that page loads. Those three views are valid for their own questions and do not substitute for an event stream. The bank described a feed, so the useful record is a time-ordered list of routing and reachability changes rather than a weekly path score, a device checkup, or a page timer. Exam caveat: match the view to the noun in the request, here events, and do not drag in path, endpoint, or page detail because those products sit on the same assurance shelf. Operational check: confirm the chosen view lists routing and reachability events over time, and that it is not limited to a SaaS path ranking, a laptop summary, or a single page waterfall.