Important SolarWinds Observability-Self-Hosted-Fundamentals Exam Questions

Answer: C

Explanation:

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 the SolarWinds Platform User Account Management guide, a Web Console Administrator can manage nodes, create alerts , build reports , and customize dashboards.

However, for security reasons, the ability to manage passwords---specifically the credentials used for polling (SNMP strings, WMI service accounts, or external integration secrets)---is often restricted. While an admin can assign an existing credential to a node, the ability to add, edit, or view the clear-text/obfuscated passwords within the centralized Credential Library is 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.

Answer: B, D

Explanation:

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.

Answer: A

Explanation:

AppStack relies on the relationship data collected by the Virtualization Manager (VMAN) and Server & Application Monitor (SAM) modules. For an ESX host and its virtual machines (VMs) to appear and be correctly mapped in the stack, the platform must be able to 'walk' the relationship from the hypervisor down to the guest OS.

The most common cause for missing virtualization data in AppStack is an incorrect polling method. To show the relationship between a physical host and its VMs, the node must be added to SolarWinds using the 'Poll for VMware' or 'Poll for Hyper-V' options. If the ESX host was added as a standard ICMP (Ping) or SNMP node without specifically enabling the virtualization polling credentials (linking it to the vCenter or the host's direct management API), the platform will see the host as a standalone server. Consequently, it will fail to discover the 'parent-child' relationship between the host and its virtual machines. Without this verified architectural link in the database, AppStack cannot 'build' the visual stack, leaving those entities out of the environment view.

Answer: A

Explanation:

The SolarWinds Platform provides distinct tools for visualizing different aspects of environmental health and performance. AppStack is primarily an entity-relationship mapping tool. According to the SolarWinds 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 which entities (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 the SolarWinds 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 showing what is connected, PerfStack excels at showing how specific metrics (CPU, Latency, IOPS) across those connected entities interact. Therefore, a combination is required where AppStack handles the entities and PerfStack handles the metrics. 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).

Answer: D

Explanation:

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.