A library consortium DC asks for role-based views so network and server teams see different monitoring dashboards. Which concept does that request apply?
Select an answer to reveal the explanation.
Short Explanation
Network folks need link flaps and BGP peers; server folks need host and app health—same building, different dashboards. Role-based views keep each team effective without drowning them in the other team's noise. One giant root login for everybody is how accidents happen.
Full Explanation
Shared municipal DC operations commonly separate monitoring access and dashboard content by role so network and compute teams each see relevant signals without unnecessary privilege or clutter. That is access and view separation for monitoring, not a mandate to hide all data or to force every user into identical privileged views. Dumping only raw optics data to server teams without role fit also misses the point.