Pass the SolarWinds Certified Professional Observability-Self-Hosted-Fundamentals Questions and answers with ExamsMirror

Visibility of the reporting module is a configurable security setting within each SolarWinds user account. According to theSolarWinds Platform User Account Managementguide, if a user logs into the Web Console and finds the Reports section empty or inaccessible, it is likely due to anAccount Limitation.

Specifically, the "Report Limitation" field in the user's profile can be set to"No Reports". This setting acts as a total block, preventing the user from viewing any report definitions, whether they are predefined (out-of-the-box) or custom-made. This is a common configuration for restricted user roles, such as basic operators or external contractors, who need to see real-time status in dashboards but should not have access to the historical, inventory, or security data contained in the platform's reporting engine. While a user could also be restricted from seeing specific entities (Option B), this would typically just result in empty datainsidea report rather than the total inability to view the reports module itself. Setting the account to "No Reports" ensures the user isprevented from viewing all reportsglobally across the platform.

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 Platform provides distinct tools for visualizing different aspects of environmental health and performance.AppStackis primarily an entity-relationship mapping tool. According to theSolarWinds SAM Administrator Guide, "The AppStack Environment view provides a powerful layer of troubleshooting visibility by exposing all participating objects in your environment, as well as their relationships to one another". It allows administrators to customize whichentities(nodes, applications, volumes, etc.) are visible and how they are grouped to show dependencies.

Conversely,PerfStack(Performance Analysis) is the engine used for metric correlation. As stated in theSolarWinds Platform Administrator Guide, PerfStack allows users to "drag and drop performance metrics from multiple entities onto a single chart to correlate data over time". While AppStack excels at showingwhatis connected, PerfStack excels at showinghowspecific metrics (CPU, Latency, IOPS) across those connected entities interact. Therefore, a combination is required where AppStack handles theentitiesand PerfStack handles themetrics. Specifically, you use AppStack to identify the scope of entities involved in a performance bottleneck and then transition those entities into a PerfStack project to perform a deep-dive analysis of the metrics. This modular approach ensures that troubleshooting is both contextually aware (via AppStack) and data-driven (via PerfStack).

In the SolarWinds Platform, the method used to poll a node (SNMP, WMI, or Agent) is a specific property assigned to the node record in the database. According to theSolarWinds Platform Agent Managementguide, simply installing the agent software on a remote server does not automatically convert the existing node record to use that agent for data collection.

If a node was originally added to the system viaWMI, the platform will continue to attempt to poll it via WMI over the network using RPC/DCOM, even if the SolarWinds Agent is successfully installed and running on the target machine. To fix this "irregularity" and take advantage of the agent's encrypted, single-port communication, an administrator mustedit the node and change the polling method (D).

By going toManage Nodes, selecting the domain controller, and clicking "Edit Properties," the admin must find the "Polling Method" section and select "Agent". Once saved, the Polling Engine will stop using WMI network calls and will instead wait for the agent to provide the data (if in Agent-Initiated mode) or reach out to the agent via the agent's port (if in Server-Initiated mode). This change ensures that the monitoring load is shifted to the agent and that the communication adheres to the desired security profile.

The ability to create or modify reports is a high-level administrative function in the SolarWinds Platform, distinct from the ability to simply view them. According to theSolarWinds Platform User Account Managementguide, this is controlled by theReport Managementright.

To restrict a specific group of users from creating or editing reports while still allowing them to view existing ones, the administrator mustremove the "Manage Reports" permissionfrom their user accounts. When this right is set to "No," the"Manage Reports" buttonis hidden from the "All Reports" view for that user. They can still click on and run any report they have access to, but they will lack the interface options to enter the "Report Builder," change schedules, or delete entries. This provides a secure way to delegate report consumption to the wider team while centralizing report creation within a smaller group of "power users" or administrators. Option D is incorrect as it refers toAlerts, which is a separate permission set entirely.

In the SolarWinds Platform, "Administrator" rights in the Web Console grant extensive control over monitoring configurations, but they are distinct from "System Administrator" or "Security Administrator" roles. According to theSolarWinds Platform User Account Managementguide, a Web Console Administrator can manage nodes, create alerts , build reports , and customize dashboards.

However, for security reasons, the ability to managepasswords—specifically the credentials used for polling (SNMP strings, WMI service accounts, or external integration secrets)—is often restricted. While an admin canassignan existing credential to a node, the ability to add, edit, or view the clear-text/obfuscated passwords within the centralizedCredential Libraryis a separate, higher-level security permission. This prevents a standard Web Administrator from potentially harvesting sensitive service account passwords from the database. This "separation of duties" ensures that while a user can manage the monitoring environment, they cannot necessarily compromise the security of the underlying infrastructure accounts.

When new users are added to the SolarWinds Platform, they are typically granted a "Standard User" baseline of permissions to ensure they have immediate visibility without administrative risk. According to theSolarWinds Platform User Account Managementguides, the two primary default rights arelog into web console (B)andview existing reports (D).

The ability to log into the web console is the fundamental prerequisite for any user interaction with the platform. Once logged in, the "View Existing Reports" permission allows the user to navigate the report manager, search for historical data, and run or export reports that have been shared with them. These permissions are considered "safe" or "read-only" baseline rights. In contrast,Edit Views (A)andManage Reports (C)are administrative-level permissions that are disabled by default. "Edit Views" allows a user to change the dashboard layout for everyone, and "Manage Reports" allows for the creation, deletion, and scheduling of reports. By restricting these to an "opt-in" basis, SolarWinds protects the integrity of the monitoring configuration while ensuring that every team member can access the information they need to perform their daily duties.

SolarWinds provides several ways to handle maintenance windows, but they have different impacts on historical data. According to theSolarWinds Platform Administrator Guide, "Unmanaging" a node (Option D) stops all polling entirely, resulting in "gaps" in your historical charts.

To prevent notifications whilepreserving data collection, the best practice is toMute the devices during maintenance. When a device is "Muted" (also known as "Pause Actions"), the platform continues to poll the device and record its status and performance metrics (CPU, Memory, Latency) into the database. However, the alerting engine is instructed to suppress any notification actions (emails, scripts, etc.) for that specific entity. This ensures that you have a full historical record of the device's behavior during the maintenance period—showing exactly when it went down and came back up—without flooding the IT team with unnecessary alerts.

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.

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 theSolarWinds HCO Alerting Enginedocumentation, the primary mechanism for a human operator to pause this automated progression isacknowledgement.

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 doesnotclear the alert or stop the "Reset Conditions" from being monitored. If the node stays down, the alert remains active, but no furthernewescalation emails will be sent. The alert will only truly disappear once the environment returns to a healthy state and the reset conditions are met.