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 theSolarWinds Platform Administrator Guide, to prevent this for a dedicated NOC account, the administrator mustdisable 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 tocreatethe 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.

TheMy Deploymentpage is the centralized administrative hub for managing the health and scale of the SolarWinds Platform. According to theSolarWinds 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 canviewlicense 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.

In the SolarWinds Platform, data visibility is controlled at the account level through a security feature known as Account Limitations. According to theSolarWinds Platform User Account Managementdocumentation, when a single user has restricted visibility while others do not, it points to a specificAccount Limitationapplied to that user's profile.

Account limitations act as a persistent filter on the database queries performed by the Web Console during that user's session. If an administrator has configured a limitation based on a custom property like "Location" or "Region," the user will only see entities that match that specific criteria. For example, if the user's account is limited to Location = New York, they will be unable to see nodes, alerts, or reports associated with Location = London, even if those nodes are active and being monitored by the system.

This is a fundamental tool for multi-tenant environments or large enterprises where different teams are responsible for different geographic or logical segments of the network. It is more effective than "View Limitations" (Option D) because an account limitation follows the user across the entire platform, including search results, alerts, and reports, whereas a view limitation only affects a specific dashboard page. Options B and C are unlikely because they would typically affect multiple users or indicate a major monitoring gap rather than a user-specific visibility issue.

The SolarWinds Alerting Engine provides a wide array of "Trigger Actions" that occur automatically when an alert's conditions are met. According to theSolarWinds 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 canschedulea report to be sent via email, the alerting engine itself does notgenerate a report(Option C) as a reactive trigger action to a node failure; reports are intended for historical analysis rather than immediate event response.

AlertStackis a specialized AIOps feature within Hybrid Cloud Observability (HCO) designed to simplify incident response. According to theSolarWinds HCO Alertingdocumentation, anAlertStack clusteris anautogenerated grouping of related active alerts on related entities.

The primary goal of clustering is to reduce "alert fatigue." Instead of presenting a technician with twenty individual alerts (e.g., one for high CPU on a server, one for an application failure, and three for slow database response), AlertStack analyzes the relationships and dependencies between those entities. If the platform determines that the alerts are part of a single root-cause event—such as a storage array failure impacting multiple virtual machines and their applications—it automatically clusters them into a single visual timeline. This clustering isautogeneratedby the platform's machine learning engine based on the AppStack dependency map; it does not require a user to manually group the alerts. This allows the IT team to identify the "blast radius" of an incident and focus on the primary failure point rather than triaging dozens of symptoms individually.

PerfStackis a cross-stack data correlation tool, but its visibility is constrained by the underlying data collection modules and user security settings. According to thePerfStack 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 theStorage 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 usesAccount Limitationsto 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.

AppStackis designed to provide a "top-to-bottom" visual representation of the IT infrastructure layers that support an application. According to theSolarWinds Platform Administrator Guide, the AppStack Environment view automatically maps relationships between specific monitored entities.

The two primary categories that appear in this view aredatabase instances (A)andservers (C). In a typical application stack, the "Server" represents the physical or virtual hardware, while the "Database Instance" (monitored via AppInsight for SQL, Oracle, etc.) represents the software layer running on that server. AppStack visually links these so that if a database instance shows a critical status, an administrator can instantly see which server it is hosted on and if there are underlying infrastructure issues. Other common categories include Applications, Transactions, Virtual Hosts, Clusters, and Volumes.

NetFlow(Option B) is a traffic analysis technology used in the NetFlow Traffic Analyzer (NTA) and is generally not a primary "entity" category in the standard AppStack environment map.SNMP Pollers(Option D) are the backend mechanisms used to collect data; they are a configuration component rather than a logical infrastructure entity that would be represented as a layer in an application dependency stack.