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

Answer : A

AlertStack is a specialized AIOps feature within Hybrid Cloud Observability (HCO) designed to simplify incident response. According to the SolarWinds HCO Alerting documentation, an AlertStack cluster is an autogenerated grouping of related active alerts on related entities.

The primary goal of clustering is to reduce 'alert fatigue.' Instead of presenting a technician with twenty individual alerts (e.g., one for high CPU on a server, one for an application failure, and three for slow database response), AlertStack analyzes the relationships and dependencies between those entities. If the platform determines that the alerts are part of a single root-cause event---such as a storage array failure impacting multiple virtual machines and their applications---it automatically clusters them into a single visual timeline. This clustering is autogenerated by the platform's machine learning engine based on the AppStack dependency map; it does not require a user to manually group the alerts. This allows the IT team to identify the 'blast radius' of an incident and focus on the primary failure point rather than triaging dozens of symptoms individually.

Answer : C

In the SolarWinds Platform, 'Administrator' rights in the Web Console grant extensive control over monitoring configurations, but they are distinct from 'System Administrator' or 'Security Administrator' roles. According to the SolarWinds Platform User Account Management guide, a Web Console Administrator can manage nodes, create alerts , build reports , and customize dashboards.

However, for security reasons, the ability to manage passwords---specifically the credentials used for polling (SNMP strings, WMI service accounts, or external integration secrets)---is often restricted. While an admin can assign an existing credential to a node, the ability to add, edit, or view the clear-text/obfuscated passwords within the centralized Credential Library is a separate, higher-level security permission. This prevents a standard Web Administrator from potentially harvesting sensitive service account passwords from the database. This 'separation of duties' ensures that while a user can manage the monitoring environment, they cannot necessarily compromise the security of the underlying infrastructure accounts.

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 : C, D

When a new user account is created in the SolarWinds Platform, it is assigned a set of 'Default' permissions designed to provide a 'Read-Only' baseline of visibility. According to the SolarWinds Platform User Account Management guide, the platform is configured to ensure that new users can immediately benefit from the monitoring data without having the power to accidentally modify the environment.

Specifically, view all active alerts (C) and view all existing reports (D) are enabled by default. This ensures that any team member with a login can see the current health of the infrastructure and access historical performance data. These are considered 'Passive' rights that allow for operational awareness. Conversely, disable session time out (A) is a security-sensitive setting that is typically disabled by default to prevent abandoned sessions from remaining active on public or shared workstations. Self-manage dashboards (B), while a common feature, often requires explicit 'Dashboards' or 'View' management permissions to be toggled on by an administrator to prevent a proliferation of unmanaged or redundant dashboard pages within the database. By defaulting to alert and report visibility, SolarWinds follows the principle of providing immediate information for troubleshooting while reserving management and security-override functions for designated administrators.

Answer : A, B

AppStack is a specialized visualization tool designed to show the 'stack' of dependencies between different layers of an IT environment. According to the SolarWinds Platform Administrator Guide, AppStack has two defining characteristics:

Automatic Relationship Gathering (A): The tool uses the data already collected by various modules (SAM, VMAN, SRM) to automatically map how applications, database instances, servers, virtual hosts, and storage volumes are linked. This eliminates the need for manual manual line-drawing in most cases.

Customizable Visual Mapping (B): It provides an interactive environment view where users can filter by status, application name, or site to see a visual map of the infrastructure. This allows a user to click on a failing application and see exactly which virtual host or storage array might be causing the failure due to its relationship.

Options C and D describe PerfStack (Performance Analysis), which is the tool used for time-series correlation and dragging metrics onto charts. AppStack focuses on the structure of the environment, whereas PerfStack focuses on the performance data of the entities within that structure.

Answer : A

The SolarWinds Platform provides distinct tools for visualizing different aspects of environmental health and performance. AppStack is primarily an entity-relationship mapping tool. According to the SolarWinds SAM Administrator Guide, 'The AppStack Environment view provides a powerful layer of troubleshooting visibility by exposing all participating objects in your environment, as well as their relationships to one another'. It allows administrators to customize which entities (nodes, applications, volumes, etc.) are visible and how they are grouped to show dependencies.

Conversely, PerfStack (Performance Analysis) is the engine used for metric correlation. As stated in the SolarWinds Platform Administrator Guide, PerfStack allows users to 'drag and drop performance metrics from multiple entities onto a single chart to correlate data over time'. While AppStack excels at showing what is connected, PerfStack excels at showing how specific metrics (CPU, Latency, IOPS) across those connected entities interact. Therefore, a combination is required where AppStack handles the entities and PerfStack handles the metrics. Specifically, you use AppStack to identify the scope of entities involved in a performance bottleneck and then transition those entities into a PerfStack project to perform a deep-dive analysis of the metrics. This modular approach ensures that troubleshooting is both contextually aware (via AppStack) and data-driven (via PerfStack).

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.