Hotel security asks for event evidence that a prefix was hijacked, and they do not want a page-load script. Which assurance view matches the request?
Select an answer to reveal the explanation.
Short Explanation
When security asks for the alarm log of a break-in, you do not hand them a photo of how fast the lobby doors open. Hotel security wants event evidence of a hijack, so the event and routing view is the match, not a page-load script. The trap is a web waterfall, a guest-device view, or a SaaS-path ranking aimed at a different question.
Full Explanation
Security asked for event evidence that a prefix was hijacked, and they said they do not want a page-load script. The event and routing view is where origin changes and related routing events are visible. A page-load script that records how the booking page loads, object by object, for the web team answers a web-performance question and is the artifact they declined. An endpoint view of the guest device, its gateway, proxy, and wireless answers whether a user device or its local path is unhealthy, which does not show who originated the prefix. A path-and-experience view of which SaaS routes worsened for the hotels this week compares path quality over the week and is not the hijack evidence request. Exam caveat: a hijack question is an event and routing question even if the booking page also feels slow while the prefix is wrong. Operational check: confirm the view given to security shows the prefix event and the unexpected origin, and that it is not a page-load script, a guest-device summary, or a weekly SaaS path ranking.