Key details for this exam, checked against the published exam outline
Each question shows the correct answer and an explanation of why it is right
Which two of the following conclusions can be made from the shown AppStack view? (Choose two.)
According to the SolarWinds Platform Administrator Guide for Hybrid Cloud Observability, the AppStack Environment View provides an interactive, visual mapping of relationships between monitored entities such as applications, servers, and storage. In the provided image, it is evident that a 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 that the 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 the Storage 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 the user 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.
Which three of the following actions can be taken within a PerfStack project? (Choose three.)
PerfStack (Performance Analysis) projects are highly versatile troubleshooting assets that can be shared and integrated across the SolarWinds Platform. According to the SolarWinds 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 a widget. 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.
Web console users are complaining of widgets moving within the web console view. What is causing this movement?
Layout instability in the SolarWinds Web Console is almost always a result of overlapping permissions on shared views. According to the SolarWinds Platform Administrator Guide, summary views (dashboards) are often shared across entire departments or user groups.
The cause of widgets 'moving' unexpectedly is typically that users have edit view rights and are editing views used by multiple users (D). In SolarWinds, if a view is assigned to multiple people and those people have the 'Edit View' permission, any change made by one user---such as dragging a widget to a different column, adding a new resource, or removing an old one---is a global change to that view's definition in the database.
When User A rearranges the dashboard to suit their screen or preference, User B will see those changes the next time their page refreshes. This creates a 'tug-of-war' scenario where different users keep moving widgets back and forth. To prevent this, administrators should follow the principle of least privilege: remove 'Edit View' rights from standard users and only allow a small number of designated 'View Administrators' to make changes. If individual personalization is required, the administrator should create unique, personal views for each user or group so that their edits do not impact the wider organization.
Which two of the following use cases are utilized for account limitations? (Choose two.)
Account Limitations are security filters applied at the user or group level to control data visibility within the Web Console. According to the SolarWinds Platform User Account Management guide, these limitations do not affect how data is collected (polling), but rather who can see the resulting data.
The two primary use cases are:
Access by Department (A): Organizations often use custom properties (like 'Department') to tag nodes. By applying an account limitation, you can ensure that the 'Finance' team only sees servers tagged for their department, while the 'IT' team sees the entire infrastructure.
Access by Device Type (B): Limitations can be set based on vendor, machine type, or other attributes. For instance, a Network Operations Center (NOC) team might be limited to seeing only 'Cisco' or 'Juniper' devices to keep their dashboard focused purely on networking gear.
Option C is incorrect because 'access to features' (like the ability to manage alerts or reports) is handled via Account Permissions, not limitations. Option D is incorrect because 'polling of devices' is a backend function of the Polling Engines, which is managed via the 'Manage Nodes' section rather than user-facing account limitations.
CPU utilization is being monitored on a critical Windows server and is set to notify when utilization exceeds 90%. Notification parameters are set to disregard those brief spikes over 90% and focus on sustained periods above 90%. What should be configured to accomplish the notification goal?
To prevent 'alert noise' caused by temporary performance spikes, the SolarWinds Platform allows for threshold persistence. According to the SolarWinds Platform Administrator Guide, simply setting a threshold at 90% would trigger an alert the moment a single poll returns a high value.
The correct configuration to ensure only sustained high utilization triggers an action is to set the node to change CPU status if the threshold is met for multiple polling cycles. This is found in the 'Edit Node' properties under the Thresholds section. For example, if the polling interval is 2 minutes and you set the condition to '10 minutes' (or 5 consecutive polls), the CPU status will only transition to Warning or Critical after the utilization has stayed above 90% for that entire duration. This filtering happens at the node/status level, ensuring that the alert engine only fires when there is a legitimate, sustained performance bottleneck rather than a transient spike caused by a routine background process.
Which two of the following items are required to use Anomaly-Based Alerts in SolarWinds Hybrid Cloud Observability (HCO)? (Choose two.)
Anomaly-Based Alerting is a premier feature of Hybrid Cloud Observability that moves beyond static thresholds to identify performance deviations based on historical behavior. According to the SolarWinds HCO Administrator Guide, this feature relies on cloud-assisted analytics to process complex datasets. To enable this, two specific components are required:
Advanced Machine-Learning Feature: This is the functional logic within the HCO platform that identifies patterns and establishes 'normal' baselines for metrics like CPU load or interface utilization.
Platform Connect: This is the essential bridge that links the self-hosted HCO instance to the SolarWinds cloud-based AIOps engine. Because anomaly detection requires significant computational power to analyze long-term historical trends, the heavy processing is often offloaded. Platform Connect ensures that the necessary metadata can be analyzed securely to generate the dynamic thresholds used for these alerts.
Without Platform Connect, the local server cannot access the machine-learning models required to calculate what constitutes an 'anomaly' versus standard operational variance. This architecture allows HCO to provide high-level AIOps capabilities without requiring massive localized hardware for every installation.
Which two of the following actions can be achieved through the My Deployment page in the web console? (Choose two.)
The My Deployment page is the centralized administrative hub for managing the health and scale of the SolarWinds Platform. According to the SolarWinds Platform Installation and Upgrade Guide, this page simplifies complex infrastructure tasks that previously required logging into the individual server consoles.
Centralized Upgrade (B): The 'Updates & Evaluations' tab allows administrators to download and orchestrate the upgrade of the main polling engine and all additional polling engines from a single interface. This 'Centralized Upgrade' feature ensures all components are updated in the correct order.
High Availability (HA) Pool Setup (D): The 'High Availability' tab provides the wizard-driven interface to create and manage HA pools. This allows you to link a primary server with a standby server to ensure near-zero downtime in the event of a hardware or software failure.
While you can view license status (Option A) or trigger diagnostics (Option C), license activation is typically handled via the License Manager, and diagnostic transmission is often a sub-function of the technical support workflow rather than the primary architectural focus of the 'My Deployment' management page.
Exam domains verified against: Official SolarWinds Observability-Self-Hosted-Fundamentals exam guide, last checked October 2026.
Understand the structural components of the SolarWinds platform and how to deploy it in your environment. Learn the network discovery capabilities that allow you to identify and add devices to your monitoring setup.
Manage monitored nodes and their statuses across your infrastructure. Work with agents to collect monitoring data from endpoints and maintain visibility across your environment.
Sample question from this domain above: Q2
Create dashboards and views tailored to your needs and organizational structure. Configure user accounts, permissions, custom properties, and groups to match your operational requirements.
Create and manage alerts that notify your team of important events, threshold breaches, and conditions requiring attention. Understand how to configure alert rules to keep your infrastructure stable.
Generate reports that track performance, trends, and incidents in your monitored environment. Use reporting tools to communicate infrastructure status and insights to stakeholders.
Sample question from this domain above: Q6
Use AppStack and PerfStack to visualize application dependencies and performance relationships. Employ Intelligent Mapping to understand how your infrastructure components interact and correlate.
Sample question from this domain above: Q1
Common questions about the exam itself
