SolarWinds Hybrid-Cloud-Observability-Network-Monitoring - Hybrid Cloud Observability Network Monitoring Exam

The SolarWinds MIB database is used for SNMP-based monitoring and performs these critical functions:

A. It defines which OIDs are recognized and what metrics can be polled via Universal Device Pollers or other custom monitors.

C. It maps OIDs (numeric identifiers) to their human-readable textual names for reporting and alerting.

Options B and D are not accurate; the database does not enable automatic polling nor does it update device OIDs during polling.

SolarWinds NTA maps flow sources to nodes by matching the IP address. If a device exports flows using a secondary IP (not the one defined as " primary " in SolarWinds), and the setting " Allow matching by other IPs " is not enabled, the flow will not map to a known node. The documentation explains:

" If flow packets are received from an IP address not designated as primary in SolarWinds, and matching by other IPs is disabled, the flow source is not linked to a node. Enable the setting to match by any device IP to resolve this issue. "

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.

If default SNMP polling is not returning data for a new device but works for others, it is likely that the device uses unique or vendor-specific MIBs not present in the SolarWinds MIB database. Updating the MIB database and building custom pollers (UDPs) for those MIBs allows you to collect the desired metrics. An SNMP walk may help you identify the OIDs, but building and assigning pollers is necessary for ongoing monitoring.

A. When you probe less frequently, updates are slower but generally more accurate since there ' s less overhead and less chance of missing network changes due to polling overlaps.

C. Probing more frequently results in faster updates but may slightly decrease accuracy due to increased network noise and overlapping probes.

The documentation states:

" A higher probing frequency provides faster updates in NetPath views but can reduce accuracy due to more frequent sampling. Lower frequency means slower updates but typically results in higher accuracy and less system load. "

Device Studio pollers are used to build custom pollers for advanced device-specific metrics and widgets. The technologies explicitly supported for Device Studio pollers include:

Machine type for node details widget: Device Studio can create custom pollers to display specific node details, such as machine type, chassis ID, or serial number, within a node details widget.

Power supply status for vital statistics view: Device Studio also allows polling and visualizing metrics such as power supply status, fan status, and other vital statistics that are not natively included in basic SNMP polling.

While Device Studio can poll for advanced or composite data such as VLAN, VRF, and device health, certain interface statistics or single CPU/memory metrics are typically managed by standard SNMP pollers or Universal Device Pollers rather than Device Studio.

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.

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.

According to the latest SolarWinds Administrator Guides, integrating Cisco ACI for true Hybrid Cloud Observability involves several coordinated steps:

B. Configure API polling credentials for the APIC cluster under “Settings > All Settings > Manage ACI” in SolarWinds. SolarWinds Hybrid Cloud Observability leverages API-based polling (not only SNMP) to retrieve comprehensive fabric topology, health scores, faults, and logical object inventory (tenants, application profiles, EPGs, etc.). Configuration of API credentials is required to access these features. " For deep ACI monitoring, use API credentials under ' Manage ACI ' . SNMP alone is insufficient for advanced monitoring, object mapping, or health correlation. "

C. Enable NetFlow export from all ACI leaf switches to the SolarWinds collector and import flow definitions in the Platform. NetFlow is essential for capturing east-west and north-south traffic inside the fabric, and SolarWinds uses this flow data for bandwidth analysis and path visualization. " SolarWinds recommends enabling NetFlow export on all leafs and importing flow records to gain traffic visibility inside Cisco ACI environments. "

D. Map tenants, application profiles, and endpoint groups (EPGs) to custom properties for advanced alerting and reporting. Custom properties in SolarWinds allow mapping logical ACI constructs to alert rules, reports, and dashboards for business-centric monitoring. " Map EPGs and application profiles to custom properties for granular alerting and business-aligned dashboards. "

Option A is incorrect because the official guide states that API polling (not just SNMP v3 with plugins) is required for automatic APIC object discovery.

Only SNMP version 3 supports advanced authentication methods such as MD5, SHA1, SHA256, and SHA512 in SolarWinds and other SNMP-compliant platforms.

The documentation specifies:

" SNMP v3 provides secure authentication and encryption options, including MD5, SHA1, SHA256, and SHA512. Versions 1 and 2c only support community string authentication. "