Free SolarWinds Hybrid-Cloud-Observability-Network-Monitoring Practice Exam with Questions & Answers | Set: 2

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.

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

The MIB browser tool in the SolarWinds web console is designed to browse, query, and verify OIDs on monitored nodes. It allows you to test if an OID returns valid data for a specific device before assigning it in a custom poller. This ensures compatibility and accuracy of your custom monitoring setup.

The correct process for creating a poller in Device Studio is:

Select the technology

Specify the data source

Assign the poller to a node

Save the poller

UDP port 2055 is the default port for NetFlow data (flow analysis), while SNMP (port 161) is required for CBQoS monitoring. SolarWinds NTA receives flow traffic on UDP 2055, and SNMP is used for polling CBQoS statistics from devices.

Show best is the status rollup mode designed for groups of redundant or backup devices. It displays the " best " (most available/least severe) status within the group, which is most useful when any one device in the group being up means the group is healthy.

According to the SolarWinds Log Analyzer Administrator Guide (Version 2024.1) , Log Analyzer provides several built-in or native log entry actions as part of its log-processing rules. The key native log entry actions include:

Add a tag to the log entry : This action allows you to tag event logs for easier searching and filtering later.

Continue rule processing but do not save : With this action, the log entry is not saved but rule processing continues.

Halt further rule processing for the log entry : Selecting this action will immediately stop the processing of any more rules for the current log entry.

Sending an email notification is an alert action and not considered a native log entry action in the context of log processing rules.

Exact Extract from Official Guide:

" Key features in LA

Apply tags to event logs

Drop unwanted event logs in LA

Filter and analyze event logs

Filter and view event logs in live mode

Filter entry details in LA

Filter on log tags... " — (Log Analyzer Administrator Guide, Page 53-54)

Additionally, the guide specifies under Create custom log-processing rules in LA that actions such as tagging, halting processing, and not saving are among the native processing actions.

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)

When displaying Universal Device Poller (UDP) data in different web console views, each view must be configured to show the UDP results as charts.

From the documentation:

“In the Universal Device Poller application, under the Web Display tab, you must check the ‘chart’ box for every web view where you want to display the poller data. If the box is not checked for the current view, the data will not be visible as a chart widget.”

When monitoring F5 BIG-IP load balancers, SolarWinds Network Insight requires both SNMP for device status and iControl (a proprietary F5 API) for advanced configuration and health monitoring. The SolarWinds guide states:

" After adding an F5 load balancer with SNMP, configure the iControl connection to access additional F5-specific health and configuration metrics. "

Enabling DNS resolution but not storing hostnames immediately results in:

Reduced database memory/storage used for DNS info, as hostnames aren’t stored with each flow record.

Less database space used for flows, since flow records will reference IPs rather than resolved DNS names.

Reduced SQL server reads/writes since the platform does not immediately resolve and store hostnames with every received flow, decreasing load.

DNS names will still appear in reports where resolved dynamically, so option C is incorrect.