Free OBSERVABILITY-SELF-HOSTED-FUNDAMENTALS Practice Test Questions and Answers (2026) Practice Questions

SolarWinds Hybrid Cloud Observability provides granular control over user access to the reporting module. Administrators can configure account permissions to: (A) prevent access to the entire reporting feature by denying the "Reports" permission; (C) prevent access to the Report Manager, which blocks the ability to create, edit, or delete reports; and (B) prevent users from seeing reports created by other users by leveraging report visibility settings (e.g., making reports private to the creator). These restrictions allow administrators to tailor report access based on user roles and responsibilities.

D. The permission system is not designed to block users from their own reports; ownership implies access. This would be a contradictory setting.

SolarWinds Platform Administrator Guide. (2023). Manage user accounts. SolarWinds Success Center. Retrieved from solarwinds.com. The section "Define what users can do with Orion Platform features and modules" details the specific permissions for "Reports" and "Report Management."

SolarWinds Platform Administrator Guide. (2023). Limit what users can see. SolarWinds Success Center. Retrieved from solarwinds.com. This section explains how account limitations can restrict data visibility within reports.

When a SolarWinds agent is configured to initiate communication with the application server (known as "active agent" or "agent-initiated mode"), it sends data to the SolarWinds server. This mode requires the agent to be able to reach the server over a specific port. The default TCP port used for this communication is 17778. Therefore, any firewalls between the agent-monitored server and the SolarWinds polling engine must be configured to allow outbound traffic from the agent to the server on TCP port 17778.

A. TCP 445 is used for Server Message Block (SMB) and is not related to SolarWinds agent communication.

B. TCP 17777 is the default port used for WMI-based polling by the SolarWinds server, not for agent communication.

D. TCP 17790 is used for server-initiated ("passive agent") communication, where the server polls the agent, not the other way around.

1. SolarWinds Port Requirements, "Ports for SolarWinds Platform products". The document lists TCP 17778 as the "Agent communication (agent-initiated)" port, required for communication from the agent to the Main Polling Engine, Additional Polling Engine, or Additional Web Server.

2. SolarWinds Platform Administrator Guide, "Deploy an agent on a Windows-based computer". The guide specifies the communication modes: "Server-initiated communication... Agent-initiated communication... The agent initiates communication with the polling engine on port 17778."

According to the official system requirements for the SolarWinds Platform, which underpins Hybrid Cloud Observability, the minimum supported version for the database server is Microsoft SQL Server 2019 (Standard or Enterprise). Support for older versions, such as SQL Server 2016 and 2017, has been deprecated in recent releases to ensure compatibility, performance, and security. Therefore, installations or upgrades of modern HCO versions require at least SQL Server 2019.

A. SQL server 2012 service pack 4: This version is significantly older and has not been supported for many years.

B. MS SQL server 2016 service pack 1: Support for SQL Server 2016 was officially removed in the SolarWinds Platform 2023.3 release.

D. MS SQL server 2012 R2: This version is also well below the minimum requirement and is not supported.

SolarWinds Platform 2024.1 System Requirements. (2024). SolarWinds Platform server software requirements. SolarWinds Success Center. Retrieved from the SolarWinds documentation, under the "Database Server" section, which lists "SQL Server 2019" and "SQL Server 2022" as the only supported versions.

Custom properties are a core feature of the SolarWinds Platform that allows administrators to extend the data model. They are user-defined fields created to store supplementary information about any monitored entity (nodes, interfaces, volumes, applications, etc.). This information, such as asset tags, physical location, department owner, or maintenance window, is not collected automatically. Once defined and populated, these properties can be leveraged in alerts, reports, dynamic groups, and custom views to organize, filter, and manage monitored elements more effectively based on business-specific criteria.

A. Custom properties are user-defined, not "built-in attributes." They are, however, commonly used to create the logic for dynamic device groups.

B. While stored in the SQL database, their primary purpose is for management and organization within the SolarWinds application, not just for database identification.

C. Custom properties are not pre-defined or automatically applied; they must be explicitly created and assigned to nodes or other elements by a user.

1. SolarWinds Platform Documentation. (2024). Create custom properties in the SolarWinds Platform. SolarWinds Success Center. Retrieved from https://documentation.solarwinds.com/en/successcenter/orionplatform/content/core-creating-custom-properties.htm. (This document states, "Custom properties are fields you can use to add your own information to monitored objects, such as nodes, volumes, or interfaces.")

2. SolarWinds Platform Documentation. (2024). Manage custom properties. SolarWinds Success Center. Retrieved from https://documentation.solarwinds.com/en/successcenter/orionplatform/content/core-custom-property-management.htm. (This guide explains how to create, edit, and assign these user-defined fields.)

3. SolarWinds Platform Documentation. (2024). Use custom properties in alerts. SolarWinds Success Center. Retrieved from https://documentation.solarwinds.com/en/successcenter/orionplatform/content/core-using-custom-properties-in-alerts.htm. (This page provides examples of how these user-defined fields are used to create more intelligent and targeted alerts.)

AppStack lets you decide which entity types (hosts, VMs, volumes, etc.) appear in the AppStack Environment, giving entity-level customization. PerfStack’s Performance Analysis view is purpose-built for dragging and dropping individual performance counters, enabling metric-level customization. The two tools work independently; entity control resides in AppStack while metric control resides in PerfStack.

B. AppStack cannot graph or select individual metrics; it only filters entity types.

C. They do not need to be combined; each tool already addresses a separate layer.

