SolarWinds Observability Self-Hosted Fundamentals Observability-Self-Hosted-Fundamentals Exam Questions

Answer : A

Anomaly-Based Alerting represents a shift from static thresholds to behavioral analysis in the HCO platform. According to the SolarWinds HCO Alerting Engine documentation, this feature uses machine learning to establish a 'baseline' for specific metrics like CPU load or memory usage over a period of 7 to 30 days.

The primary benefit is that it analyzes entity behavior and triggers an alert only when a metric deviates significantly from its historical 'normal' for that specific day and time. For example, if a server traditionally runs at 90% CPU during a Sunday night backup, a static 80% threshold alert would trigger a 'false positive' every week. Anomaly-based alerting learns this behavior and will only fire an alert if the CPU hits 90% on a Tuesday morning when the normal load is only 20%.

This reduces alert noise by focusing on true anomalies rather than simple threshold violations. It does not 'remove the requirement for trigger conditions' (Options B and C); instead, it replaces a static numerical threshold with a dynamic, machine-learned threshold. The administrator still defines which entities to monitor and how sensitive the anomaly detection should be.

Answer : A

In Hybrid Cloud Observability (HCO), specifically within the AlertStack feature, related alerts are grouped into clusters to reduce 'alert fatigue' and provide a unified view of an incident. According to the SolarWinds HCO Alerting Guide, an alert cluster transitions through several states based on the status of the underlying trigger conditions.

When the primary issues that triggered the alerts within the cluster are addressed and the 'Reset Conditions' for those alerts are satisfied, the cluster is automatically managed by the system. The term used to define a cluster that has met its end conditions is auto-closed. Unlike manual 'acknowledgment' or 'resolution,' which are user-driven actions, 'auto-closed' signifies that the platform's monitoring engine has verified the environment has returned to a healthy state and the cluster no longer requires active monitoring or intervention. This automated lifecycle management is central to the AIOps and machine-learning capabilities of the platform, ensuring that the dashboard only reflects currently active, actionable incidents rather than historical events that have already been naturally corrected.

Answer : C

According to the SolarWinds Platform Administrator Guide regarding Modern Dashboards, the platform introduces several new widget types designed for high-performance data visualization. The widget shown in the image, which displays a single, large numerical value (the number '1') representing a specific count of 'DOWN Nodes' against a distinct colored background, is officially categorized as a KPI (Key Performance Indicator) widget.

KPI widgets are specifically engineered to provide an immediate 'at-a-glance' understanding of critical metrics. Unlike the legacy 'Classic' dashboards which relied on multi-row tables or fixed gauges, the Modern Dashboard KPI widget allows for a highly streamlined presentation of data derived from SWQL (SolarWinds Query Language). In this instance, the widget is likely running a query such as SELECT count(NodeID) FROM Orion.Nodes WHERE Status = 2, which returns a single scalar value. This value is then rendered prominently in the center of the widget.

One of the defining features of the KPI widget in HCO is its ability to use Conditional Formatting. This allows the background color of the widget to change dynamically based on the value returned by the query; for example, the background may turn red if the count of down nodes is greater than zero, providing a visual alert to the NOC staff. This type of widget is distinct from a 'table' (D), which displays multiple rows of data, or a 'counter' (A), which is typically a legacy term for simple incremental statistics. It is also not a 'custom HTML' (B) widget, as those are used for embedding external content or custom code rather than native data point visualization. The KPI widget remains the primary tool for displaying high-level summary statistics, such as active alert counts, total interface errors, or, as seen here, the availability status of nodes across the environment.

Answer : A

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.

Answer : A, B, C

Access control for reporting in Hybrid Cloud Observability (HCO) is highly granular, allowing administrators to define exactly what a 'standard' (non-admin) user can do within the reporting module. According to the SolarWinds Platform User Account Management guides, three distinct restrictions can be applied:

Preventing Access to All Reports (A): By setting a 'Report Limitation' on the user account to 'No Reports,' the entire module is effectively hidden from the user.

Preventing Access to Reports by Other Users (B): This is a privacy and security feature. Administrators can configure report permissions so that users can only see the reports they have created or those explicitly shared with them, hiding the potentially sensitive custom reports created by other teams.

Preventing Access to the Report Manager (C): The 'Report Manager' is the administrative interface used to create, schedule, and delete reports. By removing the 'Manage Reports' permission from a user account, you allow them to view and run existing reports but prevent them from accessing the management tools required to modify them.

Option D is logically incorrect because if a user has access to reports at all, they must be able to see the ones they are authorized for; 'preventing access to their own reports' while allowing others would not be a standard security use case.

Answer : C

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.

Answer : A, D

The modern web-based report builder in SolarWinds is highly integrated with the rest of the platform's visualization tools. According to the SolarWinds Platform Reporting Guide, reports are no longer limited to simple data tables; they can incorporate rich, interactive content already created elsewhere in the console.

Two key configurations available as content are existing intelligent maps (A) and existing widgets (D).

Existing Intelligent Maps: This allows an administrator to take a visually mapped dependency or network topology and embed it directly into a scheduled report. This provides a geographical or logical context to the data that static tables cannot provide.

Existing Widgets: Most widgets (resources) found on Summary or Node Details pages---such as 'Top 10 Nodes by Response Time' or 'Active Alerts'---can be added to a report as a component. This ensures consistency between what users see in real-time on their dashboards and what they receive in their weekly PDF summaries.

While you can embed performance data, the report builder is designed to consume these pre-configured UI elements (Maps and Widgets) to simplify report creation and maintain a unified look and feel across the observability suite.