Updated PDF (New 2026) Actual SolarWinds Observability-Self-Hosted-Fundamentals Exam Questions
Verified Observability-Self-Hosted-Fundamentals Exam Dumps PDF [2026] Access using RealExamFree
NEW QUESTION # 10
Which two of the following settings can be included in an alert cluster? (Choose two.)
- A. metric values
- B. device status
- C. configuration
- D. audit events
Answer: A,D
Explanation:
AlertStackin Hybrid Cloud Observability (HCO) uses alert clusters to group related active alerts into a single actionable incident. According to theSolarWinds HCO Alertingdocumentation, these clusters are designed to provide context beyond the alert itself by correlating different types of data.
* Metric Values (D): Alert clusters include the specific performance data that triggered the alert, such as high CPU load percentages or interface latency values. This allows the administrator to see the "why" behind the incident immediately within the cluster view.
* Audit Events (A): To assist in root cause analysis, alert clusters can include relevant audit events. For example, if a node goes down immediately after a configuration change, the audit event showing who logged in and what they changed will be correlated within the cluster to provide a timeline of events leading to the alert.
While "device status" is often the result of an alert, the cluster is specifically built to aggregate the underlying metricsandevents(Audit/Events) to give a comprehensive picture of the environment's health.
NEW QUESTION # 11
Which function is provided by Platform Connect?
- A. intelligent mapping
- B. historical reporting
- C. infrastructure monitoring
- D. anomaly-based alerting
Answer: D
Explanation:
Platform Connectis 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 theSolarWinds HCO Administrator Guide, the primary function enabled by this connection isanomaly-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 Connectprovides 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.
NEW QUESTION # 12
Which two of the following account types are supported in SolarWinds Hybrid Cloud Observability (HCO)?
(Choose two.)
- A. Orion group
- B. Windows local domain
- C. Windows distribution AD
- D. Azure active directory (AD)
Answer: A,D
Explanation:
SolarWinds Hybrid Cloud Observability supports a variety of authentication methods to ensure seamless integration with enterprise identity providers. According to theSolarWinds Platform Installation and Upgrade Guide, the two primary modern account types used for centralized management areAzure Active Directory (AD)andOrion Groups.
* Azure Active Directory (AD): This allows organizations to leverage their cloud-based identity provider for Single Sign-On (SSO) and centralized user management. HCO integrates directly with Azure AD to authenticate users based on their existing cloud credentials.
* Orion Group: This is a local platform account type that allows administrators to define permissions at a group level rather than for individual users. By creating an Orion Group, you can assign a specific set of view, alert, and report permissions once, and any user assigned to that group automatically inherits those rights.
While "Windows Local Domain" (standard AD) is supported for on-premises deployments, the specific phrasing in HCO documentation emphasizes the shift toward cloud-native and group-based management.
"Windows distribution AD" is incorrect because SolarWinds requires security groups for permission mapping, not distribution groups.
NEW QUESTION # 13
What is the minimum supported version for SolarWinds Hybrid Cloud Observability (HCO) database server?
- A. MS SQL server 2016 service pack 1
- B. SQL server 2012 service pack 4
- C. MS SQL server 2019
- D. MS SQL server 2012 R2
Answer: C
Explanation:
The transition from the legacy Orion Platform toHybrid Cloud Observability (HCO)introduced stricter hardware and software prerequisites to support modern features like AIOps, advanced mapping, and high- performance data processing. According to theSolarWinds Hybrid Cloud Observability System Requirements, the platform requires modern SQL features for optimal performance.
While legacy versions of the Orion Platform may have supported SQL Server 2016 or even 2012 in older iterations,MS SQL Server 2019is identified as theminimum supported versionfor new HCO installations.
This requirement ensures compatibility with the latest database indexing and query optimization techniques used by the SolarWinds Platform to handle the high volume of time-series data generated by observability nodes. Additionally, using SQL 2019 or later (including SQL 2022) is necessary to ensure the platform can utilize specific security protocols and memory management improvements that are not available in the end-of- life SQL 2012 or SP1 versions of 2016.
NEW QUESTION # 14
Which two of the following platforms is supported by the agent software? (Choose two.)
- A. Fedora Linux
- B. Windows 11 Enterprise
- C. Windows Server 2022
- D. Debian 11
Answer: B,C
Explanation:
The SolarWinds Agent is a versatile polling tool, but it must be compatible with the underlying Operating System (OS) to function correctly. According to theSolarWinds Platform Agent requirements, the agent software is designed to run on a wide variety of modern Windows and Linux distributions.
For the Windows ecosystem, the agent supports both server-grade and enterprise-grade workstation operating systems.Windows Server 2022 (D)is fully supported, allowing for deep monitoring of the latest Microsoft server environments, including support for AppInsight applications. Similarly,Windows 11 Enterprise (C)is a supported platform, which is particularly useful for monitoring high-end workstations, jump boxes, or remote endpoints that act as critical nodes in the network.
While SolarWinds does support various Linux distributions (such as RHEL, CentOS, and Ubuntu),Debian 11 andFedora(Options A and B) are often not listed as "officially primary supported" in the same tier as the Windows or main enterprise Linux distributions in current HCO documentation. The Windows agent remains the most feature-complete version of the software, supporting a broader range of monitoring types (like Quality of Experience and deep application analysis) compared to its Linux counterparts. Therefore, for an HCO deployment focusing on the latest infrastructure, Windows Server 2022 and Windows 11 are the verified answers.
NEW QUESTION # 15
An alert is needed when the bandwidth utilization on a specific set of router interfaces exceeds 75%. The alert needs to be limited to specific devices and their interfaces. How is this task accomplished?
- A. Modify the scope on the trigger conditions to contain the desired nodes and interfaces.
- B. Modify the scope on the reset conditions to contain the desired nodes and interfaces.
- C. Use an account limitation to limit the alert to desired devices and interfaces.
- D. Create a critical status-based alert and change the interface utilization status.
Answer: A
Explanation:
The alerting engine in the SolarWinds Platform uses a "Scope" and "Condition" logic to determine when an action should fire. According to theSolarWinds Platform Alerting Guide, the "Scope" defineswhichobjects the alert engine should evaluate, while the "Condition" defineswhatperformance metric triggers the alert.
To limit an alert to a specific set of router interfaces, the administrator mustmodify the scope on the trigger conditions. In the Alert Wizard, under the "Trigger Condition" tab, there is a section titled "I want to alert on..." (Interface) and a secondary section for "The scope of the alert". By adding specific rules to this scope- such as Node Name is Router-A or Interface Alias contains WAN-the alert engine will ignore the thousands of other interfaces in the database and only monitor the 75% utilization threshold on those specific targets.
Using account limitations (Option D) is incorrect for this purpose, as account limitations affect what auser sees in the console, not how the backendalerting engineprocesses data.
NEW QUESTION # 16
User access is being modified by adding Windows groups and setting group permissions. Two users are in multiple groups with different permissions. The correct permissions need to be applied to the users involved in multiple groups. Which two of the following actions will accomplish this goal? (Choose two.)
- A. add users as individual users and configure permissions
- B. re-order groups to apply correct permissions in order
- C. remove impacted groups and add all users individually
- D. remove users' accounts and create individual accounts
Answer: A,B
Explanation:
Managing user permissions through Active Directory (AD) groups in SolarWinds requires an understanding of how the platform resolves conflicting rights. When a user belongs to multiple groups, the platform must determine which set of permissions takes precedence. According to theSolarWinds Platform User Account Managementguide, there are two primary ways to ensure the "correct" (often the most restrictive or most specific) permissions are applied.
* Add users as individual users (A): Individual user account settings always take precedence over group settings in the SolarWinds Platform. If a user needs specific rights that differ from their assigned AD groups, creating a local or AD-linked individual account for them allows the administrator to "override" group-level permissions with 100% certainty.
* Re-order groups (D): The SolarWinds Web Console allows administrators to change thesearch order of groups. When a user logs in, the platform checks the groups in the order they are listed in the
"Manage Accounts" screen. The first group match it finds is the one that defines the user's session permissions. By re-ordering the groups, an admin can ensure that the group with the "correct" intended permissions is processed first.
Options B and C are inefficient and unnecessary "nuclear" options that disrupt the benefits of using centralized AD management for the rest of the organization.
NEW QUESTION # 17
Which type of modern dashboard widget is represented?
- A. KPI
- B. counter
- C. table
- D. custom HTML
Answer: A
Explanation:
According to theSolarWinds Platform Administrator GuideregardingModern Dashboards, the platform introduces several new widget types designed for high-performance data visualization. The widget shown in the image, which displays a single, large numerical value (the number "1") representing a specific count of
"DOWN Nodes" against a distinct colored background, is officially categorized as aKPI (Key Performance Indicator)widget.
KPI widgets are specifically engineered to provide an immediate "at-a-glance" understanding of critical metrics. Unlike the legacy "Classic" dashboards which relied on multi-row tables or fixed gauges, the Modern Dashboard KPI widget allows for a highly streamlined presentation of data derived fromSWQL (SolarWinds Query Language). In this instance, the widget is likely running a query such as SELECT count(NodeID) FROM Orion.Nodes WHERE Status = 2, which returns a single scalar value. This value is then rendered prominently in the center of the widget.
One of the defining features of the KPI widget in HCO is its ability to useConditional Formatting. This allows the background color of the widget to change dynamically based on the value returned by the query; for example, the background may turn red if the count of down nodes is greater than zero, providing a visual alert to the NOC staff. This type of widget is distinct from a "table" (D), which displays multiple rows of data, or a "counter" (A), which is typically a legacy term for simple incremental statistics. It is also not a "custom HTML" (B) widget, as those are used for embedding external content or custom code rather than native data point visualization. The KPI widget remains the primary tool for displaying high-level summary statistics, such as active alert counts, total interface errors, or, as seen here, the availability status of nodes across the environment.
NEW QUESTION # 18
Agents have been deployed to a Windows server on a network. The agent is to initiate communication with the application server for all agents. Which firewall port needs to be opened?
- A. TCP 445
- B. TCP 17778
- C. TCP 17790
- D. TCP 17777
Answer: B
Explanation:
SolarWinds agents support two communication modes: "Server-Initiated" (Passive) and "Agent-Initiated" (Active). According to theSolarWinds Platform Agent requirements and port information, the direction of communication determines which firewall ports must be open.
When an agent is configured forAgent-Initiated communication(where the agent on the managed node reaches out to the SolarWinds server), it usesTCP port 17778. This port must be open for inbound traffic on the SolarWinds Main Polling Engine or Additional Polling Engine. This mode is highly beneficial for monitoring servers in DMZs or remote sites where the SolarWinds server cannot initiate a connection through the firewall, but the remote node is allowed to communicate back to the primary management network. Port
17777 (Option B) is used for the legacy Orion Information Service, and 17790 (Option D) is used for specific client-to-server messaging in different contexts, but 17778 is the dedicated, encrypted port for agent-initiated data transmission.
NEW QUESTION # 19
What is the effect of checking the Encrypt connections with SSL box in the configuration wizard?
- A. The login account to access the SQL server will be encrypted and stored in SolarWinds' Hybrid Cloud Observability Platform server.
- B. The login credentials will be encrypted between SolarWinds' Hybrid Cloud Observability Platform server and the SQL server while in transit.
- C. The installed SolarWinds product will use the login account to access the databases on the SQL server.
- D. The network data between SolarWinds' Hybrid Cloud Observability Platform server and the SQL server will be encrypted.
Answer: D
Explanation:
According to theSolarWinds Platformconfiguration documentation, the option toEncrypt connections with SSLduring the database configuration wizard specifically dictates the security level of the communication channel between the application server and the database backend. When this box is checked, the platform ensures thatthe network data between SolarWinds' Hybrid Cloud Observability Platform server and the SQL server will be encrypted. This security measure is critical for protecting the integrity and confidentiality of the performance metrics, configuration data, and credentials as they traverse the internal network between these two primary architectural components.
This encryption utilizesTransport Layer Security (TLS)to wrap theTDS (Tabular Data Stream)protocol used by Microsoft SQL Server. By enabling this feature, the platform prevents potential "man-in-the-middle" attacks where an adversary could sniff network traffic to intercept sensitive monitoring data or administrative information stored within the SQL database. It is important to note that for this setting to function correctly, theSQL Servermust be configured with a valid SSL/TLS certificate that is trusted by the SolarWinds application server.
This setting differs from simple credential encryption (Option C) or secure storage (Option B) because it applies toall datatransmitted during the session, not just the initial login exchange. Furthermore, while the configuration wizard does require a login account (Option A), that account's specific permissions are a separate functional requirement from the underlying encryption of the transport layer. Enabling SSL encryption is a standard best practice for organizations following strict compliance frameworks likeHIPAA, PCI-DSS, orSOC2, where protecting data-in-transit is a mandatory requirement even on internal, "trusted" network segments. This centralized encryption toggle simplifies the deployment of high-security observability environments by orchestrating the secure connection parameters through the standard SolarWinds Configuration Wizard interface.
NEW QUESTION # 20
Platform administrators are to be given access to view all reports created and used in SolarWinds Hybrid Cloud Observability (HCO), regardless of who created them or their permission settings. Which report limitation setting should be used?
- A. no limitation
- B. new limitation
- C. no reports
- D. default
Answer: A
Explanation:
In Hybrid Cloud Observability (HCO), report visibility is controlled byReport Limitation Categories. While standard users are typically restricted to specific categories (e.g., "Finance Reports" or "Network Reports"), administrators often require a global view of all reporting assets.
According to theSolarWinds Platform Documentation on Restricting Report Access, the setting"No Limitation"is the specific value used to bypass all category-based filters. When an account is configured with the "No Limitation" report category, the platform security layer allows that user to see every report stored in the database, including reports marked as "private" or those assigned to specific siloed departments.
It is important to distinguish this from the"Default"setting (Option A), which typically only allows users to see reports that have not been assigned to any specific limitation category. To ensure a Platform Administrator has a truly comprehensive view for auditing or management purposes, the "No Limitation" setting must be explicitly selected in their User Account settings underSettings > All Settings > Manage Accounts > Edit User.
NEW QUESTION # 21
Which statement defines the meaning of acknowledging an alert?
- A. The issue that triggered the alert has been resolved.
- B. The issue that triggered the alert is being worked on and will not be escalated.
- C. The issue that triggered the alert is being worked on and will be escalated.
- D. The issue that triggered the alert is being worked on.
Answer: B
Explanation:
In the SolarWinds alerting workflow, "Acknowledgment" is a critical state change that coordinates the human response to an incident. According to theSolarWinds 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 thatthe 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 acknowledgmentdoes notmean 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.
NEW QUESTION # 22
Which two of the following settings are automatically enabled for a user with the default set of user permissions in SolarWinds' Hybrid Cloud Observability (HCO)? (Choose two.)
- A. view all existing reports
- B. disable session time out
- C. view all active alerts
- D. self-manage dashboards
Answer: A,C
Explanation:
When a new user account is created in the SolarWinds Platform, it is assigned a set of "Default" permissions designed to provide a "Read-Only" baseline of visibility. According to theSolarWinds Platform User Account Managementguide, the platform is configured to ensure that new users can immediately benefit from the monitoring data without having the power to accidentally modify the environment.
Specifically,view all active alerts (C)andview all existing reports (D)are enabled by default. This ensures that any team member with a login can see the current health of the infrastructure and access historical performance data. These are considered "Passive" rights that allow for operational awareness. Conversely, disable session time out (A)is a security-sensitive setting that is typically disabled by default to prevent abandoned sessions from remaining active on public or shared workstations.Self-manage dashboards (B), while a common feature, often requires explicit "Dashboards" or "View" management permissions to be toggled on by an administrator to prevent a proliferation of unmanaged or redundant dashboard pages within the database. By defaulting to alert and report visibility, SolarWinds follows the principle of providing immediate information for troubleshooting while reserving management and security-override functions for designated administrators.
NEW QUESTION # 23
What is the result of a monitored node being deleted?
- A. node will be removed and associated objects will remain unless explicitly deleted
- B. node and associated objects will be immediately removed
- C. neither the node nor the associated objects will be removed
- D. node and associated objects will be removed during next database maintenance cycle
Answer: B
Explanation:
In the SolarWinds Platform, the "Node" acts as the primary parent object for all other monitored elements related to that IP address or hostname. According to theSolarWinds Platform Node Managementguide, the deletion process follows a strict parent-child relationship hierarchy.
When an administrator selects a node and chooses to delete it, thenode and all its associated objects are immediately removed (B)from the active monitoring database. Associated objects include interfaces, volumes, hardware health sensors, and application monitors (such as those assigned via SAM). This is an irreversible action. Unlike "Unmanaging" or "Muting," which keep the node record intact, "Delete" purges the entity and its historical data pointers from the current view.
It is important to understand that while the records are removed from the web console immediately, the actual data rows in the SQL database may be marked for deletion and cleared during the next scheduled "Database Maintenance" (Option C). However, from the perspective of the user and the monitoring engine, theresultis immediate: the node stops being polled, its alerts are cancelled, and it no longer appears in any dashboards or reports. The platform does not allow "orphaned" objects; you cannot have a monitored interface in the database if its parent node has been deleted (Option D).
NEW QUESTION # 24
From which two of the following locations can CPU load be excluded from contributing to overall node status? (Choose two.)
- A. node child status
- B. mute node
- C. all nodes widget
- D. edit node properties
Answer: A,D
Explanation:
By default, the "overall status" of a node (Up, Warning, Critical) is calculated based on its availability and the health of its child components, such as CPU and Memory. According to theSolarWinds Platform Node Managementdocumentation, administrators can fine-tune this rollup behavior to prevent non-critical metrics from turning a node "red" on the dashboard.
* Edit Node Properties (B): Inside the "Edit Node" page, there is a section for "Thresholds." Here, an administrator can uncheck the box that allows CPU load to contribute to the node's overall status. This is useful for servers that consistently run high CPU but are otherwise healthy.
* Node Child Status (D): Within the global SolarWinds settings, administrators can manage "Node Child Status Participation." This centralized menu allows you to define which sub-elements (CPU, Memory, Interfaces, etc.) are allowed to influence the parent node's status.
Muting a node(Option C) only pauses alerts and does not change how status is calculated. TheAll Nodes widget(Option A) is a visualization tool and does not provide the configuration settings to change the underlying status logic.
NEW QUESTION # 25
A network discovery job was performed. The job was not correctly defined and not all devices were discovered within the network. What is the likely reason for the skipped devices?
- A. The preferred polling method in the discovery job was set to WML
- B. The network discovery timeout was too short
- C. The missing devices were included in the discovery ignore list.
- D. The missing devices were configured for SNPMvS.
Answer: C
Explanation:
Network Discovery is an automated process to scan subnets and import new infrastructure. However, the discovery engine includes logic to prevent duplicate entries and ignore non-relevant assets. According to the SolarWinds Platform Administrator Guide, if specific devices are missing from the results, the most common administrative cause is theDiscovery Ignore List.
The "Ignore List" is a database of IP addresses or MAC addresses that the platform has been explicitly told to skip. This often happens if a device was previously discovered but the administrator chose "Ignore this node" during the import phase. The system remembers this choice to prevent the device from reappearing in every subsequent scan. Additionally, the platform automatically ignores any node that isalready presentin the
"Manage Nodes" list to avoid creating redundant monitoring objects.
While a timeout (Option C) or incorrect polling method (Option D) could cause a node to fail to respond with its full metadata, the device would typically still appear in the discovery results as a "Generic" or "ICMP- only" device rather than being skipped entirely. Only theIgnore Listor pre-existing status causes a device to be excluded from the discovery results table during a scan of a valid subnet.
NEW QUESTION # 26
A group has been created to monitor a set of nodes. When additional nodes are added for monitoring, how can they be automatically placed in the group?
- A. create a custom property and add the nodes manually to a group
- B. create a custom property and add nodes to a static group
- C. create a custom property and use an alert to add them
- D. create a custom property and dynamic query to add them to a group
Answer: D
Explanation:
Automation is a cornerstone of efficient node management in the SolarWinds Platform. To avoid the manual labor of updating groups every time a new device is commissioned, the platform utilizesDynamic Queries.
According to theSolarWinds Platform Administrator Guide, the best-practice workflow for automated grouping involves two steps.
First, an administrator shouldcreate a custom property(e.g., City or ApplicationName). When new nodes are added via the "Add Node" wizard or Network Discovery, they are tagged with a specific value for that property. Second, the group's membership is defined by adynamic queryrather than a static list. For example, a group could be configured with a rule that states: "Add any node where City is equal to London".
Once this is configured, the platform's backend services periodically scan for any new nodes that match the criteria. As soon as a new server is added and its custom property is set, it isautomaticallyadded to the group without any further human intervention. This ensures that dashboards, alerts, and reports that rely on that group always reflect the current state of the infrastructure. Option D is incorrect because while alerts can trigger actions, they are not the standard architectural mechanism for group membership management.
NEW QUESTION # 27
What is supported when importing custom property values to SolarWinds* Hybrid Cloud Observability (HCO)?
- A. incoming values can contain special characters
- B. importing values from .json file format
- C. importing complex .xls or .xlsx files
- D. incoming values validated before being written
Answer: D
Explanation:
The Custom Property Import tool is designed to help administrators bulk-update metadata for hundreds or thousands of nodes simultaneously. According to theSolarWinds Platform Administrator Guide, maintaining data integrity is a priority during this process.
A critical feature supported during the import is thatincoming values are validated before being written (D)
. When an administrator uploads a CSV or Excel file containing custom property values, the platform performs a validation check against the defined "Type" of each property in the database. For example, if a custom property InstallDate is defined as a "Date" type, and the import file contains a text string like "Last Tuesday," the validation engine will flag an error and prevent the import from corrupting the database. This validation also checks for character limits and ensures that values for restricted "Drop-down" properties match the predefined allowed list. This safeguard is essential for ensuring that automated alerts and reports, which rely on this metadata, function correctly without being disrupted by malformed data entries.
NEW QUESTION # 28
Which two of the following permissions are default settings for users added to SolarWinds* Hybrid Cloud Observability (HCO)? (Choose two.)
- A. edit views
- B. view existing reports
- C. log into web console
- D. manage reports
Answer: B,C
Explanation:
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 the SolarWinds 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.
NEW QUESTION # 29
Which statement regarding SolarWinds* Hybrid Cloud Observability (HCO) groups is accurate?
- A. group status rollup mode options do not apply to all members
- B. group status rollup mode is set to "show best status" by default
- C. groups cannot be a member of another group
- D. groups can be created based on custom properties
Answer: D
Explanation:
Groups in the SolarWinds Platform are logical containers used to organize monitored entities for easier management, alerting, and reporting. According to theSolarWinds Platform Administrator Guide, one of the most powerful features of the grouping engine is the ability to automate membership. Specifically,groups can be created based on custom properties.
When defining a group, administrators can choose between "Static Selection" (manual) or "Dynamic Query." By using dynamic queries, a group can be configured to automatically include any node, interface, or volume that matches specific criteria, such as a custom property value (e.g., Department = Engineering or Site = London). This ensures that as new infrastructure is added to the environment and tagged with the appropriate metadata, the groups update themselves without human intervention.
Regarding the other options: groupscanbe members of other groups (nested groups), which is a common practice for creating complex hierarchical views of an organization. The default status rollup mode is typically set to "Mixed" or "Show Worst Status" rather than "Best Status," to ensure that any single failure within the group is visible to the administrator. Finally, rollup options absolutely apply to all members within the group, as they define how the collective health of those members is calculated and displayed on the dashboard.
NEW QUESTION # 30
Which two of the following statements apply to predefined alerts on SolarWinds Hybrid Cloud Observability (HCO)? (Choose two.)
- A. predefined alerts with send an e-mail action require default recipients to be configured in default send email action
- B. trigger and reset actions of predefined alerts cannot be directly edited
- C. predefined alerts with send an e-mail action will forward notifications to the product registration email as a default
- D. trigger and reset conditions of predefined alerts cannot be directly edited
Answer: A,D
Explanation:
Predefined alerts(out-of-the-box alerts) come built into Hybrid Cloud Observability to provide immediate value. According to theSolarWinds Platform Alerting Guide, these alerts have specific behaviors regarding modification.
* Default Email Recipients (A): Many predefined alerts include a "Send an Email" action by default.
However, for these to work, an administrator must first configure the global SMTP settings and ensure that "Default Recipients" are defined, or the alert will have no destination for its notifications.
* Conditions cannot be directly edited (D): To protect the integrity of the built-in logic, the platform often prevents users from directly overwriting thetrigger and reset conditionsof a predefined alert.
Instead, the recommended workflow is to "Duplicate and Edit," allowing the user to create a customizable copy of the alert while keeping the original out-of-the-box version intact for reference.
Option B is incorrect as SolarWinds does not automatically use the registration email for monitoring notifications. Option C is generally incorrect because while conditions are often locked, administrators are usually allowed to add or modifyactions(like adding a specific email address) to a predefined alert to make it functional for their specific environment.
NEW QUESTION # 31
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?
- A. set node to inherit CPU thresholds and alert to fire when threshold is met
- B. change polling interval to match length of time for an alert to fire
- C. change polling method on the server from WMI to agent polling
- D. set node to change CPU status if threshold is met for multiple polling cycles
Answer: D
Explanation:
To prevent "alert noise" caused by temporary performance spikes, the SolarWinds Platform allows for threshold persistence. According to theSolarWinds 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 onlysustainedhigh utilization triggers an action is toset 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.
NEW QUESTION # 32
What two of the following reasons apply to creating custom views in SolarWinds' web console? (Choose two.)
- A. limit user access to specific elements
- B. personalize user experience and focus on specific elements
- C. perform customizations with SQL queries
- D. monitor devices and elements not shown in default views
Answer: A,B
Explanation:
Custom Views(Summary Views and Detail Views) are the primary way administrators control the layout and focus of the SolarWinds Web Console. According to theSolarWinds Platform Administrator Guide, views are used to tailor the platform to different user roles.
The two primary reasons for creating them are:
* Limit user access to specific elements (A): Views can be restricted to specific users or groups. By creating a custom view that only contains "Storage" widgets and assigning it to the Storage Team, an administrator can effectively limit what those users see when they log in. This prevents users from being overwhelmed by irrelevant data and acts as a functional layer of access control.
* Personalize user experience and focus on specific elements (D): Different roles require different data. A CXO might need a high-level "Map" and "SLA Trend" view, while a technician needs a "Top
10 Nodes by CPU" and "Active Alerts" view. Custom views allow the administrator to curate exactly which widgets are visible, ensuring that each user has the most relevant information for their job front- and-center.
SQL customizations(Option C) are a method of building widgets, but not thereasonfor the view itself.
Monitoring new elements (Option B) is handled through theAdd NodeandPollerssettings; a view onlydisplays what is already being monitored.
NEW QUESTION # 33
Which two of the following settings can be configured while adding a single node for monitoring within
"manage nodes"? (Choose two.)
- A. create custom properties
- B. configure rediscovery interval
- C. add device studio pollers
- D. select statistics and resources
Answer: A,D
Explanation:
The "Add Node" wizard in the SolarWinds Platform is a multi-step process designed to fully integrate a new device into the monitoring ecosystem. According to theSolarWinds Platform Node Management documentation, once the IP address and credentials (SNMP/WMI) are verified, the administrator is presented with several configuration panels.
* Select Statistics and Resources (D): This is the critical step where the admin chooseswhatto monitor on the node. This includes selecting specific interfaces, volumes, or hardware health sensors. It also allows for the selection of the polling frequency for "Statistics" (how often to collect performance data) and "Status" (how often to check if the node is up).
* Create/Assign Custom Properties (C): During the "Add Node" process, there is a dedicated tab for metadata. Here, the admin can fill in values for existing custom properties (such as Site, Owner, or Asset Tag). If a property does not exist, the wizard often provides a shortcut to the Custom Property manager tocreateor modify the fields so that the node is correctly categorized from the moment it is added to the database.
Device Studio Pollers(Option A) are typically assignedaftera node is added if the default pollers are insufficient.Rediscovery Interval(Option B) is a global setting or found deep in the advanced node properties, rather than a primary configuration step in the standard "Add Node" wizard.
NEW QUESTION # 34
......
Try Best Observability-Self-Hosted-Fundamentals Exam Questions from Training Expert RealExamFree: https://www.realexamfree.com/Observability-Self-Hosted-Fundamentals-real-exam-dumps.html
Practice Examples and Dumps & Tips for 2026 Latest Observability-Self-Hosted-Fundamentals Valid Tests Dumps: https://drive.google.com/open?id=19K5YDCjq6bMkrqk7J_HATWM9BQYbvKhg
