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

When configuring database log collection (e.g., from SQL Server), SolarWinds supports:

Mixed mode authentication (SQL Server and Windows authentication)

Windows authentication

Kerberos and oAUTH are not supported directly as authentication methods for log collection from SQL Server databases in the SolarWinds platform.

When the SNMP community string is changed on a device, SolarWinds recommends:

Edit the node properties and save the changes.

Update the community string in node properties to match the new value on the device.

" To restore polling, edit the node in SolarWinds, update the SNMP community string in the properties, and save the changes. This ensures that SolarWinds can authenticate and resume polling. Deleting and re-adding the node is not necessary, nor is restarting the SNMP service on the device in most cases. "

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. "

Log Analyzer listens for syslog messages by default on:

TCP port 514 (the standard syslog port)

TCP port 6514 (the default port for syslog over TLS/SSL, i.e., secure syslog)

Port 162 is for SNMP traps, and 1463 is not standard for syslog in SolarWinds.

Device Studio pollers can use manually defined OIDs when the required OID is not present in the SolarWinds MIB database. SolarWinds documentation specifically describes the option to select Manually Define Object Identifier (OID) , type the OID name and value, select the SNMP get type, and poll the current value from the test node. That makes option A correct. Option B is wrong because if the target device itself does not support or return the OID, SolarWinds cannot poll that value. Option C is wrong because Device Studio can poll multiple OIDs for a given technology. Option D is too broad; SolarWinds says Device Studio values are displayed in existing resources, not that every result becomes a separate widget.

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

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.

Ping the device from the polling engine: Verifies network connectivity and correct polling engine assignment.

Verify hardware health sensors: Ensures the platform is receiving valid sensor data; missing data may indicate sensor or device communication issues.

Adding a remote site node and waiting are not direct troubleshooting steps for missing data on a node that is already “up.”

Exact Extract from Official Guide:

“If a node is up but data is missing, check network connectivity from the polling engine using ping or SNMP walk tools, and verify that hardware health sensors are reporting valid data.”

— (Network Performance Monitor Administrator Guide, “Troubleshooting Nodes and Data Collection” section)

The flow navigator in SolarWinds NetFlow Traffic Analyzer allows users to filter and analyze flow data. For future access, you can save your custom view to the menu bar from the flow navigator, providing one-click access to your saved configurations.

The documentation states:

“To save a custom NetFlow analysis for future use, configure your view in the flow navigator, then select the option to save the view to the menu bar for easy retrieval.”

SolarWinds documentation is direct on this point: a red/down interface generally indicates that there is no connection. The first checks should be physical and dependency-based, not custom polling or hardware sensor configuration. The parent node must be reviewed because an interface can appear down or unreachable if the parent device itself is not operating correctly. The cable must also be checked because physical layer failure is a common cause of a down interface. Hardware health sensors are for device component health such as fans, power supplies, or temperature, not primary interface link-state troubleshooting. Device Studio is also irrelevant because the built-in interface status poller already handles interface state.

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

Incorrect hardware health data often results from polling the wrong MIB tree. By changing to the correct or preferred MIB tree for the device model, SolarWinds can accurately interpret and display hardware health metrics.