Hybrid-Cloud-Observability-Network-Monitoring Practice Questions

A.  

C.  

The documentation states:

" Unclassified traffic may result when known applications use non-default ports or when flow records lack required port information for mapping. "

To effectively diagnose a slow connection using NetPath, the following data points are essential:

Date, time, and duration of the performance issue: Helps correlate the problem with specific events or maintenance windows.

IP addresses of the nodes in question: Identifies the exact points in the network path where issues may arise.

Latency and packet loss information: These are core metrics provided by NetPath and are critical for pinpointing where delays and data loss occur.

The SolarWinds documentation states:

" When troubleshooting with NetPath, consider the time frame, the specific nodes (by IP address), and the latency/packet loss details between hops. Alert descriptions are not a primary diagnostic data point in NetPath ' s workflow. "

SolarWinds Hybrid Cloud Observability (HCO) supports capturing flow data and CBQoS data using:

A.  

C.  

J-Flow is primarily for flow data (from Juniper devices), and SNMP is not a flow export protocol.

The documentation states:

" NetFlow (including NetFlow v9) and IPFIX are supported for flow and CBQoS data collection. These standards provide extensive network traffic and QoS visibility within HCO. "

NetPath is specifically designed to trace and troubleshoot connectivity paths between nodes.

Network Insight provides in-depth analysis and diagnostics for specific vendors/devices, including health, connectivity, and configuration.

Asset inventory and MIB browser are not direct troubleshooting tools for connectivity.

SolarWinds identifies and classifies flow traffic based on application and port mapping in the platform.

" Unclassified traffic in flow charts often occurs when an application is not mapped in the system, or when the application uses a port that is not defined in the SolarWinds Hybrid Cloud Observability (HCO) application mapping database. Flows from unsupported devices or flow direction do not cause unclassified application traffic—rather, they will not be collected or will be marked as unknown flows. "

Thus, unclassified traffic can result from new or custom applications or changes in port usage that are not reflected in the configuration.

Unreadable fields in SNMP traps from a device typically indicate either the device is not monitored as a node (so SolarWinds cannot fully parse its SNMP data) or the MIB file for that device is not included in the SolarWinds MIB database, making it impossible to decode certain OIDs.

This question is defective as written. It says “Choose three,” but SolarWinds capacity forecasting documentation supports all four listed capacity problem areas. SolarWinds states that node capacity includes both CPU load and percent memory usage , volume capacity includes volume usage and exhaustion forecasting, and interface capacity forecasting includes receive/transmit interface utilization thresholds. Therefore, CPU load, interface utilization, memory use, and percent disk usage are all valid capacity forecasting/capacity problem categories. A forced three-answer key would be unreliable and should be corrected, not blindly accepted. The clean correction is to change the item from “Choose three” to “Choose four,” or remove one valid option.

===============

Hardware health monitoring can be enabled during node discovery or after a node is added via the " List Resources " option. Additionally, hardware health can be enabled or viewed in the Asset Inventory page for nodes that support it.

From the documentation:

“You can enable hardware health sensors by selecting the option during resource discovery (List Resources) or later via Asset Inventory for individual nodes.”