SolarWinds Observability-Self-Hosted-Fundamentals Dumps - Pass SolarWinds Observability Self-Hosted Fundamentals Exam in First Attempt 2026

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.

Groups in the SolarWinds Platform are logical containers used to organize monitored entities for easier management, alerting, and reporting. According to the SolarWinds Platform Administrator Guide, one of the most powerful features of the grouping engine is the ability to automate membership. Specifically, groups can be created based on custom properties.

When defining a group, administrators can choose between 'Static Selection' (manual) or 'Dynamic Query.' By using dynamic queries, a group can be configured to automatically include any node, interface, or volume that matches specific criteria, such as a custom property value (e.g., Department = Engineering or Site = London). This ensures that as new infrastructure is added to the environment and tagged with the appropriate metadata, the groups update themselves without human intervention.

Regarding the other options: groups can be members of other groups (nested groups), which is a common practice for creating complex hierarchical views of an organization. The default status rollup mode is typically set to 'Mixed' or 'Show Worst Status' rather than 'Best Status,' to ensure that any single failure within the group is visible to the administrator. Finally, rollup options absolutely apply to all members within the group, as they define how the collective health of those members is calculated and displayed on the dashboard.

The SolarWinds Hybrid Cloud Observability (HCO) Platform is designed for maximum deployment flexibility to accommodate diverse enterprise security and infrastructure requirements. According to the SolarWinds Platform Installation and Upgrade Guide, the platform's architecture is fundamentally self-contained.

Operation without an internet connection (A): This is a critical requirement for many government, military, and high-security financial environments. The platform is capable of 'air-gapped' operation, where all polling, data processing, and visualization occur within a private network. While features like 'Platform Connect' (for cloud-based AI) may require a connection, the core monitoring, alerting, and reporting functions remain fully operational without any external internet access.

Deployment on-premises or in the cloud (B): HCO is truly hybrid. It can be installed on physical hardware or virtual machines within a local data center, or it can be deployed within a Virtual Private Cloud (VPC) on platforms like AWS or Azure. This allows organizations to maintain their monitoring infrastructure alongside their managed assets, regardless of where those assets reside.

While HCO provides AIOps and machine learning (Option C), this is a feature of specific licensing tiers and configuration states rather than a fundamental 'platform' characteristic that defines its deployment capability in the same way its offline and hybrid nature does.

SolarWinds Intelligent Maps are highly interactive, but their functionality is strictly gated by user permissions. According to the SolarWinds Platform documentation on Map Management, if a user can see nodes but cannot see their real-time status (the colored status ring) or perform advanced functions like nesting one map inside another, it points to a lack of Map Editing Rights.

Without 'Map Edit' permissions, the user is essentially in a 'restricted view' mode. They can see the physical entities that have been placed on a map, but the dynamic overlays---such as the status of the node or the ability to modify the hierarchy of the map---are disabled to prevent unauthorized changes to the global map configuration. To resolve this, a Platform Administrator must navigate to Settings > All Settings > Manage Accounts, edit the specific user account, and change the 'Map Management' or 'Allow Map Editing' permission to 'Yes'. This grants the user the ability to interact with the map's metadata and organizational structure, including nesting and status visualization.

The ability to create and manage Intelligent Maps in the SolarWinds Platform is tied to a specific set of granular user permissions. While a user may have general rights to view the console, creating a map involves placing entities onto a canvas and, frequently, utilizing background images or custom icons. According to the SolarWinds Platform documentation on Map Management, a critical prerequisite for full map creation functionality is the permission to add images (D).

In the user account settings under Settings > All Settings > Manage Accounts, there is a specific toggle for 'Allow Map Management' or 'Allow Editing.' However, if the underlying platform permission for 'Add Images' is not enabled, the user will find the map creation wizard restricted or non-functional. This is because Intelligent Maps rely on the platform's shared image library to store the metadata and visual components of the map. Without the right to write to this library (Add Images), the user is blocked from saving new map definitions to the database. This permission is often disabled by default for standard users to prevent the web server's storage from being filled with unauthorized or non-work-related image files.