Pass the SolarWinds Certified Professional SCP-NPM Questions and answers with ExamsMirror

The SNMP trap service is responsible for receiving, decoding, displaying, and storing the SNMP trap messages in the Log Analyzer database. If the service is not running, you will not see the messages in the Orion Web Console. You can verify the status of the service by using the Orion Service Manager or the Windows Services console. You can also restart the service if needed. The other options are not relevant for troubleshooting the cause of missing SNMP trap messages. References:

Monitor SNMP traps

Troubleshoot SNMP traps

Orion Service Manager

 If you want to see a statistic that NPM does not support out of the box, you can use the Manage Pollers feature in Device Studio or the Universal Device Pollers (UnDP) feature to collect the statistics you want from the device. Both features allow you to create custom monitors for almost any statistic provided by SNMP based on its Management Information Base (MIB) and object identifier (OID). You can also assign the custom pollers to specific devices, view the polled data in the Orion Web Console, and use the data in alerts and reports. The difference between the two features is that Manage Pollers is a web-based interface that simplifies the creation and management of custom pollers, while UnDP is a standalone application that offers more advanced options and flexibility. Device templates and application monitor templates are not features that can be usedto collect custom statistics from devices, as they are predefined sets of monitors for specific device types or applications that NPM supports out of the box. References:

Define a custom statistic to monitor in the NPM

Manage pollers using Device Studio

[Monitor custom statistics based on OIDs with Universal Device Pollers]

According to the SolarWinds NPM Administrator Guide, you can use Orion groups to organize your network objects based on any criteria, such as location, device type, department, etc. You can then apply account limitations based on Orion groups to restrict user access to only the network objects that belong to a specific group. For example, you can create two Orion groups, one for Sydney and one for Perth, and assign the devices in each location to the corresponding group. Then, you can use the single group Account limitation to limit the users in Sydney to only view the Sydney group, and the users in Perth to only view the Perth group. References: SolarWinds NPM Administrator Guide, page 163-165; Limit users to specific network areas in the SolarWinds Platform