Pass4Future also provide interactive practice exam software for preparing SolarWinds Observability Self-Hosted Fundamentals (Observability-Self-Hosted-Fundamentals) Exam effectively. You are welcome to explore sample free SolarWinds Observability-Self-Hosted-Fundamentals Exam questions below and also try SolarWinds Observability-Self-Hosted-Fundamentals Exam practice test software.
Do you know that you can access more real SolarWinds Observability-Self-Hosted-Fundamentals exam questions via Premium Access? ()
A user is building a PerfStack project to troubleshoot an issue with an application. The user is unable to find data for the storage entities that the application accesses beyond application status. Which two of the following reasons explain this discrepancy? (Choose two.)
Answer : A, C
PerfStack is a cross-stack data correlation tool, but its visibility is constrained by the underlying data collection modules and user security settings. According to the PerfStack Troubleshooting Guide, there are two primary reasons why specific entity data (like Storage) would be missing:
Product Not Installed: Performance data for deep storage metrics (like LUN latency, Array IOPS, or Pool capacity) requires the Storage Resource Monitor (SRM) module or the equivalent HCO storage licensing tiers. If only Server & Application Monitor (SAM) is installed, the user will see the application status, but the specific storage back-end metrics will not be available for selection in the PerfStack pallet because the 'collector' for that data doesn't exist.
Account Limitations: SolarWinds uses Account Limitations to restrict user access to specific parts of the infrastructure. If a user account is limited to 'Department = Sales' or 'Vendor = Cisco,' and the storage entities do not meet those criteria, those entities will be filtered out of the search results in PerfStack. Even if the data exists in the database, the platform security layer prevents the user from 'finding' or displaying it to ensure data privacy and multi-tenant security.
What are custom properties and how are they used?
Answer : D
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.
Which two of the following settings are present in modern dashboards and not classic dashboards? (Choose two.)
Answer : C, D
Modern Dashboards represent a significant evolution over the legacy 'Classic' summary views in the SolarWinds Platform. According to the SolarWinds Platform Administrator Guide, there are several architectural differences designed to improve performance and flexibility.
Define visible data using SWQL (D): Unlike classic dashboards that rely on a fixed 'Data Selection' wizard or pre-built resources, modern dashboards allow administrators to hand-edit SWQL (SolarWinds Query Language) queries directly within the widget configuration. This provides near-infinite flexibility to filter and display data in ways that were previously impossible without custom coding.
Configure refresh rates (C): Classic dashboards typically rely on the global web console refresh interval (often 5 minutes) or a full page reload. Modern dashboards introduce the ability to set individual refresh intervals for each widget (from 1 second to 24 hours), or configure a 'Modern Widget Refresh' default for the entire dashboard. This ensures that critical real-time data is updated more frequently than static inventory data on the same page.
While 'NOC mode' (Option B) and 'Account Limitations' (Option A) are compatible with the broader SolarWinds environment, they are standard platform features that have existed in classic views for years and are not 'unique' new settings specific only to the modern dashboarding engine.
Which out-of-the-box property is associated with a web-based report?
Answer : A
In Hybrid Cloud Observability (HCO), reports are organized using specific metadata to make them searchable and manageable. According to the SolarWinds Platform Administrator Guide, every report created or provided out-of-the-box is associated with a category.
Categories serve as the primary organizational structure in the Report Manager. Examples of standard categories include 'Inventory,' 'Performance,' 'Historical,' or 'User Accounts'. When creating a new report, the user is prompted to assign it to one of these categories or create a new one, which then dictates where the report appears in the navigation tree.
While the system may track who created a report, fields like 'Owner' (Option D) or 'Creator' (Option B) are not standard, visible metadata properties used for the primary sorting and management of web-based reports in the same way the category is. 'Format' (Option C) refers to the export type (PDF/Excel) and is a function of how the report is run or scheduled, rather than an inherent property of the report definition itself.
User access is being modified by adding Windows groups and setting group permissions. Two users are in multiple groups with different permissions. The correct permissions need to be applied to the users involved in multiple groups. Which two of the following actions will accomplish this goal? (Choose two.)
Answer : A, D
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 the SolarWinds Platform User Account Management guide, 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 the search order of 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.
