Exam Overview
| Exam Code | Observability-Self-Hosted-Fundamentals |
| Exam Name | SolarWinds Observability Self-Hosted Fundamentals |
| Vendor | SolarWinds |
| Total Questions | 75 |
| Last Updated | 26-Oct, 2026 |
Why CertsPoint?
- Latest & Verified Questions
- Detailed Explanations
- Regular Updates
- Full-Length Practice Tests
- Boost Your Exam Confidence
PDF Study Materials
Downloadable guides and resources
Practice Tests
Full-length tests with real exam experience
Progress Tracking
Monitor your performance and improvement
Study Anywhere
Access on desktop, tablet, and mobile
Secure Payment
Privacy Protected
Money Back Guarantee
Free Observability-Self-Hosted-Fundamentals Practice Questions
Explore 4 free practice questions for the SolarWinds Observability-Self-Hosted-Fundamentals exam and review the answers and explanations to support your preparation.
-
Question 1
Multiple answersWhich two of the following account types are supported in SolarWinds Hybrid Cloud Observability (HCO)? (Choose two.)
-
Option A:Correct
Azure active directory (AD)
-
Option B:Correct
Orion group
-
Option C:Correct
Windows distribution AD
-
Option D:Correct
Windows local domain
Show Answer & Explanation Hide Answer & Explanation
Correct Answer: 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.
-
-
Question 2
Multiple answersWhat are custom properties and how are they used?
-
Option A:Correct
built-in attributes used for dynamic device grouping
-
Option B:Correct
static fields used to identify nodes in SQL database
-
Option C:Correct
static, pre-defined fields automatically applied to all monitored nodes
-
Option D:Correct
user-defined fields to store additional node or element information
Show Answer & Explanation Hide Answer & Explanation
Correct Answer: 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.
-
-
Question 3
Single answerWhat indicates an alert cluster has been eliminated (i.e., end conditions have been met)?
-
Option A:Correct
auto-closed
-
Option B:Correct
closed
-
Option C:Correct
completed
-
Option D:Correct
resolved
Show Answer & Explanation Hide Answer & Explanation
Correct Answer: 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.
-
-
Question 4
Single answerHow can access to all reports be removed from user accounts?
-
Option A:Correct
add to report group and modify access
-
Option B:Correct
disable manage reports permissions
-
Option C:Correct
set user account report limitation to default
-
Option D:Correct
set user account report limitation to no reports
Show Answer & Explanation Hide Answer & Explanation
Correct Answer: 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.
-