SolarWinds Observability Self-Hosted Fundamentals Observability-Self-Hosted-Fundamentals Exam Questions

Answer : B

Network Discovery is an automated process to scan subnets and import new infrastructure. However, the discovery engine includes logic to prevent duplicate entries and ignore non-relevant assets. According to the SolarWinds Platform Administrator Guide, if specific devices are missing from the results, the most common administrative cause is the Discovery Ignore List.

The 'Ignore List' is a database of IP addresses or MAC addresses that the platform has been explicitly told to skip. This often happens if a device was previously discovered but the administrator chose 'Ignore this node' during the import phase. The system remembers this choice to prevent the device from reappearing in every subsequent scan. Additionally, the platform automatically ignores any node that is already present in the 'Manage Nodes' list to avoid creating redundant monitoring objects.

While a timeout (Option C) or incorrect polling method (Option D) could cause a node to fail to respond with its full metadata, the device would typically still appear in the discovery results as a 'Generic' or 'ICMP-only' device rather than being skipped entirely. Only the Ignore List or pre-existing status causes a device to be excluded from the discovery results table during a scan of a valid subnet.

Answer : A

When integrating Active Directory (AD) with the SolarWinds Platform, the system is designed to leverage AD groups for role-based access control (RBAC). According to the SolarWinds Platform Administrator Guide, the platform specifically requires Security Groups for authentication and permission mapping.

Active Directory contains two primary group types: Security Groups and Distribution Groups. Distribution groups are intended purely for email lists and do not have a Security Identifier (SID) that can be used for assigning file system or application permissions. Because SolarWinds relies on the SID to grant web console access and define user rights, distribution groups will not appear in the search results when attempting to add new Windows groups to the platform. To resolve this, the AD administrator must either convert the existing distribution groups to security groups or create new security groups containing the desired users. Once the group type is set correctly to 'Security,' the SolarWinds search utility will be able to resolve the group name and SID, allowing it to be imported and assigned permissions within the console.

Answer : D

The Custom Property Import tool is designed to help administrators bulk-update metadata for hundreds or thousands of nodes simultaneously. According to the SolarWinds Platform Administrator Guide, maintaining data integrity is a priority during this process.

A critical feature supported during the import is that incoming values are validated before being written (D). When an administrator uploads a CSV or Excel file containing custom property values, the platform performs a validation check against the defined 'Type' of each property in the database. For example, if a custom property InstallDate is defined as a 'Date' type, and the import file contains a text string like 'Last Tuesday,' the validation engine will flag an error and prevent the import from corrupting the database. This validation also checks for character limits and ensures that values for restricted 'Drop-down' properties match the predefined allowed list. This safeguard is essential for ensuring that automated alerts and reports, which rely on this metadata, function correctly without being disrupted by malformed data entries.

Answer : A, B, C

Access control for reporting in Hybrid Cloud Observability (HCO) is highly granular, allowing administrators to define exactly what a 'standard' (non-admin) user can do within the reporting module. According to the SolarWinds Platform User Account Management guides, three distinct restrictions can be applied:

Preventing Access to All Reports (A): By setting a 'Report Limitation' on the user account to 'No Reports,' the entire module is effectively hidden from the user.

Preventing Access to Reports by Other Users (B): This is a privacy and security feature. Administrators can configure report permissions so that users can only see the reports they have created or those explicitly shared with them, hiding the potentially sensitive custom reports created by other teams.

Preventing Access to the Report Manager (C): The 'Report Manager' is the administrative interface used to create, schedule, and delete reports. By removing the 'Manage Reports' permission from a user account, you allow them to view and run existing reports but prevent them from accessing the management tools required to modify them.

Option D is logically incorrect because if a user has access to reports at all, they must be able to see the ones they are authorized for; 'preventing access to their own reports' while allowing others would not be a standard security use case.

Answer : A

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.

Answer : A, D

AlertStack in Hybrid Cloud Observability (HCO) uses alert clusters to group related active alerts into a single actionable incident. According to the SolarWinds HCO Alerting documentation, these clusters are designed to provide context beyond the alert itself by correlating different types of data.

Metric Values (D): Alert clusters include the specific performance data that triggered the alert, such as high CPU load percentages or interface latency values. This allows the administrator to see the 'why' behind the incident immediately within the cluster view.

Audit Events (A): To assist in root cause analysis, alert clusters can include relevant audit events. For example, if a node goes down immediately after a configuration change, the audit event showing who logged in and what they changed will be correlated within the cluster to provide a timeline of events leading to the alert.

While 'device status' is often the result of an alert, the cluster is specifically built to aggregate the underlying metrics and events (Audit/Events) to give a comprehensive picture of the environment's health.

Answer : A

Alert escalation in the SolarWinds Platform allows for a tiered response to critical issues (e.g., emailing a technician immediately, then emailing a manager if the issue persists for 30 minutes). According to the SolarWinds HCO Alerting Engine documentation, the primary mechanism for a human operator to pause this automated progression is acknowledgement.

When an active alert is acknowledged via the Web Console, several things happen:

The alert is moved to the 'Acknowledged' category, signaling to other team members that the issue is being addressed.

The 'Acknowledge' timestamp and the user's name are recorded.

The escalation chain is halted. Any further actions defined in the 'Escalation' tab of the alert configuration---which were scheduled to fire after a certain duration---are cancelled.

It is important to note that acknowledging an alert does not clear the alert or stop the 'Reset Conditions' from being monitored. If the node stays down, the alert remains active, but no further new escalation emails will be sent. The alert will only truly disappear once the environment returns to a healthy state and the reset conditions are met.