SolarWinds SCP Network Performance Monitor (NPM) SCP-NPM Exam Practice Test

Answer : C

By default, NPM uses the global critical CPU threshold for node statuses, which is 90%. However, you can override this threshold for individual nodes by editing their properties and specifying a custom value for the critical CPU threshold. This way, you can adjust the threshold according to the specific characteristics and performance of each node. Changing the critical CPU threshold on the node will affect how the node status is calculated and displayed in the web console, as well as how the alerts are triggered based on the CPU utilization.Reference:Thresholds in the SolarWinds Platform;CPU Critical Threshold - Forum - Network Performance Monitor (NPM) - THWACK

Answer : D

The Discovery Ignore List is a feature that allows you to specify the IP addresses or hostnames of the devices that you do not want to monitor or discover in the future. You can add devices to the ignore list manually or automatically during the discovery process. Once a device is added to the ignore list, it will be skipped by any subsequent discovery. You can also remove devices from the ignore list if you change your mind and want to monitor them later.Reference:Add devices to the Discovery Ignore List in NPM,Remove devices from the Discovery Ignore List in NPM,How to View Devices on Your Windows Network and What to Do If You Can't See Them

Answer : D

Account limitations are a way of restricting the access of Orion user accounts to specific network objects, such as nodes, interfaces, groups, maps, or alerts. You can use account limitations to prevent a user from seeing or working with select monitored entities through the SolarWinds server. For example, you can limit a user to see only the nodes in a certain group, or only the maps that they have created. You can apply account limitations to individual users or user groups, and you can choose from predefined limitations or create custom limitations based on custom properties. The other options are not effective ways of limiting user access to monitored entities, as they either affect the monitoring status of the entities (unmanage), the permissions of the entities themselves (configure permissions), or the alerting scope of the entities (configure alert limitations).Reference:

Limit user access to network areas with account limitations

Predefined Orion Platform account limitations

Create custom account limitations

Answer : A

The best way to reduce false alerts for high traffic utilization is to configure the alert trigger condition to be more specific and accurate. By setting the alert to trigger only when traffic utilization remains high for a sustained period, you can avoid getting alerted for short-lived spikes that are not a cause for concern. You can use theTime of DayandTrigger Conditionoptions in the alert configuration wizard to define the duration and threshold of the high traffic utilization condition. For example, you can set the alert to trigger only when traffic utilization is greater than 80% for more than 10 minutes during business hours.Reference:

How do I create a high transmit percent utilization alert to monitor interface bandwidth - Forum - Network Performance Monitor (NPM) - THWACK Products

How alerts work - SolarWinds

SCP Study Aid - SolarWinds(page 8)

Answer : C

When you create or edit an alert, you can test the trigger and reset actions by clicking Simulate next to the action you want to test. This will execute the action regardless of the trigger condition. You can also select an object to resolve any variables you have used in your action. For example, if your action is to send an email with the node name and status, you can select a node to see how the email will look like. This way, you can ensure the trigger actions you set on an alert will work as expected.Reference:Test alert triggers and actions in the SolarWinds Platform,How to Create Intelligent Alerts with NPM,How alerts work.

Answer : A

Device Studio Poller is a feature that allows users to create custom pollers for devices or technologies that are not supported by default in NPM. It can poll multiple OIDs for a given technology, perform logical operations or transformations on the polled data, and display the polled values in existing resources.However, it does not collect data from Orion Failover Engine or Hot Standby Engines, which are features of Orion High Availability that ensure continuous monitoring in case of primary server failure12.Reference:1: Create pollers in Device Studio for NPM3,2: When Good OIDs Go Bad: Customizing Device Pollers,3: Manage Pollers (AKA Device Studio) question

https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-monitoring-mibs-with-universal-device-pollers-sw548.htm

Answer : B

For any node you monitor, you cannot use Network Discovery to automatically add child volumes or interfaces for monitoring. Network Discovery is a tool that helps you identify and add new devices to your network, but it does not automatically monitor all the components of the discovered devices. You need to manually select the volumes or interfaces you want to monitor from the list of resources on each node. You can also use the Network Sonar Results Wizard to filter and add the resources you want to monitor after running a discovery job.Reference:

Discover your network with NPM - SolarWinds(see the Monitoring Settings panel section)

Network Discovery Tool - Automated Discovery Software | SolarWinds(see the Monitor Devices section)