Skip to main content
ITPrepCerts
Login
Exams Free Samples About Contact
Login Create an account

Observability-Self-Hosted-Fundamentals SolarWinds Observability Self-Hosted Fundamentals

  • SolarWinds
  • 4 free sample questions

About this exam

Observability-Self-Hosted-Fundamentals is the SolarWinds exam SolarWinds Observability Self-Hosted Fundamentals. Paid practice material for this exam is not available yet, but you can try its free sample questions.

Exam code
Observability-Self-Hosted-Fundamentals
Vendor
SolarWinds
Practice questions
Not available yet
Free sample questions
4
Question bank last updated
Not available yet

Try 2 sample questions

Taken from the free sample set for Observability-Self-Hosted-Fundamentals.

Question 1 (choose 2)

Which two of the following account types are supported in SolarWinds Hybrid Cloud Observability (HCO)? (Choose two.)

  1. Option A:
    Azure active directory (AD)
  2. Option B:
    Orion group
  3. Option C:
    Windows distribution AD
  4. Option D:
    Windows local domain 
Show answer and explanation

Correct answer: A, B

SolarWinds Hybrid Cloud Observability supports a variety of authentication methods to ensure seamless integration with enterprise identity providers. According to the SolarWinds Platform Installation and Upgrade Guide, the two primary modern account types used for centralized management are Azure Active Directory (AD) and Orion 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.  

Question 2 (choose 1)

What are custom properties and how are they used?  
  1. Option A:
    built-in attributes used for dynamic device grouping
  2. Option B:
    static fields used to identify nodes in SQL database
  3. Option C:
    static, pre-defined fields automatically applied to all monitored nodes
  4. Option D:
    user-defined fields to store additional node or element information
Show answer and explanation

Correct answer: D

Custom Properties are one of the most versatile features of the SolarWinds Platform, providing a way to extend the metadata associated with monitored objects. The SolarWinds Platform Administrator Guide defines them as "user-defined fields that allow you to add custom information to nodes, interfaces, volumes, or other monitored entities". Unlike built-in attributes like "IP Address" or "Vendor," which are discovered automatically, custom properties are created by the administrator to suit specific business needs. Common examples include "Site Location," "Emergency Contact," "Department," or "Service Level Agreement (SLA) Tier". These fields are critical for organization and automation because they allow for: Filtering and Grouping: You can create groups that automatically include any node where the "Department" custom property is set to "Finance". Alerting: You can configure alerts to only trigger for nodes marked as "Mission Critical" in a custom property field.  
See all 4 free sample questions