Observability-Self-Hosted-Fundamentals Practice Questions

The Application Stack (AppStack) view in the SolarWinds Platform is a tool that automatically gathers and displays relationships between monitored entities to help identify the root cause of performance issues. It organizes objects into logical categories that represent the different layers of an application's environment. Key categories displayed include Applications, Servers (both physical and virtual), Virtualization (clusters, hosts, datastores), and Storage (arrays, LUNs). Database instances are typically categorized under Applications, and Servers are a fundamental category on their own.

B. NetFlow data provides traffic analysis and is visualized in NetFlow-specific views, not as a primary object category within the AppStack map.

D. SNMP pollers are components of the monitoring system (the SolarWinds Platform itself), not the monitored infrastructure entities displayed in AppStack.

1. SolarWinds Platform Administrator Guide. (2023). Troubleshoot environmental issues with AppStack. SolarWinds Success Center. The documentation describes the AppStack layout and lists the categories of objects it displays, including "Servers," "Virtualization," "Storage," and "Applications," which encompass database instances. (Section: AppStack for root cause analysis).

Custom properties are a core feature of the SolarWinds Platform that allows administrators to extend the data model. They are user-defined fields created to store supplementary information about any monitored entity (nodes, interfaces, volumes, applications, etc.). This information, such as asset tags, physical location, department owner, or maintenance window, is not collected automatically. Once defined and populated, these properties can be leveraged in alerts, reports, dynamic groups, and custom views to organize, filter, and manage monitored elements more effectively based on business-specific criteria.

A. Custom properties are user-defined, not "built-in attributes." They are, however, commonly used to create the logic for dynamic device groups.

B. While stored in the SQL database, their primary purpose is for management and organization within the SolarWinds application, not just for database identification.

C. Custom properties are not pre-defined or automatically applied; they must be explicitly created and assigned to nodes or other elements by a user.

1. SolarWinds Platform Documentation. (2024). Create custom properties in the SolarWinds Platform. SolarWinds Success Center. Retrieved from https://documentation.solarwinds.com/en/successcenter/orionplatform/content/core-creating-custom-properties.htm. (This document states, "Custom properties are fields you can use to add your own information to monitored objects, such as nodes, volumes, or interfaces.")

2. SolarWinds Platform Documentation. (2024). Manage custom properties. SolarWinds Success Center. Retrieved from https://documentation.solarwinds.com/en/successcenter/orionplatform/content/core-custom-property-management.htm. (This guide explains how to create, edit, and assign these user-defined fields.)

3. SolarWinds Platform Documentation. (2024). Use custom properties in alerts. SolarWinds Success Center. Retrieved from https://documentation.solarwinds.com/en/successcenter/orionplatform/content/core-using-custom-properties-in-alerts.htm. (This page provides examples of how these user-defined fields are used to create more intelligent and targeted alerts.)

CPU load can be removed from node-status computation either globally per node via Edit Node > Polling & Thresholds, or selectively under Node Child Status, which lists each metric that contributes to status. The All-Nodes widget and Mute functions do not alter the status roll-up logic.

A. Widget is read-only; no configuration controls.

C. Muting only suppresses alerts, it does not change how status is calculated.

1. SolarWinds Platform Admin Guide 2023.4 – “Edit a node > Polling” (Exclude CPU/Memory from status) step 4.

2. SolarWinds Platform Admin Guide 2023.4 – “Tune node-status calculations with Node Child Status”, para 1-3.

In SolarWinds Hybrid Cloud Observability, permissions are granularly controlled. The "Report Management" right is an administrative-level permission specifically required for modifying the core configuration of reports. This includes creating, deleting, and editing reports, which encompasses changing a report's schedule or its timing. Standard user permissions typically only allow for viewing, running, and exporting existing reports they have access to, but not altering their fundamental properties or schedules.

B. export the report: Exporting a report is a standard user-level function and does not require administrative report management permissions.

D. run an existing report: Running a report is a basic viewing privilege and is not considered a management task.

1. SolarWinds Platform Administrator Guide. "Manage user accounts." SolarWinds Success Center. This section details the different permission levels, distinguishing between user-level actions like viewing/running reports and administrative actions like editing schedules, which fall under "Report Management" rights.

2. SolarWinds Platform Administrator Guide. "User account permissions and rights." SolarWinds Success Center. This document explicitly lists "Manage Reports" as a privilege required to "create and modify reports and report schedules."

The described symptoms—inability to see entity status and the unavailability of the map nesting feature—are indicative of insufficient permissions for the Orion Maps feature. A user account lacking full "Map Editing Rights" can be restricted to a view-only or a basic creation mode. This prevents the use of advanced editor functions like nesting maps and can also limit the dynamic display of object statuses, as full data polling and rendering are part of the complete editing and management feature set. The combination of both issues points directly to a limitation on the map management functionality itself.

A. Administrative rights are not required; a non-admin can have full map permissions. This option is too broad.

C. Node management rights pertain to adding, deleting, or editing nodes, not the functionality of the map editor like nesting.

D. View edit rights relate to customizing web console dashboards and pages, which is a separate permission from managing Orion Maps.

