Observability Self-Hosted Network Monitoring

Observability Self-Hosted Network Monitoring practice questions, page 6 of 7, with answer review and explanations.

Question 26

A device studio poller is being built for the node details widget. The plan is to add a field for serial numbers.How would this be accomplished?

  1. Add the object ID (OID) to an existing data source and edit the field name in the widget.
  2. Change one data source field to serial number and supply the OID for the data source.
  3. Default widgets are being used, fields cannot be added to the device studio pollers.
  4. Create a serial number universal device poller (UDP) and link to the node details widget.

Question 27

The web console is showing the status of a network router as “down”, however the node is up and running.Which two of the following causes could be creating the issue? (Choose two.)

  1. agent connection status with the polling engine is “down”
  2. ICMP is blocked between the device and the polling engine
  3. router is configured as a parent in a node dependency
  4. SNMP is blocked between the device and the polling engine

Question 28

Which method is used to add new UPS battery status statistics onto an existing node that does not have the default value polled?

  1. create new custom device poller
  2. custom statistics cannot be added to an existing node
  3. define custom statistic with universal device poller (UnDP)
  4. update SolarWinds’ MIB database

Question 29

If the data collected for hardware health is incorrect, which step could rectify the issue?

  1. Change the MIB tree used for polling.
  2. Change the poller assigned to sensor.
  3. Create a custom poller in device studio for fan speed, power supply, and temperature.
  4. Download the MIB file from the SolarWinds website and add it to the device’s firmware.

Question 30

The status of the interfaces for a network switch shows as “unknown” in SolarWinds’ platform web console, although the node status is “up”.What could be the reason?

  1. hardware sensors are disabled on the node
  2. ICMP is blocked between the node and the polling engine
  3. interface details have changed on the device
  4. interfaces are not managed in hybrid cloud observability (HCO)