Free Practice Questions for SolarWinds Hybrid-Cloud-Observability-Network-Monitoring Exam

The Universal Device Poller (UDP) in SolarWinds NPM allows users to monitor any SNMP-exposed value, including interface traffic, UPS battery status, and CPU temperature, provided the device ' s MIB exposes the relevant OIDs. Users configure the UDP to poll these custom OIDs, making it a flexible option for monitoring a wide range of metrics across diverse devices.

To properly collect and display NetFlow data in SolarWinds NTA, the following requirements must be met:

C. Each device that exports NetFlow data to SolarWinds’ NTA must be monitored in NPM.

NTA (NetFlow Traffic Analyzer) relies on devices being monitored by NPM (Network Performance Monitor) to collect and correlate flow data.

D. The interface through which a device exports NetFlow data must be monitored in NPM.

Only interfaces that are managed in NPM can be used for NetFlow data collection, visualization, and reporting.

Devices do not need to be monitored in NCM (Network Configuration Manager) for NetFlow, and exporting NetFlow is not optional if you want the device’s flows displayed in NTA.

For organizations with very large environments and strict requirements for data freshness and availability, SolarWinds documentation prescribes several specific steps:

A. Deploy multiple additional polling engines (APEs) in each regional datacenter and configure load balancing. " For environments exceeding 20,000 monitored interfaces, deploy multiple Additional Polling Engines (APEs) to distribute load and maintain polling intervals. Place APEs close to monitored devices to reduce latency. "

B. Implement SolarWinds High Availability (HA) pools for both the main and polling engine servers, with active-passive failover. " SolarWinds HA pools provide automatic failover for platform and polling engines, ensuring service continuity in case of hardware or network failures. "

C. Configure the SolarWinds database server in a Microsoft SQL Server Always On Availability Group. " To protect against database outages, deploy the SolarWinds database in a SQL Server Always On Availability Group or Failover Cluster Instance (FCI). "

Option D is incorrect; overlapping node groups are not a requirement and, in fact, the documentation suggests using dynamic assignment to balance load, not strictly static node groups.

When you observe an " unknown traffic event " in the SolarWinds web console, it usually means the collector is receiving NetFlow or other flow data from a device that is not currently managed or monitored in the SolarWinds database. The collector can receive flows from any device, but if the device is not added or properly monitored, the traffic will show up as " unknown " because SolarWinds cannot associate the flows with a known interface or device.

This message means the NetFlow collector is receiving flow data from a device whose IP address is not managed in the SolarWinds platform, so the flow data is discarded. To resolve this, you must either:

Add the sending device as a managed node using the correct IP address, or

Enable the " Allow matching nodes by another IP " option in the NetFlow settings, which allows SolarWinds to match flows sent from an interface IP or secondary IP.

Universal Device Pollers (UDPs) in SolarWinds are tightly coupled with the polling engine on which they are configured. If the main polling engine fails, custom pollers do not automatically failover; as a result, statistics collection for those UDPs is interrupted. According to SolarWinds documentation:

" UDPs are assigned to a specific polling engine. If the polling engine fails, UDP statistics are not collected until the engine is restored. "

" Universal Device Pollers are not supported on failover engines; they do not collect data from hot standby or failover engines. "

Thus, options C and D directly reflect the official guidance.

If interfaces on a node show an “unknown” status, the recommended solution is to delete and rediscover the node. This ensures all current interface information, OIDs, and properties are correctly detected and polled, resolving mismatch or missing data that can cause an “unknown” status.

A node rediscovery updates all node and interface information, including names, IP addresses, captions, and interface aliases. Running a rediscovery on the node ensures all related interface details are refreshed in the SolarWinds database and web console.

To monitor an application on a server with SolarWinds, you must first find the application in the list of available (supported or discovered) applications and enable monitoring for it. The platform also provides a “monitor recommended applications” button to automatically suggest and enable monitoring for best-practice applications on a given server.

From the documentation:

“To monitor an application, select it from the list of available applications and enable it for the target server. The ‘Monitor Recommended Applications’ option helps you quickly enable commonly used application monitors.”

Grouping IP addresses or configuring specific source/destination pairs is not required for standard application monitoring.

If a node remains in “unknown” status:

A. Ping device from assigned polling engine: Verifies direct network connectivity from the poller to the node.

C. Verify the appropriate polling method is set for this node: Ensures SolarWinds uses the correct protocol (ICMP, SNMP, WMI, etc.) for monitoring.

D. Verify a ping response for this node is received through the ICMP: Confirms basic reachability and that the node is not blocking ping requests.

Running an SNMP walk (B) can help diagnose SNMP-specific issues but is not always directly relevant to a node simply being in “unknown” status unless SNMP is the configured polling method.