A manufacturer collects BGP session state, interface errors, and throughput toward a plant peer, and wants a page only when that BGP session leaves the established state. Which action matches the request?
Select an answer to reveal the explanation.
Short Explanation
You don't evacuate the plant because a poster lists every gauge. Page on the BGP session state the manufacturer named, and leave the other charts as charts. An endpoint CPU alert, a dashboard with no rule, and a capacity project don't page anyone for that session.
Full Explanation
The manufacturer named one condition for the page: the BGP session toward the plant peer leaving the established state. A network-condition alert on that BGP session state is the rule that matches the request, while interface errors and throughput can remain collected data. An endpoint CPU alert watches a workstation in the plant office and does not watch the peer session. A dashboard that shows BGP state, interface errors, and throughput informs someone who is looking and does not page when no rule is attached. A capacity project for the plant WAN may change the design later and does not page the on-call roster for this session. Showing every signal is not the same job as paging on the one signal they named. Exam caveat: when several network signals are already collected, alert on the condition the question names rather than on a chart of all of them. Operational check: review a past transition of that BGP session out of the established state, confirm the rule paged, and confirm a CPU alert did not page for that event.