From which two of the following locations can CPU load be excluded from contributing to overall node status? (Choose two.)
AnswerB, D
ExplanationBy default, the 'overall status' of a node (Up, Warning, Critical) is calculated based on its availability and the health of its child components, such as CPU and Memory. According to the SolarWinds Platform Node Management documentation, administrators can fine-tune this rollup behavior to prevent non-critical metrics from turning a node 'red' on the dashboard.
Edit Node Properties (B): Inside the 'Edit Node' page, there is a section for 'Thresholds.' Here, an administrator can uncheck the box that allows CPU load to contribute to the node's overall status. This is useful for servers that consistently run high CPU but are otherwise healthy.
Node Child Status (D): Within the global SolarWinds settings, administrators can manage 'Node Child Status Participation.' This centralized menu allows you to define which sub-elements (CPU, Memory, Interfaces, etc.) are allowed to influence the parent node's status.
Muting a node (Option C) only pauses alerts and does not change how status is calculated. The All Nodes widget (Option A) is a visualization tool and does not provide the configuration settings to change the underlying status logic.