SolarWinds Platform Administrator Guide. (2023). Define what users can do with Orion Platform features and modules. SolarWinds Success Center. Retrieved from solarwinds.com. In the section "Account rights for Orion Platform features," the "Orion Maps Management" permission governs the ability to create and edit maps.

In SolarWinds Hybrid Cloud Observability, default user permissions are configured based on the principle of providing visibility without granting modification rights. A standard, non-administrative user account is automatically granted permissions to see fundamental monitoring data. This includes viewing all active alerts to stay informed of environmental issues and viewing all existing reports to consume pre-configured performance and status information. These settings ensure that users have the necessary visibility for their roles without being able to make administrative changes.

A. Disabling the session timeout is a significant security setting and is not enabled by default for any user, as it increases security risks.

B. The ability to self-manage dashboards (create, edit, delete) is typically a separate, elevated permission that is not granted to users by default.

1. SolarWinds Platform 2023.4 Administrator Guide, "Manage user accounts". This section describes the creation and configuration of user accounts.

2. SolarWinds Platform 2023.4 Administrator Guide, "Account permissions". The list of default permissions shows that view-only rights for key areas like "Alerts" and "Reports" are standard, while management rights are typically disabled for new, non-admin accounts.

The SolarWinds Platform's reporting engine is designed to generate comprehensive overviews of network and system performance over time. Key use cases include creating reports that detail the historical availability and response time metrics for monitored devices, which is crucial for Service Level Agreement (SLA) compliance and capacity planning. Additionally, reports are frequently used to summarize the current or recent health status of the environment, such as listing all nodes that are currently in a warning or critical state, providing a snapshot for daily health checks or management briefings.

B. Critical incidents needing immediate attention are the primary function of the alerting engine and dashboards, not static, historical reports.

C. Reporting on database dependencies is a specialized function, typically handled by modules like Database Performance Analyzer (DPA), not a general purpose of the core reporting engine.

1. SolarWinds Platform 2024.1 Documentation, "Create a report that shows the current status of nodes". This guide demonstrates creating reports based on node status, directly supporting option D.

2. SolarWinds Platform 2024.1 Documentation, "Reports and alerts for response time". This section details how to create reports focusing on availability and response time metrics, supporting option A.

3. SolarWinds Platform 2024.1 Documentation, "Create a web-based report". The overview describes using reports to "display information about your network in a comprehensive and easy-to-read format," which encompasses performance statistics like availability, response time, and current status.

In the SolarWinds Platform alerting engine, acknowledging an alert is a manual action taken by a user to indicate they are aware of the issue. This action takes ownership of the alert and, critically, halts the escalation process. This prevents subsequent notification tiers or more severe actions defined in the alert's configuration from being executed, allowing the user time to investigate and resolve the underlying problem without generating further unnecessary notifications.

B. Reset actions are executed only when the alert's reset conditions are met, signifying the issue is resolved, not just halted.

C. Reset conditions define the criteria for an alert to return to a normal state; they do not stop an active escalation.

D. Trigger actions are the initial set of operations that occur when an alert is first activated; they start the process, not halt it.

SolarWinds Platform Documentation, "Acknowledge alerts". (solarwinds.com/documentation/orion/docs/orionplatformcoreagacknowledgedalerts.htm). This document states, "When you acknowledge an alert, you are taking ownership of the triggered alert. Acknowledging an alert can stop the escalation of the alert, so that no further alert actions are executed."

To ensure a view runs continuously in a Network Operations Center (NOC) without interruption from user inactivity, the session timeout for that specific user account must be disabled. Within the user account settings, an administrator can override the global session timeout policy. By selecting the "Disable Session Timeout" option for the NOC user account, the web console session for that user will remain active indefinitely, preventing automatic logouts and ensuring the display is always current.

B. Granting "manage dashboard" permissions allows the user to edit dashboards but does not affect the session's idle timeout.

C. Granting "manage view" permissions allows the user to edit views but does not prevent the session from timing out due to inactivity.

D. Setting an account expiration date controls the account's overall lifespan, not the duration of an individual login session.

1. SolarWinds Platform Administrator Guide. "Define what and how users can access the SolarWinds Platform". SolarWinds Press. Under the "Account session settings" subsection, it describes the "Disable Session Timeout" option, stating it is "Used for accounts that display NOC views." This directly supports the correct answer.

The screenshot provides two clear pieces of information. First, the title at the top, "Environment for MS Exchange Server," indicates that the AppStack view has been filtered to show only the objects and their relationships that are relevant to a specific application instance. Second, in the top right corner of the interface, the checkbox labeled "Hide categories with no objects" is visibly selected. This user interface setting filters out entire categories from the left-hand navigation pane if they do not contain any objects related to the current context (in this case, the MS Exchange Server).

C. The "Storage" category is visible, which suggests the Storage Resource Monitor (SRM) module is installed. The message "No...objects found" simply means no storage objects are related to the filtered application.

D. The ability to see the AppStack view does not imply administrator access; a user with appropriate, limited view permissions could see the same information.

1. SolarWinds Platform Administrator Guide. "AppStack for the SolarWinds Platform". SolarWinds Press. This section explains that AppStack provides an "interactive map of your objects and their relationships" and that the view can be focused on a specific object, such as an application, which validates option A. The documentation also describes the UI controls, including the "Hide categories with no objects" option, validating option B.