Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk
ServiceNow
All Vendors
  2. Home
  3. Exams
  4. SolarWinds
  5. Observability-Self-Hosted-Fundamentals

SolarWinds Observability-Self-Hosted-Fundamentals Exam Questions
SolarWinds Observability Self-Hosted Fundamentals (Page 4 )

Updated On: 24-Feb-2026
Page 3 of 16
PDF with 75 Questions

An alert has been created to email when AppInsight for SQL detects a database fragmentation that exceeds 30%. The issue is not considered resolved unless the fragmentation is below 10%. How would the reset conditions be configured for this alert?

  1. set reset conditions to manual reset when issue is resolved
  2. set reset condition to never reset and notify of all issues
  3. set reset condition to reset when condition is below a set percent
  4. set reset conditions to reset when trigger conditions are no longer true

Answer(s): C

Explanation:

In advanced alerting scenarios, particularly with performance metrics like disk fragmentation or temperature, the "Trigger Condition" and "Reset Condition" often require different thresholds to prevent "flapping"--a state where an alert rapidly toggles between triggered and reset states because the metric is hovering right at the threshold line. According to the SolarWinds Platform Alerting Guide, while the default behavior is to reset when trigger conditions are no longer true (Option D), this would reset the alert as soon as fragmentation hit 29.9%.

To satisfy the specific requirement where the issue is only "resolved" at 10%, a custom Reset Condition must be defined. By selecting "set reset condition to reset when condition is below a set percent," the administrator can explicitly define a separate value ($10\%$) from the trigger value ($30\%$). This creates a "deadband" or hysteresis effect, ensuring the alert remains active and visible until the database maintenance has successfully reduced the fragmentation to the desired healthy level. This configuration is essential for AppInsight applications where returning to a "not- critical" state (e.g., 29%) does not necessarily mean the underlying performance bottleneck has been sufficiently remediated.



What is the minimum supported version for SolarWinds Hybrid Cloud Observability (HCO) database server?

  1. SQL server 2012 service pack 4
  2. MS SQL server 2016 service pack 1
  3. MS SQL server 2019
  4. MS SQL server 2012 R2

Answer(s): C

Explanation:

The transition from the legacy Orion Platform to Hybrid Cloud Observability (HCO) introduced stricter hardware and software prerequisites to support modern features like AIOps, advanced mapping, and high-performance data processing. According to the SolarWinds 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 2019 is identified as the minimum supported version for 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.



Which two of the following export formats are supported in Hybrid Cloud Observability (HCO) reports? (Choose two.)

  1. excel
  2. JSON
  3. PDF
  4. txt

Answer(s): A,C

Explanation:

SolarWinds Hybrid Cloud Observability provides robust reporting capabilities designed for both technical analysis and executive presentation. The SolarWinds Platform Reporting Guide specifies 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 uses JSON (Option B) for internal API communications and some dashboard configurations, and txt (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.



An Intelligent Map has been created of certain administered entities. Entities are to be added before the map is added to an enterprise summary view.
When entities are added to the map, it is unable to be saved.
What is the cause of the issue?

  1. Only map owners can save edits to an original Intelligent Map. A copy is needed.
  2. The owner of the Intelligent Map has set it to read-only.
  3. The user does not have Intelligent Map edit rights.
  4. The user does not have rights to view and / or work with the nodes to be added.

Answer(s): C

Explanation:

SolarWinds Intelligent Maps require specific functional permissions within the user's account settings to perform modifications. According to the SolarWinds Platform Administrator Guide, the ability to view a map does not automatically grant the right to edit or save changes to it.

The primary cause for being unable to save edits--such as adding new entities or changing the layout--is that the user does not have Intelligent Map edit rights assigned to their user account. In the SolarWinds Web Console, map permissions are granular. An administrator must go to Settings > All Settings > Manage Accounts, select the user, and ensure the "Map Management" or specific "Allow Map Editing" toggle is set to "Yes". If this permission is absent, the user may still be able to interact with the map in a "live" temporary session (moving nodes around for visualization), but the "Save" button will either be disabled or will result in an error because the platform's security layer prevents permanent changes to the database from unauthorized accounts.



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.)

  1. account limitations restrict the user from accessing storage entities
  2. amount of data to be displayed is too large
  3. product that collects the data is not installed
  4. storage entities may not have data during the specific time period

Answer(s): A,C

Explanation:

PerfStack is a cross-stack data correlation tool, but its visibility is constrained by the underlying data collection modules and user security settings. According to the PerfStack 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 the Storage 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 uses Account Limitations to 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.






Post your Comments and Discuss SolarWinds Observability-Self-Hosted-Fundamentals exam dumps with other Community members:

Join the Observability-Self-Hosted-Fundamentals Discussion