Observability-Self-Hosted-Fundamentals Practice Questions

The export capabilities for chart-based reports are designed to provide both a visual representation and the underlying raw data. According to theSolarWinds Platform Administrator Guide, when viewing or scheduling a report that contains charts or graphs, the system supports two primary export formats:

PDF: This format is the standard for visual reports. It captures the rendered chart exactly as it appears in the Web Console, making it ideal for email distribution to management or for archival purposes where the visual trend is more important than the individual data points.

CSV (Comma Separated Values): When a chart is exported to CSV, the platform extracts the time-series data points used to generate that chart. This allows technical staff to import the raw performance numbers into external tools like Excel for deeper statistical analysis that may not be possible within the standard web view.

While the broader reporting engine supportsExcel (.xls)for tabular reports (as seen in Question 8), the specific function for exportingchart componentsoften defaults to CSV for the data layer and PDF for the visual layer.XML(Option D) is typically reserved for reportdefinitions(transferring a report from one server to another) rather than exporting the data results of a chart.

SolarWinds Hybrid Cloud Observability supports a variety of authentication methods to ensure seamless integration with enterprise identity providers. According to theSolarWinds Platform Installation and Upgrade Guide, the two primary modern account types used for centralized management areAzure Active Directory (AD)andOrion 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.

AppStackis a specialized visualization tool designed to show the "stack" of dependencies between different layers of an IT environment. According to theSolarWinds Platform Administrator Guide, AppStack has two defining characteristics:

Automatic Relationship Gathering (A): The tool uses the data already collected by various modules (SAM, VMAN, SRM) toautomaticallymap how applications, database instances, servers, virtual hosts, and storage volumes are linked. This eliminates the need for manual manual line-drawing in most cases.

Customizable Visual Mapping (B): It provides aninteractive environment viewwhere users can filter by status, application name, or site to see a visual map of the infrastructure. This allows a user to click on a failing application and see exactly which virtual host or storage array might be causing the failure due to its relationship.

Options C and D describePerfStack(Performance Analysis), which is the tool used for time-series correlation and dragging metrics onto charts. AppStack focuses on thestructureof the environment, whereas PerfStack focuses on theperformance dataof the entities within that structure.

Managing user permissions through Active Directory (AD) groups in SolarWinds requires an understanding of how the platform resolves conflicting rights. When a user belongs to multiple groups, the platform must determine which set of permissions takes precedence. According to theSolarWinds Platform User Account Managementguide, there are two primary ways to ensure the "correct" (often the most restrictive or most specific) permissions are applied.

Add users as individual users (A): Individual user account settings always take precedence over group settings in the SolarWinds Platform. If a user needs specific rights that differ from their assigned AD groups, creating a local or AD-linked individual account for them allows the administrator to "override" group-level permissions with 100% certainty.

Re-order groups (D): The SolarWinds Web Console allows administrators to change thesearch orderof groups. When a user logs in, the platform checks the groups in the order they are listed in the "Manage Accounts" screen. The first group match it finds is the one that defines the user's session permissions. By re-ordering the groups, an admin can ensure that the group with the "correct" intended permissions is processed first.

Options B and C are inefficient and unnecessary "nuclear" options that disrupt the benefits of using centralized AD management for the rest of the organization.

According to the SolarWinds Platform Administrator Guide for Hybrid Cloud Observability, theAppStack Environment Viewprovides an interactive, visual mapping of relationships between monitored entities such as applications, servers, and storage. In the provided image, it is evident thata filter is applied to show entities related to an application (A)because the left-hand navigation pane shows specific filters selected under the "Applications" category, and the main view displays a subset of the environment's total objects that correspond specifically to those application relationships. This filtering capability allows users to narrow down the environment to focus on the specific dependencies of a critical business service, such as Microsoft Active Directory or a SQL Server instance, which are shown as filtered groups in the sidebar.

Furthermore, it can be concluded thatthe option to hide categories with no objects is selected (B). A standard, unfiltered AppStack view typically displays every possible layer of the IT stack—including Transactions, LUNs, Pools, and Arrays—regardless of whether they contain active entities. However, in the provided view, only categories containing entities relevant to the current filter (such as Applications, Database Instances, Servers, and Volumes) are visible. This indicates that the "Hide categories with no objects" setting is active, which is a standard customization used to clean up the interface and highlight only the active parts of the dependency map.

While the view shows storage-related entities like "Volumes," this does not confirm whether theStorage Resource Monitor (SRM) is not installed (C), as basic volume data can often be collected via standard node polling. Additionally, the AppStack interface itself does not provide enough diagnostic data to verify if theuser account is given administrator access rights (D), as these visual elements are accessible to non-admin users with appropriate view permissions. Therefore, A and B are the only verified conclusions based on the visual evidence of the filtered environment.

PerfStack(Performance Analysis) projects are highly versatile troubleshooting assets that can be shared and integrated across the SolarWinds Platform. According to theSolarWinds Platform Administrator Guide, once a correlation project is built—linking metrics like CPU, Latency, and IOPS—it can be utilized in several ways.

Add as a menu bar item (A): A specific PerfStack project that is used frequently (such as "Core Switch Health") can be saved and added directly to the main navigation menu. This allows users to access the troubleshooting dashboard with a single click from anywhere in the console.

Share to non-web console users (B): PerfStack projects can be shared via a unique URL. This "Public Link" feature allows stakeholders who do not have a SolarWinds account (such as third-party vendors or executives) to view the real-time correlation data in a read-only browser view.

Show as a widget in a view (D): PerfStack projects can be embedded into Summary Views or Node Details pages as awidget. This provides context-sensitive performance data right alongside the standard node information, allowing for "at-a-glance" correlation without leaving the main dashboard.

While PerfStack provides visual data, it is typically treated as a dynamic, interactive "Project" or "Widget" rather than a static "dashboard graphic" (Option C) in the classic sense of a standalone image or icon.