CPU utilization is being monitored on a critical Windows server and is set to notify when utilization exceeds 90%. Notification parameters are set to disregard those brief spikes over 90% and focus on sustained periods above 90%. What should be configured to accomplish the notification goal?
Answer : C
To prevent 'alert noise' caused by temporary performance spikes, the SolarWinds Platform allows for threshold persistence. According to the SolarWinds Platform Administrator Guide, simply setting a threshold at 90% would trigger an alert the moment a single poll returns a high value.
The correct configuration to ensure only sustained high utilization triggers an action is to set the node to change CPU status if the threshold is met for multiple polling cycles. This is found in the 'Edit Node' properties under the Thresholds section. For example, if the polling interval is 2 minutes and you set the condition to '10 minutes' (or 5 consecutive polls), the CPU status will only transition to Warning or Critical after the utilization has stayed above 90% for that entire duration. This filtering happens at the node/status level, ensuring that the alert engine only fires when there is a legitimate, sustained performance bottleneck rather than a transient spike caused by a routine background process.
A network discovery job was performed. The job was not correctly defined and not all devices were discovered within the network. What is the likely reason for the skipped devices?
Answer : B
Network Discovery is an automated process to scan subnets and import new infrastructure. However, the discovery engine includes logic to prevent duplicate entries and ignore non-relevant assets. According to the SolarWinds Platform Administrator Guide, if specific devices are missing from the results, the most common administrative cause is the Discovery Ignore List.
The 'Ignore List' is a database of IP addresses or MAC addresses that the platform has been explicitly told to skip. This often happens if a device was previously discovered but the administrator chose 'Ignore this node' during the import phase. The system remembers this choice to prevent the device from reappearing in every subsequent scan. Additionally, the platform automatically ignores any node that is already present in the 'Manage Nodes' list to avoid creating redundant monitoring objects.
While a timeout (Option C) or incorrect polling method (Option D) could cause a node to fail to respond with its full metadata, the device would typically still appear in the discovery results as a 'Generic' or 'ICMP-only' device rather than being skipped entirely. Only the Ignore List or pre-existing status causes a device to be excluded from the discovery results table during a scan of a valid subnet.
A non-administrator user reports they are unable to create Intelligent Maps in the web console. What is the reason for the block?
Answer : D
The ability to create and manage Intelligent Maps in the SolarWinds Platform is tied to a specific set of granular user permissions. While a user may have general rights to view the console, creating a map involves placing entities onto a canvas and, frequently, utilizing background images or custom icons. According to the SolarWinds Platform documentation on Map Management, a critical prerequisite for full map creation functionality is the permission to add images (D).
In the user account settings under Settings > All Settings > Manage Accounts, there is a specific toggle for 'Allow Map Management' or 'Allow Editing.' However, if the underlying platform permission for 'Add Images' is not enabled, the user will find the map creation wizard restricted or non-functional. This is because Intelligent Maps rely on the platform's shared image library to store the metadata and visual components of the map. Without the right to write to this library (Add Images), the user is blocked from saving new map definitions to the database. This permission is often disabled by default for standard users to prevent the web server's storage from being filled with unauthorized or non-work-related image files.
An agent software has been deployed to the Windows domain controller, however the server is being polled through WMI. What is causing this irregularity?
Answer : D
In the SolarWinds Platform, the method used to poll a node (SNMP, WMI, or Agent) is a specific property assigned to the node record in the database. According to the SolarWinds Platform Agent Management guide, simply installing the agent software on a remote server does not automatically convert the existing node record to use that agent for data collection.
If a node was originally added to the system via WMI, the platform will continue to attempt to poll it via WMI over the network using RPC/DCOM, even if the SolarWinds Agent is successfully installed and running on the target machine. To fix this 'irregularity' and take advantage of the agent's encrypted, single-port communication, an administrator must edit the node and change the polling method (D).
By going to Manage Nodes, selecting the domain controller, and clicking 'Edit Properties,' the admin must find the 'Polling Method' section and select 'Agent'. Once saved, the Polling Engine will stop using WMI network calls and will instead wait for the agent to provide the data (if in Agent-Initiated mode) or reach out to the agent via the agent's port (if in Server-Initiated mode). This change ensures that the monitoring load is shifted to the agent and that the communication adheres to the desired security profile.
A subset of the monitored devices is due for maintenance. These devices are expected to be shut down and restarted multiple times during maintenance. Which action should be taken to prevent the devices from triggering alerts during this period without impacting data collection?
Answer : C
SolarWinds provides several ways to handle maintenance windows, but they have different impacts on historical data. According to the SolarWinds Platform Administrator Guide, 'Unmanaging' a node (Option D) stops all polling entirely, resulting in 'gaps' in your historical charts.
To prevent notifications while preserving data collection, the best practice is to Mute the devices during maintenance. When a device is 'Muted' (also known as 'Pause Actions'), the platform continues to poll the device and record its status and performance metrics (CPU, Memory, Latency) into the database. However, the alerting engine is instructed to suppress any notification actions (emails, scripts, etc.) for that specific entity. This ensures that you have a full historical record of the device's behavior during the maintenance period---showing exactly when it went down and came back up---without flooding the IT team with unnecessary alerts.
How can access to all reports be removed from user accounts?
Answer : D
In the SolarWinds Platform, report access is governed by both functional permissions and account limitations. While 'Disable Manage Reports' (Option B) prevents a user from editing or creating reports, it does not necessarily hide the 'Reports' menu or prevent the user from viewing existing reports they have access to. To completely remove the visibility and accessibility of all reports for a specific user account, an Account Limitation must be applied.
According to the SolarWinds Platform User Account Management documentation, account limitations act as a security filter that restricts what the user can see throughout the entire Web Console. By navigating to Settings > All Settings > Manage Accounts, selecting the user, and editing their Report Limitation, an administrator can choose 'No Reports'. This configuration ensures that when the user logs in, the Reports section will either be empty or completely hidden from their navigation bar, regardless of their other permissions. This is the most effective method for high-security environments or multi-tenant deployments where certain users should have zero visibility into the historical performance data or inventory summaries contained within the reporting engine.
Which two of the following export formats are supported in Hybrid Cloud Observability (HCO) reports? (Choose two.)
Answer : A, C
SolarWinds Hybrid Cloud Observability provides robust reporting capabilities designed for both technical analysis and executive presentation. The SolarWinds Platform Reporting Guide specifies that reports generated through the Web Console can be delivered or manually exported in several standardized formats.
Excel (.xls/.xlsx): This format is primarily used for data-heavy reports where administrators need to perform further calculations, sorting, or external data manipulation. It allows the raw table data from the report to be easily ingested into other business intelligence tools.
PDF: This is the standard format for automated delivery and 'executive-ready' documentation. It preserves the visual layout, including charts, logos, and specific formatting defined in the report builder.
While the platform uses JSON (Option B) for internal API communications and some dashboard configurations, and txt (Option D) might be used for certain log exports, they are not standard selectable 'export formats' within the primary Web-Based Report builder for end-user consumption. The primary focus of the reporting engine is providing human-readable (PDF) and spreadsheet-compatible (Excel) outputs.