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

SolarWinds agents support two communication modes: 'Server-Initiated' (Passive) and 'Agent-Initiated' (Active). According to the SolarWinds Platform Agent requirements and port information, the direction of communication determines which firewall ports must be open.

When an agent is configured for Agent-Initiated communication (where the agent on the managed node reaches out to the SolarWinds server), it uses TCP port 17778. This port must be open for inbound traffic on the SolarWinds Main Polling Engine or Additional Polling Engine. This mode is highly beneficial for monitoring servers in DMZs or remote sites where the SolarWinds server cannot initiate a connection through the firewall, but the remote node is allowed to communicate back to the primary management network. Port 17777 (Option B) is used for the legacy Orion Information Service, and 17790 (Option D) is used for specific client-to-server messaging in different contexts, but 17778 is the dedicated, encrypted port for agent-initiated data transmission.

The SolarWinds Agent is a versatile polling tool, but it must be compatible with the underlying Operating System (OS) to function correctly. According to the SolarWinds Platform Agent requirements, the agent software is designed to run on a wide variety of modern Windows and Linux distributions.

For the Windows ecosystem, the agent supports both server-grade and enterprise-grade workstation operating systems. Windows Server 2022 (D) is fully supported, allowing for deep monitoring of the latest Microsoft server environments, including support for AppInsight applications. Similarly, Windows 11 Enterprise (C) is a supported platform, which is particularly useful for monitoring high-end workstations, jump boxes, or remote endpoints that act as critical nodes in the network.

While SolarWinds does support various Linux distributions (such as RHEL, CentOS, and Ubuntu), Debian 11 and Fedora (Options A and B) are often not listed as 'officially primary supported' in the same tier as the Windows or main enterprise Linux distributions in current HCO documentation. The Windows agent remains the most feature-complete version of the software, supporting a broader range of monitoring types (like Quality of Experience and deep application analysis) compared to its Linux counterparts. Therefore, for an HCO deployment focusing on the latest infrastructure, Windows Server 2022 and Windows 11 are the verified answers.

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.

In the SolarWinds Platform, visibility of specific reports is managed through Report Limitations. According to the SolarWinds Platform Reporting Guide, even if a user has general permissions to view nodes, an administrator can restrict their access to specific reports to ensure data privacy or to simplify their workspace.

By creating a report limitation, you define a rule---such as filtering by a custom property or report category---and apply it directly to a user's account settings. Once applied, the user will only see the reports that match the criteria of that limitation when they navigate to the Reports section of the Web Console. This is different from a standard Account Limitation (Option D), which restricts the visibility of the nodes themselves across the entire platform. Using a report-specific limitation allows the user to still monitor the nodes in real-time views while preventing them from accessing sensitive historical or inventory data contained in specific PDF or web-based reports.

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.

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.

In Hybrid Cloud Observability (HCO), reports are organized using specific metadata to make them searchable and manageable. According to the SolarWinds Platform Administrator Guide, every report created or provided out-of-the-box is associated with a category.

Categories serve as the primary organizational structure in the Report Manager. Examples of standard categories include 'Inventory,' 'Performance,' 'Historical,' or 'User Accounts'. When creating a new report, the user is prompted to assign it to one of these categories or create a new one, which then dictates where the report appears in the navigation tree.

While the system may track who created a report, fields like 'Owner' (Option D) or 'Creator' (Option B) are not standard, visible metadata properties used for the primary sorting and management of web-based reports in the same way the category is. 'Format' (Option C) refers to the export type (PDF/Excel) and is a function of how the report is run or scheduled, rather than an inherent property of the report definition itself.

The alerting engine in the SolarWinds Platform uses a 'Scope' and 'Condition' logic to determine when an action should fire. According to the SolarWinds Platform Alerting Guide, the 'Scope' defines which objects the alert engine should evaluate, while the 'Condition' defines what performance metric triggers the alert.

To limit an alert to a specific set of router interfaces, the administrator must modify the scope on the trigger conditions. In the Alert Wizard, under the 'Trigger Condition' tab, there is a section titled 'I want to alert on...' (Interface) and a secondary section for 'The scope of the alert'. By adding specific rules to this scope---such as Node Name is Router-A or Interface Alias contains WAN---the alert engine will ignore the thousands of other interfaces in the database and only monitor the 75% utilization threshold on those specific targets. Using account limitations (Option D) is incorrect for this purpose, as account limitations affect what a user sees in the console, not how the backend alerting engine processes data.

SolarWinds Hybrid Cloud Observability supports a variety of authentication methods to ensure seamless integration with enterprise identity providers. According to the SolarWinds Platform Installation and Upgrade Guide, the two primary modern account types used for centralized management are Azure Active Directory (AD) and Orion Groups.

Azure Active Directory (AD): This allows organizations to leverage their cloud-based identity provider for Single Sign-On (SSO) and centralized user management. HCO integrates directly with Azure AD to authenticate users based on their existing cloud credentials.

Orion Group: This is a local platform account type that allows administrators to define permissions at a group level rather than for individual users. By creating an Orion Group, you can assign a specific set of view, alert, and report permissions once, and any user assigned to that group automatically inherits those rights.

While 'Windows Local Domain' (standard AD) is supported for on-premises deployments, the specific phrasing in HCO documentation emphasizes the shift toward cloud-native and group-based management. 'Windows distribution AD' is incorrect because SolarWinds requires security groups for permission mapping, not distribution groups.

PerfStack is a cross-stack data correlation tool, but its visibility is constrained by the underlying data collection modules and user security settings. According to the PerfStack Troubleshooting Guide, there are two primary reasons why specific entity data (like Storage) would be missing:

Product Not Installed: Performance data for deep storage metrics (like LUN latency, Array IOPS, or Pool capacity) requires the Storage Resource Monitor (SRM) module or the equivalent HCO storage licensing tiers. If only Server & Application Monitor (SAM) is installed, the user will see the application status, but the specific storage back-end metrics will not be available for selection in the PerfStack pallet because the 'collector' for that data doesn't exist.

Account Limitations: SolarWinds uses Account Limitations to restrict user access to specific parts of the infrastructure. If a user account is limited to 'Department = Sales' or 'Vendor = Cisco,' and the storage entities do not meet those criteria, those entities will be filtered out of the search results in PerfStack. Even if the data exists in the database, the platform security layer prevents the user from 'finding' or displaying it to ensure data privacy and multi-tenant security.