Pass Your Next Observability-Self-Hosted-Fundamentals Certification Exam Easily & Hassle Free
Free SolarWinds Observability-Self-Hosted-Fundamentals Exam Question Practice Exams
NEW QUESTION # 18
A company has two SolarWinds* Hybrid Cloud Observability (HCO) servers, running in two different sites.
An employee at the second site has designed a report that the first site wants to use. How can the report be shared between the sites?
- A. export the report as an XML from the second site and import it to the first site
- B. export the report as a DOC from the second site and import it to the first site
- C. export the report as a CSV from the second site and import it to the first site
- D. export the report as a PDF from the second site and import it to the first site
Answer: A
Explanation:
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 theSolarWinds Platform Reporting Guide, while CSV, PDF, and DOC are formats used for exporting theresultsof 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 theExport/Import XMLfunctionality. 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.
NEW QUESTION # 19
What is the effect of checking the Encrypt connections with SSL box in the configuration wizard?
- A. The network data between SolarWinds' Hybrid Cloud Observability Platform server and the SQL server will be encrypted.
- B. The login account to access the SQL server will be encrypted and stored in SolarWinds' Hybrid Cloud Observability Platform server.
- C. The login credentials will be encrypted between SolarWinds' Hybrid Cloud Observability Platform server and the SQL server while in transit.
- D. The installed SolarWinds product will use the login account to access the databases on the SQL server.
Answer: A
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
What indicates an alert cluster has been eliminated (i.e., end conditions have been met)?
- A. resolved
- B. closed
- C. auto-closed
- D. completed
Answer: C
Explanation:
In Hybrid Cloud Observability (HCO), specifically within theAlertStackfeature, related alerts are grouped into clusters to reduce "alert fatigue" and provide a unified view of an incident. According to theSolarWinds HCO Alerting Guide, an alert cluster transitions through several states based on the status of the underlying trigger conditions.
When the primary issues that triggered the alerts within the cluster are addressed and the "Reset Conditions" for those alerts are satisfied, the cluster is automatically managed by the system. The term used to define a cluster that has met its end conditions isauto-closed. Unlike manual "acknowledgment" or "resolution," which are user-driven actions, "auto-closed" signifies that the platform's monitoring engine has verified the environment has returned to a healthy state and the cluster no longer requires active monitoring or intervention. This automated lifecycle management is central to the AIOps and machine-learning capabilities of the platform, ensuring that the dashboard only reflects currently active, actionable incidents rather than historical events that have already been naturally corrected.
NEW QUESTION # 21
From which two of the following locations can CPU load be excluded from contributing to overall node status? (Choose two.)
- A. all nodes widget
- B. node child status
- C. mute node
- D. edit node properties
Answer: B,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 # 22
Which two of the following settings are present in modern dashboards and not classic dashboards? (Choose two.)
- A. define what is visible in widgets using SWQL
- B. apply account limitations
- C. configure network operations center (NOC) mode
- D. configure refresh rates
Answer: A,D
Explanation:
Modern Dashboardsrepresent a significant evolution over the legacy "Classic" summary views in the SolarWinds Platform. According to theSolarWinds Platform Administrator Guide, there are several architectural differences designed to improve performance and flexibility.
* Define visible data using SWQL (D): Unlike classic dashboards that rely on a fixed "Data Selection" wizard or pre-built resources, modern dashboards allow administrators tohand-edit SWQL (SolarWinds Query Language) queriesdirectly within the widget configuration. This provides near- infinite flexibility to filter and display data in ways that were previously impossible without custom coding.
* Configure refresh rates (C): Classic dashboards typically rely on the global web console refresh interval (often 5 minutes) or a full page reload. Modern dashboards introduce the ability toset individual refresh intervalsfor each widget (from 1 second to 24 hours), or configure a "Modern Widget Refresh" default for the entire dashboard. This ensures that critical real-time data is updated more frequently than static inventory data on the same page.
While "NOC mode" (Option B) and "Account Limitations" (Option A) are compatible with the broader SolarWinds environment, they are standard platform features that have existed in classic views for years and are not "unique" new settings specific only to the modern dashboarding engine.
NEW QUESTION # 23
Which two of the following export formats are supported in Hybrid Cloud Observability (HCO) reports?
(Choose two.)
- A. txt
- B. JSON
- C. PDF
- D. excel
Answer: C,D
Explanation:
SolarWinds Hybrid Cloud Observability provides robust reporting capabilities designed for both technical analysis and executive presentation. TheSolarWinds Platform Reporting Guidespecifies that reports generated through the Web Console can be delivered or manually exported in several standardized formats.
* Excel (.xls/.xlsx): This format is primarily used for data-heavy reports where administrators need to perform further calculations, sorting, or external data manipulation. It allows the raw table data from the report to be easily ingested into other business intelligence tools.
* PDF: This is the standard format for automated delivery and "executive-ready" documentation. It preserves the visual layout, including charts, logos, and specific formatting defined in the report builder.
While the platform usesJSON(Option B) for internal API communications and some dashboard configurations, andtxt(Option D) might be used for certain log exports, they are not standard selectable
"export formats" within the primary Web-Based Report builder for end-user consumption. The primary focus of the reporting engine is providing human-readable (PDF) and spreadsheet-compatible (Excel) outputs.
NEW QUESTION # 24
Which two of the following configurations are available as content for web-based reports? (Choose two.)
- A. existing intelligent maps
- B. existing PerfStack projects
- C. existing widgets
- D. existing diagrams
Answer: A,C
Explanation:
The modern web-based report builder in SolarWinds is highly integrated with the rest of the platform's visualization tools. According to theSolarWinds Platform Reporting Guide, reports are no longer limited to simple data tables; they can incorporate rich, interactive content already created elsewhere in the console.
Two key configurations available as content areexisting intelligent maps (A)andexisting widgets (D).
* Existing Intelligent Maps: This allows an administrator to take a visually mapped dependency or network topology and embed it directly into a scheduled report. This provides a geographical or logical context to the data that static tables cannot provide.
* Existing Widgets: Most widgets (resources) found on Summary or Node Details pages-such as "Top
10 Nodes by Response Time" or "Active Alerts"-can be added to a report as a component. This ensures consistency between what users see in real-time on their dashboards and what they receive in their weekly PDF summaries.
While you can embed performance data, the report builder is designed to consume these pre-configured UI elements (Maps and Widgets) to simplify report creation and maintain a unified look and feel across the observability suite.
NEW QUESTION # 25
Which two of the following statements apply to SolarWinds Hybrid Cloud Observability (HCO) Platform?
(Choose two.)
- A. provides AIOps and machine learning technology
- B. can operate without an internet connection
- C. requires SolarWinds hybrid cloud observability
- D. can be deployed on-premises or in the cloud
Answer: B,D
Explanation:
The SolarWinds Hybrid Cloud Observability (HCO) Platform is designed for maximum deployment flexibility to accommodate diverse enterprise security and infrastructure requirements. According to the SolarWinds Platform Installation and Upgrade Guide, the platform's architecture is fundamentally self- contained.
* Operation without an internet connection (A): This is a critical requirement for many government, military, and high-security financial environments. The platform is capable of "air-gapped" operation, where all polling, data processing, and visualization occur within a private network. While features like
"Platform Connect" (for cloud-based AI) may require a connection, the core monitoring, alerting, and reporting functions remain fully operational without any external internet access.
* Deployment on-premises or in the cloud (B): HCO is truly hybrid. It can be installed on physical hardware or virtual machines within a local data center, or it can be deployed within a Virtual Private Cloud (VPC) on platforms like AWS or Azure. This allows organizations to maintain their monitoring infrastructure alongside their managed assets, regardless of where those assets reside.
While HCOprovidesAIOps and machine learning (Option C), this is a feature of specific licensing tiers and configuration states rather than a fundamental "platform" characteristic that defines its deployment capability in the same way its offline and hybrid nature does.
NEW QUESTION # 26
Which two of the following account types are supported in SolarWinds Hybrid Cloud Observability (HCO)?
(Choose two.)
- A. Azure active directory (AD)
- B. Orion group
- C. Windows distribution AD
- D. Windows local domain
Answer: A,B
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 # 27
Which two of the following settings can be included in an alert cluster? (Choose two.)
- A. audit events
- B. device status
- C. configuration
- D. metric values
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 # 28
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 network discovery timeout was too short
- B. The preferred polling method in the discovery job was set to WML
- 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 # 29
A user is building a PerfStack project to troubleshoot an issue with an application. The user is unable to find data for the storage entities that the application accesses beyond application status. Which two of the following reasons explain this discrepancy? (Choose two.)
- A. amount of data to be displayed is too large
- B. account limitations restrict the user from accessing storage entities
- C. product that collects the data is not installed
- D. storage entities may not have data during the specific time period
Answer: B,C
Explanation:
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.
NEW QUESTION # 30
Which statement regarding SolarWinds* Hybrid Cloud Observability (HCO) groups is accurate?
- A. groups cannot be a member of another group
- B. group status rollup mode options do not apply to all members
- C. group status rollup mode is set to "show best status" by default
- 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 # 31
Which three of the following actions can be taken within a PerfStack project? (Choose three.)
- A. share to non-web console users
- B. add as a menu bar item
- C. show as a dashboard graphic
- D. show as a widget in a view
Answer: A,B,D
Explanation:
PerfStack(Performance Analysis) projects are highly versatile troubleshooting assets that can be shared and integrated across the SolarWinds Platform. According to theSolarWinds Platform Administrator Guide, once a correlation project is built-linking metrics like CPU, Latency, and IOPS-it can be utilized in several ways.
* Add as a menu bar item (A): A specific PerfStack project that is used frequently (such as "Core Switch Health") can be saved and added directly to the main navigation menu. This allows users to access the troubleshooting dashboard with a single click from anywhere in the console.
* Share to non-web console users (B): PerfStack projects can be shared via a unique URL. This "Public Link" feature allows stakeholders who do not have a SolarWinds account (such as third-party vendors or executives) to view the real-time correlation data in a read-only browser view.
* Show as a widget in a view (D): PerfStack projects can be embedded into Summary Views or Node Details pages as awidget. This provides context-sensitive performance data right alongside the standard node information, allowing for "at-a-glance" correlation without leaving the main dashboard.
While PerfStack provides visual data, it is typically treated as a dynamic, interactive "Project" or "Widget" rather than a static "dashboard graphic" (Option C) in the classic sense of a standalone image or icon.
NEW QUESTION # 32
Which two of the following conclusions can be made from the shown AppStack view? (Choose two.)
- A. The storage resource monitor (SRM) is not installed.
- B. The user's account is given administrator access rights.
- C. The option to hide categories with no objects is selected.
- D. A filter is applied to show entities related to an application.
Answer: C,D
Explanation:
According to the SolarWinds Platform Administrator Guide for Hybrid Cloud Observability, theAppStack Environment Viewprovides an interactive, visual mapping of relationships between monitored entities such as applications, servers, and storage. In the provided image, it is evident thata 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 thatthe 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 theStorage 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.
NEW QUESTION # 33
How can access to all reports be removed from user accounts?
- A. set user account report limitation to no reports
- B. set user account report limitation to default
- C. disable manage reports permissions
- D. add to report group and modify access
Answer: A
Explanation:
In the SolarWinds Platform, report access is governed by both functional permissions and account limitations.
While "Disable Manage Reports" (Option B) prevents a user from editing or creating reports, it does not necessarily hide the "Reports" menu or prevent the user from viewing existing reports they have access to. To completely remove the visibility and accessibility of all reports for a specific user account, anAccount Limitationmust be applied.
According to theSolarWinds Platform User Account Managementdocumentation, account limitations act as a security filter that restricts what the user can see throughout the entire Web Console. By navigating toSettings
> All Settings > Manage Accounts, selecting the user, andediting theirReport Limitation, an administrator can choose "No Reports". This configuration ensures that when the user logs in, the Reports section will either be empty or completely hidden from their navigation bar, regardless of their other permissions. This is the most effective method for high-security environments or multi-tenant deployments where certain users should have zero visibility into the historical performance data or inventory summaries contained within the reporting engine.
NEW QUESTION # 34
A subset of the monitored devices is due for maintenance. These devices are expected to be shut down and restarted multiple times during maintenance. Which action should be taken to prevent the devices from triggering alerts during this period without impacting data collection?
- A. Mute the devices during maintenance.
- B. Disable all alerts during maintenance.
- C. Make unreachable during maintenance.
- D. Unmanage devices during maintenance.
Answer: A
Explanation:
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.
NEW QUESTION # 35
Web console users are complaining of widgets moving within the web console view. What is causing this movement?
- A. screen resolution on user's computers
- B. users have edit view rights and are editing views used by multiple users
- C. unsupported browser is used
- D. single user has admin rights and is changing views in account settings
Answer: B
Explanation:
Layout instability in the SolarWinds Web Console is almost always a result of overlapping permissions on shared views. According to theSolarWinds Platform Administrator Guide, summary views (dashboards) are often shared across entire departments or user groups.
The cause of widgets "moving" unexpectedly is typically thatusers 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.
NEW QUESTION # 36
A non-administrator user reports they are unable to create Intelligent Maps in the web console. What is the reason for the block?
- A. user has not been given default set of user permissions
- B. user has not been given the creator role in maps
- C. user has not been given permission to add images
- D. user has not been given the manage views permission
Answer: C
Explanation:
The ability to create and manageIntelligent Mapsin the SolarWinds Platform is tied to a specific set of granular user permissions. While a user may have general rights to view the console, creating a map involves placing entities onto a canvas and, frequently, utilizing background images or custom icons. According to the SolarWinds Platform documentation on Map Management, a critical prerequisite for full map creation functionality is thepermission to add images (D).
In the user account settings underSettings > All Settings > Manage Accounts, there is a specific toggle for
"Allow Map Management" or "Allow Editing." However, if the underlying platform permission for "Add Images" is not enabled, the user will find the map creation wizard restricted or non-functional. This is because Intelligent Maps rely on the platform's shared image library to store the metadata and visual components of the map. Without the right to write to this library (Add Images), the user is blocked from saving new map definitions to the database. This permission is often disabled by default for standard users to prevent the web server's storage from being filled with unauthorized or non-work-related image files.
NEW QUESTION # 37
Which two of the following statements describe the AppStack tool in SolarWinds Hybrid Cloud Observability (HCO)? (Choose two.)
- A. automatically gathers information about objects in an environment (including relationships)
- B. drag and drop performance metrics, events, and log data from multiple device types to a chart for analysis
- C. displays objects in an environment in a customizable and interactive visual mapping
- D. visually correlates time series data, both historical and current from multiple products and entity types
Answer: A,C
Explanation:
AppStackis a specialized visualization tool designed to show the "stack" of dependencies between different layers of an IT environment. According to theSolarWinds 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) toautomaticallymap 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 aninteractive environment viewwhere 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 describePerfStack(Performance Analysis), which is the tool used for time-series correlation and dragging metrics onto charts. AppStack focuses on thestructureof the environment, whereas PerfStack focuses on theperformance dataof the entities within that structure.
NEW QUESTION # 38
Which two of the following customizations can be made on a report layout? (Choose two.)
- A. font of the report content
- B. logo on the report
- C. position of page number
- D. width of the report
Answer: B,D
Explanation:
The SolarWinds Platform web-based report builder provides specific layout options to ensure reports are professional and readable. According to theSolarWinds Platform Reporting Guide, customization of a report's visual structure is handled through the Layout tab.
* Logo on the report (B): Administrators can upload a custom company logo to appear in the header of the report. This ensures that exported PDFs and web views align with corporate branding standards.
* Width of the report (D): The layout editor allows users to define the report width, typically choosing between a fixed pixel width (often used to ensure a consistent look on printed paper or PDF) or a percentage-based fluid width that adjusts to the browser window.
While the platform allows for some styling, granular control over thefont of the report content(Option A) is generally limited to global CSS or predefined themes rather than individual report layout settings. Similarly, theposition of the page number(Option C) is usually a fixed element of the report's footer template and is not a standard customizable field within the primary web-based report layout wizard.
NEW QUESTION # 39
Which two of the following settings can be configured while adding a single node for monitoring within
"manage nodes"? (Choose two.)
- A. configure rediscovery interval
- B. select statistics and resources
- C. create custom properties
- D. add device studio pollers
Answer: B,C
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 # 40
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 # 41
Which two of the following platforms is supported by the agent software? (Choose two.)
- A. Windows 11 Enterprise
- B. Debian 11
- C. Windows Server 2022
- D. Fedora Linux
Answer: A,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 # 42
......
SolarWinds Observability-Self-Hosted-Fundamentals Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
Ace Observability-Self-Hosted-Fundamentals Certification with 77 Actual Questions: https://lead2pass.real4prep.com/Observability-Self-Hosted-Fundamentals-exam.html