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.

The SolarWinds Alerting Engine provides a wide array of "Trigger Actions" that occur automatically when an alert's conditions are met. According to the SolarWinds Platform Alerting Guide , these actions are designed to either notify a human operator or perform an automated remediation step.

Send an e-mail (D) : This is the most common alert action. It allows the system to send formatted notifications (including variables for node name, IP, and status) to individuals, distribution lists, or ticketing systems like ServiceNow or SolarWinds Service Desk.

Execute a script (B) : This is the primary tool for automated "self-healing." An alert can be configured to run a local batch file, a PowerShell script, or a VBScript on the SolarWinds server. For example, if a "Service Down" alert triggers, the system can automatically execute a script to attempt to restart that service on the remote node before a human technician even sees the alert.

Options A and C are incorrect because they are not "actions" triggered by the alerting engine. Adding widgets to views (Option A) is a manual customization task performed by an administrator in the web console. While you can schedule a report to be sent via email, the alerting engine itself does not generate a report (Option C) as a reactive trigger action to a node failure; reports are intended for historical analysis rather than immediate event response.

For Network Operations Centers (NOCs) that display SolarWinds dashboards on large wall-mounted monitors, maintaining a continuous session is vital. By default, the SolarWinds Platform implements a security timeout (often 15 to 20 minutes of inactivity) that automatically logs a user out to protect the console.

According to the SolarWinds Platform Administrator Guide , to prevent this for a dedicated NOC account, the administrator must disable session timeout default settings (A) . This is found within the "Advanced" section of the specific User Account settings. When this toggle is enabled, the platform ignores the global session timeout for that specific login, allowing the dashboard to refresh indefinitely without requiring manual re-authentication.

While granting management permissions (Options B and C) might allow the user to create the view, it does nothing to prevent the session from expiring. Similarly, an "Account Expiration Date" (Option D) only controls the long-term validity of the account, not the duration of an individual active web session. Disabling the timeout is the standard procedural requirement for any "Service Account" or "Display Account" used in a continuous monitoring environment.

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.

The reporting engine in the SolarWinds Platform is designed to provide historical documentation and summary data for management and technical analysis. According to the SolarWinds Platform Reporting Guide , reports are distinct from alerts; while alerts focus on real-time "critical incidents needing immediate attention" (Option B), reports focus on aggregated data over time.

Specifically, the two primary purposes shown in the options are:

Availability and Response Time Reports (A) : These provide a summary of how infrastructure has performed over a specific period (daily, weekly, monthly). This is used for Service Level Agreement (SLA) reporting to show that devices at a particular location maintained required uptime and performance metrics.

Status Summaries (D) : Reports can be generated to show the current or historical distribution of node health. A report on the "number of nodes in warning or critical states" provides an executive-level view of environmental stability, identifying which areas of the network are experiencing the most frequent issues.

Option C is incorrect as database dependencies are typically visualized live in AppStack or Intelligent Maps rather than in a static report. Option B describes the function of the Alerting Engine , which is intended for immediate operational response rather than the post-hoc analysis provided by reports.

AppStack is a specialized visualization tool designed to show the "stack" of dependencies between different layers of an IT environment. According to the SolarWinds 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) to automatically map 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 an interactive environment view where 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 describe PerfStack (Performance Analysis), which is the tool used for time-series correlation and dragging metrics onto charts. AppStack focuses on the structure of the environment, whereas PerfStack focuses on the performance data of the entities within that structure.

Platform Connect is a foundational technology in Hybrid Cloud Observability (HCO) that bridges the gap between the on-premises (self-hosted) installation and SolarWinds' cloud-based AIOps and machine learning services. According to the SolarWinds HCO Administrator Guide , the primary function enabled by this connection is anomaly-based alerting .

Anomaly detection requires significant computational resources to process months of historical performance data and build sophisticated behavioral baselines for thousands of metrics. To prevent this heavy processing from impacting the performance of the local monitoring server, SolarWinds offloads the analysis to a cloud-based machine learning engine. Platform Connect provides the secure, encrypted tunnel required to transmit relevant performance metadata to the cloud for analysis and receive dynamic threshold updates in return.

Without Platform Connect, the local instance is restricted to traditional static thresholds (e.g., "Alert if CPU > 90%"). With it, the system can identify "unusual" behavior (e.g., "Alert if CPU is 70% at 2:00 AM on a Tuesday, when it is normally 10%"). While HCO handles infrastructure monitoring and mapping locally, the specific "intelligence" layer that drives anomaly detection is the standout benefit provided by the Platform Connect architecture.

SolarWinds Intelligent Maps are highly interactive, but their functionality is strictly gated by user permissions. According to the SolarWinds Platform documentation on Map Management , if a user can see nodes but cannot see their real-time status (the colored status ring) or perform advanced functions like nesting one map inside another, it points to a lack of Map Editing Rights .

Without "Map Edit" permissions, the user is essentially in a "restricted view" mode. They can see the physical entities that have been placed on a map, but the dynamic overlays—such as the status of the node or the ability to modify the hierarchy of the map—are disabled to prevent unauthorized changes to the global map configuration. To resolve this, a Platform Administrator must navigate to Settings > All Settings > Manage Accounts , edit the specific user account, and change the " Map Management " or " Allow Map Editing " permission to " Yes ". This grants the user the ability to interact with the map's metadata and organizational structure, including nesting and status visualization.

In the SolarWinds alerting workflow, "Acknowledgment" is a critical state change that coordinates the human response to an incident. According to the SolarWinds Platform Alerting Guide , acknowledging an alert communicates to the rest of the team that a specific technician has taken ownership of the issue.

The formal definition of acknowledgment is that the issue is being worked on and the alert will not be escalated . This is the most important functional result of the action: it halts the automated escalation chain. If an alert was configured to email a manager after 30 minutes of inactivity, acknowledging the alert at the 15-minute mark cancels that pending manager email. It signals to the system—and other operators—that active troubleshooting is underway and further automated "noise" is unnecessary.

It is important to note that acknowledgment does not mean the issue is resolved (Option A); the alert remains active in the "All Active Alerts" list (though often filtered into an "Acknowledged" category) until the underlying trigger condition is cleared by the monitoring engine. It is a procedural tool for incident management, ensuring that once a human engages with a problem, the platform's automated notification logic steps aside to let them work without further distraction.

In the SolarWinds Platform, transferring report definitions between different instances (such as Site A and Site B) requires a format that captures the underlying logic, SQL/SWQL queries, and layout metadata. According to the SolarWinds Platform Reporting Guide , while CSV, PDF, and DOC are formats used for exporting the results of a report (the data), they do not contain the instructions needed to recreate the report itself on a different server.

To share a report's structure, the administrator must use the Export/Import XML functionality. By selecting the report in the Report Manager and choosing "Export," the system generates a specialized .xml file . This file contains the complete definition of the report, including the datasource filters, selected columns, chart configurations, and formatting rules. When this XML file is imported into the second SolarWinds instance, the platform parses the code and creates a new entry in the local database. This is the standard method for migrating custom reports from a test environment to production or sharing successful reporting templates across a geographically distributed organization with multiple independent polling installations.