Which statements describe how thresholds can be defined in NPM?

Which statements describe how thresholds can be defined in NPM?

• A. Thresholds are defined by CPU only
• B. Thresholds can be static or dynamic with baselines, and use evaluation windows
• C. Thresholds are always static and cannot use baselines
• D. Thresholds are defined per device but cannot be evaluated

Answer: (C)

Thresholds in NPM can be static or dynamic, using baselines and evaluation windows to make the monitoring intelligent. A dynamic threshold compares the current value to a baseline that’s derived from historical data, and the evaluation window determines over what period that baseline is calculated and how the current measurement is judged. This allows thresholds to adapt to the normal behavior of different devices and time periods, reducing false alerts while still catching real issues. Thresholds aren’t limited to CPU; they can be defined for various metrics such as memory, disk I/O, or interface utilization, and you can apply them per device, per metric, or per interface as needed. The system continuously evaluates incoming data against these thresholds to decide when to raise alerts. Choices that restrict thresholds to CPU, insist they’re always static without baselines, or claim they can’t be evaluated don’t fit how NPM thresholds are designed to work.

Thresholds in NPM can be static or dynamic, using baselines and evaluation windows to make the monitoring intelligent. A dynamic threshold compares the current value to a baseline that’s derived from historical data, and the evaluation window determines over what period that baseline is calculated and how the current measurement is judged. This allows thresholds to adapt to the normal behavior of different devices and time periods, reducing false alerts while still catching real issues. Thresholds aren’t limited to CPU; they can be defined for various metrics such as memory, disk I/O, or interface utilization, and you can apply them per device, per metric, or per interface as needed. The system continuously evaluates incoming data against these thresholds to decide when to raise alerts.

Choices that restrict thresholds to CPU, insist they’re always static without baselines, or claim they can’t be evaluated don’t fit how NPM thresholds are designed to work.