D. PerfStack customises metrics but cannot add/remove entities outside those already selected.

1. SolarWinds Platform Administrator Guide 2023.4, “Use the AppStack Environment view,” §2.1.3 – “…toggle entity types on or off to customise what appears.”

2. SolarWinds Platform Administrator Guide 2023.4, “Create Performance Analysis Projects (PerfStack),” §9.2 – “…drag metrics from entities to customise performance charts.”

SolarWinds Platform alerts are configured with trigger actions that execute when alert conditions are met. The "Send an E-Mail" action is a standard method for notifying personnel of an issue. The "Execute an External Program or Script" action allows for automated remediation or integration with other systems by running a script on the SolarWinds server. These are two of the most common and powerful built-in alert actions available for automating responses to network events.

A. add widgets to views: This is a view customization or dashboard management task, not an automated action triggered by an alert.

C. generate a report: This is a function of the reporting engine. While reports can be scheduled, it is not a direct, real-time alert action.

1. SolarWinds Platform Administrator Guide. (2024). Alert Actions. SolarWinds Success Center. Retrieved from SolarWinds documentation on "Use alert actions". Specifically, the sections detailing "Send an Email / Page" and "Execute an external program or script".

2. SolarWinds Platform Administrator Guide. (2024). Default alert actions in the SolarWinds Platform. SolarWinds Success Center. This document lists and describes the available alert actions, including sending emails and executing external programs.

SolarWinds Hybrid Cloud Observability (HCO) supports several account types for authentication and authorization. It can integrate with Azure Active Directory (AD) to use cloud-based identity services for user and group management. Internally, HCO uses "Orion Groups," which are logical containers within the platform. These groups are used to assign specific permissions, views, and limitations to a collection of individual or directory-based accounts, simplifying rights management across the user base.

C. Windows distribution AD: HCO integrates with Active Directory security groups for permissions, not distribution groups, which are primarily for email lists and typically cannot be assigned security rights.

D. Windows local domain: This is not a distinct account type. HCO supports individual Windows accounts, which can be local to the server or part of an Active Directory domain, but "local domain" is not a category.

SolarWinds Platform Administrator Guide. (2024). User account types in the Orion Web Console. SolarWinds Success Center. Retrieved from the SolarWinds documentation, section on "Add a new user account," which details Individual accounts, Group accounts (including Windows AD, Azure AD, and SAML), and Orion Groups.

In the SolarWinds Platform alerting engine, acknowledging an alert is a manual action taken by a user to indicate they are aware of the issue. This action takes ownership of the alert and, critically, halts the escalation process. This prevents subsequent notification tiers or more severe actions defined in the alert's configuration from being executed, allowing the user time to investigate and resolve the underlying problem without generating further unnecessary notifications.

B. Reset actions are executed only when the alert's reset conditions are met, signifying the issue is resolved, not just halted.

C. Reset conditions define the criteria for an alert to return to a normal state; they do not stop an active escalation.

D. Trigger actions are the initial set of operations that occur when an alert is first activated; they start the process, not halt it.

SolarWinds Platform Documentation, "Acknowledge alerts". (solarwinds.com/documentation/orion/docs/orionplatformcoreagacknowledgedalerts.htm). This document states, "When you acknowledge an alert, you are taking ownership of the triggered alert. Acknowledging an alert can stop the escalation of the alert, so that no further alert actions are executed."

The SolarWinds Platform's reporting engine is designed to generate comprehensive overviews of network and system performance over time. Key use cases include creating reports that detail the historical availability and response time metrics for monitored devices, which is crucial for Service Level Agreement (SLA) compliance and capacity planning. Additionally, reports are frequently used to summarize the current or recent health status of the environment, such as listing all nodes that are currently in a warning or critical state, providing a snapshot for daily health checks or management briefings.

B. Critical incidents needing immediate attention are the primary function of the alerting engine and dashboards, not static, historical reports.

C. Reporting on database dependencies is a specialized function, typically handled by modules like Database Performance Analyzer (DPA), not a general purpose of the core reporting engine.

1. SolarWinds Platform 2024.1 Documentation, "Create a report that shows the current status of nodes". This guide demonstrates creating reports based on node status, directly supporting option D.

2. SolarWinds Platform 2024.1 Documentation, "Reports and alerts for response time". This section details how to create reports focusing on availability and response time metrics, supporting option A.

3. SolarWinds Platform 2024.1 Documentation, "Create a web-based report". The overview describes using reports to "display information about your network in a comprehensive and easy-to-read format," which encompasses performance statistics like availability, response time, and current status.

In SolarWinds Hybrid Cloud Observability, default user permissions are configured based on the principle of providing visibility without granting modification rights. A standard, non-administrative user account is automatically granted permissions to see fundamental monitoring data. This includes viewing all active alerts to stay informed of environmental issues and viewing all existing reports to consume pre-configured performance and status information. These settings ensure that users have the necessary visibility for their roles without being able to make administrative changes.

A. Disabling the session timeout is a significant security setting and is not enabled by default for any user, as it increases security risks.

B. The ability to self-manage dashboards (create, edit, delete) is typically a separate, elevated permission that is not granted to users by default.

1. SolarWinds Platform 2023.4 Administrator Guide, "Manage user accounts". This section describes the creation and configuration of user accounts.

2. SolarWinds Platform 2023.4 Administrator Guide, "Account permissions". The list of default permissions shows that view-only rights for key areas like "Alerts" and "Reports" are standard, while management rights are typically disabled for new, non-admin accounts.