Free SolarWinds Hybrid-Cloud-Observability-Network-Monitoring Practice Exam with Questions & Answers

By default, SolarWinds Network Performance Monitor uses historical data from the last 7 to 30 days to calculate capacity forecasts. This range balances the need for relevant recent data with enough samples to provide trend accuracy.

The documentation states:

“Capacity forecasting in SolarWinds NPM uses the last 7 to 30 days of historical data by default for its projections.”

SolarWinds Hybrid Cloud Observability supports a wide range of flow technologies for IP traffic monitoring. Per the SolarWinds NPM Administrator Guide:

" SolarWinds supports NetFlow, sFlow, J-Flow, and IPFIX for monitoring traffic flows. These protocols are used by devices from different vendors to export flow information. "

J-Flow: Used by Juniper devices and fully supported.

NetFlow (nFlow): The industry standard from Cisco and widely supported.

sFlow: A vendor-neutral flow technology supported by multiple devices.

IPF1X is not a recognized flow protocol in SolarWinds documentation.

SolarWinds provides a MIB Browser utility that lets you search and verify whether a specific object ID (OID) exists in the SolarWinds MIB database. By entering the OID in the MIB Browser, you can confirm its presence and also test polling against the device.

The documentation states:

" Use the MIB Browser to search for and verify OIDs in the SolarWinds MIB database. The tool also allows you to test poll the device to ensure the OID is being returned. "

When collecting Windows event logs without installing an agent, SolarWinds recommends converting those events to SNMP traps or syslog messages using the SolarWinds Event Log Forwarder for Windows. This allows the platform to ingest and recognize Windows events through standard logging protocols.

" The SolarWinds Event Log Forwarder for Windows enables you to forward Windows event logs as SNMP traps or syslog messages, allowing agentless collection and integration into your SolarWinds platform. "

Option C, converting events to traps, is the correct method supported for agentless environments.

Duplicate flow data typically results when both ingress and egress flow monitoring are applied simultaneously on interfaces. If both directions are enabled either globally (all interfaces) or locally (on a single interface), the same flow is counted twice—once entering and once leaving—resulting in duplicate statistics.

The most common cause of mismatch between bandwidth (SNMP) numbers and flow (NetFlow, sFlow, etc.) numbers is that not all network traffic is included in the flow export. SNMP bandwidth counters include all traffic traversing the interface, but NetFlow or other flow records may only represent sampled or filtered subsets, or may miss certain traffic due to export or device configuration limitations. This is a well-documented and expected difference in the SolarWinds platform.

Hiding an IP address group in IPAM management means that group will not appear in dashboards, charts, or reports, but the underlying data and group definition remain intact and are not deleted.

Network Insight in SolarWinds supports in-depth monitoring for certain advanced switch platforms. According to the latest SolarWinds Network Performance Monitor Administrator Guide:

" Network Insight for Cisco Nexus provides advanced visibility into the health, configuration, and performance of Nexus switches. This includes inventory, configuration changes, interface health, VDCs, and more. "

Other switch families such as Brocade, Juniper, and Meraki are not currently supported by Network Insight.

If flows are confirmed as reaching the poller but no data appears in the web console, the most common cause is a missing or incorrect source address field in the flow configuration on the sending device. SolarWinds uses the source address to match incoming flows to the correct device record in its database; if this field is missing or misconfigured, the data will not be processed or displayed.

Exact Extract from Official Guide:

“If the source address field is missing or incorrectly configured in the flow-exporting device, the system cannot associate the flow with a monitored device, and no data will appear in the console.”

— (Network Performance Monitor Administrator Guide, “Troubleshooting NetFlow” section)

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.