Traders at a bank lose the market application when the VPN client on the endpoint disconnects, and endpoint data records that disconnect. Which alert matches the symptom?
Select an answer to reveal the explanation.
Short Explanation
When the headset unplugs, you alarm the headset rather than the city power grid. You alert on the endpoint VPN client, because the market application dies when that client disconnects. A BGP-state alert, a core-router SNMP alarm, and a weekly executive mail aren't watching the trader's VPN client.
Full Explanation
The market application fails when the VPN client on the endpoint disconnects, and endpoint data records that disconnect, so the matching alert is an endpoint VPN alert. The object that moved is the VPN client on the trader laptop, which is an end-user experience signal. A BGP-state alert on the bank edge watches a BGP session and does not watch that VPN client. An SNMP interface alarm on a core router does not see the client disconnect on the laptop. A weekly executive mail about trading uptime does not watch the VPN client at the moment it drops. Edge BGP, a core interface, and a weekly summary can all stay quiet while the endpoint VPN client is what disconnected. Exam caveat: the VPN client on the endpoint is not the same object as a BGP session on the edge, so a BGP-state alert does not cover this disconnect. Operational check: match market-application failures to VPN client disconnects on the endpoint and confirm the alert fired on that client event while the core interface alarm stayed quiet.