Observability-Self-Hosted-Fundamentals Exam Questions and Answers (Page: 1)

QUESTION: 1

A performance issue on a network is being troubleshooted and needs customization of metrics and entities to be viewed during troubleshooting.
Which tool combination / no combination would allow this to happen?

AppStack allows customization of entities and PerfStack allows customization of metrics
AppStack alone allows customization of metrics and entities
AppStack and PerfStack combined together allow customization of metrics and entities
PerfStack alone allows customization of metrics and entities

Answer(s): A

Explanation:

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).

Reveal Solution Next Question

QUESTION: 2

How can access to all reports be removed from user accounts?

add to report group and modify access
disable manage reports permissions
set user account report limitation to default
set user account report limitation to no reports

Answer(s): D

Explanation:

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.

Reveal Solution Next Question

QUESTION: 3

What indicates an alert cluster has been eliminated (i.e., end conditions have been met)?

auto-closed
closed
completed
resolved

Answer(s): A

Explanation:

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.

Reveal Solution Next Question

QUESTION: 4

What are custom properties and how are they used?

built-in attributes used for dynamic device grouping
static fields used to identify nodes in SQL database
static, pre-defined fields automatically applied to all monitored nodes
user-defined fields to store additional node or element information

Answer(s): D

Explanation:

Custom Properties are one of the most versatile features of the SolarWinds Platform, providing a way to extend the metadata associated with monitored objects. The SolarWinds Platform Administrator

Guide defines them as "user-defined fields that allow you to add custom information to nodes, interfaces, volumes, or other monitored entities".

Unlike built-in attributes like "IP Address" or "Vendor," which are discovered automatically, custom properties are created by the administrator to suit specific business needs. Common examples include "Site Location," "Emergency Contact," "Department," or "Service Level Agreement (SLA) Tier". These fields are critical for organization and automation because they allow for:

Filtering and Grouping: You can create groups that automatically include any node where the "Department" custom property is set to "Finance".

Alerting: You can configure alerts to only trigger for nodes marked as "Mission Critical" in a custom property field.

Reporting: Reports can be generated to show the uptime of all nodes belonging to a specific "Owner" or "Cost Center".

Because they are user-defined, they provide the necessary flexibility to map technical monitoring data to real-world business structures.

Reveal Solution Next Question

QUESTION: 5

Which two of the following account types are supported in SolarWinds Hybrid Cloud Observability (HCO)? (Choose two.)

Azure active directory (AD)
Orion group
Windows distribution AD
Windows local domain

Answer(s): A,B

Explanation:

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.

Reveal Solution Next Question

QUESTION: 6

An alert has been created to email when AppInsight for SQL detects a database fragmentation that exceeds 30%. The issue is not considered resolved unless the fragmentation is below 10%. How would the reset conditions be configured for this alert?

set reset conditions to manual reset when issue is resolved
set reset condition to never reset and notify of all issues
set reset condition to reset when condition is below a set percent
set reset conditions to reset when trigger conditions are no longer true

Answer(s): C

Explanation:

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.

Reveal Solution Next Question

QUESTION: 7

What is the minimum supported version for SolarWinds Hybrid Cloud Observability (HCO) database server?

SQL server 2012 service pack 4
MS SQL server 2016 service pack 1
MS SQL server 2019
MS SQL server 2012 R2

Answer(s): C

Explanation:

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.

Reveal Solution Next Question

QUESTION: 8

Which two of the following export formats are supported in Hybrid Cloud Observability (HCO) reports? (Choose two.)

excel
JSON
PDF
txt

Answer(s): A,C

Explanation:

SolarWinds Hybrid Cloud Observability provides robust reporting capabilities designed for both technical analysis and executive presentation. The SolarWinds Platform Reporting Guide specifies that reports generated through the Web Console can be delivered or manually exported in several standardized formats.

Excel (.xls/.xlsx): This format is primarily used for data-heavy reports where administrators need to perform further calculations, sorting, or external data manipulation. It allows the raw table data from the report to be easily ingested into other business intelligence tools.

PDF: This is the standard format for automated delivery and "executive-ready" documentation. It preserves the visual layout, including charts, logos, and specific formatting defined in the report builder.

While the platform uses JSON (Option B) for internal API communications and some dashboard configurations, and txt (Option D) might be used for certain log exports, they are not standard selectable "export formats" within the primary Web-Based Report builder for end-user consumption. The primary focus of the reporting engine is providing human-readable (PDF) and spreadsheet- compatible (Excel) outputs.

Reveal Solution Next Question

SolarWinds Observability-Self-Hosted-Fundamentals Exam (page: 1)
SolarWinds Observability Self-Hosted Fundamentals
Updated on: 12-Feb-2026

Access free Observability-Self-Hosted-Fundamentals actual exam questions, answers, explanations and user discussions.

QUESTION: 1

Explanation:

QUESTION: 2

Explanation:

QUESTION: 3

Explanation:

QUESTION: 4

Explanation:

QUESTION: 5

Explanation:

QUESTION: 6

Explanation:

QUESTION: 7

Explanation:

QUESTION: 8

Explanation:

SolarWinds Observability-Self-Hosted-Fundamentals Exam (page: 1) SolarWinds Observability Self-Hosted Fundamentals Updated on: 12-Feb-2026

Access free Observability-Self-Hosted-Fundamentals actual exam questions, answers, explanations and user discussions.

QUESTION: 1

Explanation:

QUESTION: 2

Explanation:

QUESTION: 3

Explanation:

QUESTION: 4

Explanation:

QUESTION: 5

Explanation:

QUESTION: 6

Explanation:

QUESTION: 7

Explanation:

QUESTION: 8

Explanation:

SolarWinds Observability-Self-Hosted-Fundamentals Exam (page: 1)
SolarWinds Observability Self-Hosted Fundamentals
Updated on: 12-Feb-2026