SolarWinds Observability-Self-Hosted-Fundamentals Exam Dumps

The transition from the legacy Orion Platform to Hybrid Cloud Observability (HCO) introduced stricter hardware and software prerequisites to support modern features like AIOps, advanced mapping, and high-performance data processing. According to the SolarWinds Hybrid Cloud Observability System Requirements, the platform requires modern SQL features for optimal performance.

While legacy versions of the Orion Platform may have supported SQL Server 2016 or even 2012 in older iterations, MS SQL Server 2019 is identified as the minimum supported version for new HCO installations. This requirement ensures compatibility with the latest database indexing and query optimization techniques used by the SolarWinds Platform to handle the high volume of time-series data generated by observability nodes. Additionally, using SQL 2019 or later (including SQL 2022) is necessary to ensure the platform can utilize specific security protocols and memory management improvements that are not available in the end-of-life SQL 2012 or SP1 versions of 2016.

In the SolarWinds alerting workflow, 'Acknowledgment' is a critical state change that coordinates the human response to an incident. According to the SolarWinds Platform Alerting Guide, acknowledging an alert communicates to the rest of the team that a specific technician has taken ownership of the issue.

The formal definition of acknowledgment is that the issue is being worked on and the alert will not be escalated. This is the most important functional result of the action: it halts the automated escalation chain. If an alert was configured to email a manager after 30 minutes of inactivity, acknowledging the alert at the 15-minute mark cancels that pending manager email. It signals to the system---and other operators---that active troubleshooting is underway and further automated 'noise' is unnecessary.

It is important to note that acknowledgment does not mean the issue is resolved (Option A); the alert remains active in the 'All Active Alerts' list (though often filtered into an 'Acknowledged' category) until the underlying trigger condition is cleared by the monitoring engine. It is a procedural tool for incident management, ensuring that once a human engages with a problem, the platform's automated notification logic steps aside to let them work without further distraction.

SolarWinds Intelligent Maps are highly interactive, but their functionality is strictly gated by user permissions. According to the SolarWinds Platform documentation on Map Management, if a user can see nodes but cannot see their real-time status (the colored status ring) or perform advanced functions like nesting one map inside another, it points to a lack of Map Editing Rights.

Without 'Map Edit' permissions, the user is essentially in a 'restricted view' mode. They can see the physical entities that have been placed on a map, but the dynamic overlays---such as the status of the node or the ability to modify the hierarchy of the map---are disabled to prevent unauthorized changes to the global map configuration. To resolve this, a Platform Administrator must navigate to Settings > All Settings > Manage Accounts, edit the specific user account, and change the 'Map Management' or 'Allow Map Editing' permission to 'Yes'. This grants the user the ability to interact with the map's metadata and organizational structure, including nesting and status visualization.

SolarWinds Intelligent Maps require specific functional permissions within the user's account settings to perform modifications. According to the SolarWinds Platform Administrator Guide, the ability to view a map does not automatically grant the right to edit or save changes to it.

The primary cause for being unable to save edits---such as adding new entities or changing the layout---is that the user does not have Intelligent Map edit rights assigned to their user account. In the SolarWinds Web Console, map permissions are granular. An administrator must go to Settings > All Settings > Manage Accounts, select the user, and ensure the 'Map Management' or specific 'Allow Map Editing' toggle is set to 'Yes'. If this permission is absent, the user may still be able to interact with the map in a 'live' temporary session (moving nodes around for visualization), but the 'Save' button will either be disabled or will result in an error because the platform's security layer prevents permanent changes to the database from unauthorized accounts.

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.