List Resources: When you add or manage a node, the List Resources page allows you to enable or verify hardware health monitoring options.

Manage Sensors: This section allows you to directly manage the hardware sensors (such as fans, power supplies, and temperature sensors) that report health status.

Device view and node properties are not the primary locations for enabling or managing hardware health sensors.

If the web console shows a router as “down” but it is actually operational:

ICMP is blocked: If the polling engine cannot ping the device, it will be reported as down.

SNMP is blocked: If SNMP polling fails (for devices polled via SNMP), detailed data and status cannot be retrieved, resulting in a down state.

Agent connection issues may apply for agent-based monitoring but are not typical for network routers. Node dependency configuration could affect child node status display but would not cause the parent node to show “down”.

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.

A node rediscovery updates all node and interface information, including names, IP addresses, captions, and interface aliases. Running a rediscovery on the node ensures all related interface details are refreshed in the SolarWinds database and web console.

You can check the status of the flow collector service from the NetFlow collector services section and from NetFlow settings in the SolarWinds web console. These locations provide service health, up/down status, and logs. " Flow and CBQoS sources " and " Top XX receivers " do not display service health.

With Network Insight features (including for Palo Alto and F5 BIG-IP devices) installed alongside Network Configuration Manager and Performance Monitoring, you can monitor:

High availability details: Provides information on device redundancy, failover status, and clustering.

Policy details: Enables insight into firewall, security, and NAT policies for managed devices.

Access lists and VPNs may be monitored in other modules, but the primary, advanced insight is for high availability and policy configurations.

Capacity forecasting accuracy is directly impacted by:

Amount of historical data used: More historical data provides better trend analysis.

Exhaustion calculation method: Different methods (e.g., linear, peak, moving average) affect how forecasts are calculated.

Polling interval: More frequent polling increases granularity and the accuracy of forecasting.

Warning thresholds (D) do not affect the precision of forecasts, only the alerting behavior.

The local NetFlow source provides live (real-time) flow traffic data that is sourced to and from the main polling engine server. This feature is primarily for monitoring the main polling engine’s traffic and quickly identifying top talkers and general flow activity on that server.

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.

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.

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