SolarWinds Observability-Self-Hosted-Fundamentals Exam Questions

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.

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 advanced alerting scenarios, particularly with performance metrics like disk fragmentation or temperature, the 'Trigger Condition' and 'Reset Condition' often require different thresholds to prevent 'flapping'---a state where an alert rapidly toggles between triggered and reset states because the metric is hovering right at the threshold line. According to the SolarWinds Platform Alerting Guide, while the default behavior is to reset when trigger conditions are no longer true (Option D), this would reset the alert as soon as fragmentation hit 29.9%.

To satisfy the specific requirement where the issue is only 'resolved' at 10%, a custom Reset Condition must be defined. By selecting 'set reset condition to reset when condition is below a set percent,' the administrator can explicitly define a separate value ($10\%$) from the trigger value ($30\%$). This creates a 'deadband' or hysteresis effect, ensuring the alert remains active and visible until the database maintenance has successfully reduced the fragmentation to the desired healthy level. This configuration is essential for AppInsight applications where returning to a 'not-critical' state (e.g., 29%) does not necessarily mean the underlying performance bottleneck has been sufficiently remediated.

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.

The ability to create or modify reports is a high-level administrative function in the SolarWinds Platform, distinct from the ability to simply view them. According to the SolarWinds Platform User Account Management guide, this is controlled by the Report Management right.

To restrict a specific group of users from creating or editing reports while still allowing them to view existing ones, the administrator must remove the 'Manage Reports' permission from their user accounts. When this right is set to 'No,' the 'Manage Reports' button is hidden from the 'All Reports' view for that user. They can still click on and run any report they have access to, but they will lack the interface options to enter the 'Report Builder,' change schedules, or delete entries. This provides a secure way to delegate report consumption to the wider team while centralizing report creation within a smaller group of 'power users' or administrators. Option D is incorrect as it refers to Alerts, which is a separate permission set entirely.