Observability-Self-Hosted-Fundamentals Certification Exam Dumps Questions in here [May-2026]
Updated Observability-Self-Hosted-Fundamentals Exam Practice Test Questions
NEW QUESTION # 40
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 the creator role in maps
- B. user has not been given the manage views permission
- C. user has not been given permission to add images
- D. user has not been given default set of user permissions
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 # 41
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 reports
- B. new limitation
- C. default
- D. no limitation
Answer: D
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 # 42
Which statement regarding SolarWinds* Hybrid Cloud Observability (HCO) groups is accurate?
- A. groups can be created based on custom properties
- B. group status rollup mode options do not apply to all members
- C. groups cannot be a member of another group
- D. group status rollup mode is set to "show best status" by default
Answer: A
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 # 43
Which two of the following permissions are default settings for users added to SolarWinds* Hybrid Cloud Observability (HCO)? (Choose two.)
- A. log into web console
- B. edit views
- C. manage reports
- D. view existing reports
Answer: A,D
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 # 44
Web console users are complaining of widgets moving within the web console view. What is causing this movement?
- A. unsupported browser is used
- B. screen resolution on user's computers
- C. single user has admin rights and is changing views in account settings
- D. users have edit view rights and are editing views used by multiple users
Answer: D
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 # 45
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. change polling interval to match length of time for an alert to fire
- B. set node to change CPU status if threshold is met for multiple polling cycles
- C. set node to inherit CPU thresholds and alert to fire when threshold is met
- D. change polling method on the server from WMI to agent polling
Answer: B
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 # 46
Which two of the following use cases are utilized for account limitations? (Choose two.)
- A. access to features by departments
- B. access to monitored data by device types
- C. polling of devices by location
- D. access to monitored data by departments
Answer: B,D
Explanation:
Account Limitationsare security filters applied at the user or group level to control data visibility within the Web Console. According to theSolarWinds Platform User Account Managementguide, these limitations do not affecthowdata is collected (polling), but ratherwhocan see the resulting data.
The two primary use cases are:
* Access by Department (A): Organizations often use custom properties (like "Department") to tag nodes. By applying an account limitation, you can ensure that the "Finance" team only sees servers tagged for their department, while the "IT" team sees the entire infrastructure.
* Access by Device Type (B): Limitations can be set based on vendor, machine type, or other attributes.
For instance, a Network Operations Center (NOC) team might be limited to seeing only "Cisco" or
"Juniper" devices to keep their dashboard focused purely on networking gear.
Option C is incorrect because "access to features" (like the ability to manage alerts or reports) is handled via Account Permissions, not limitations. Option D is incorrect because "polling of devices" is a backend function of thePolling Engines, which is managed via the "Manage Nodes" section rather than user-facing account limitations.
NEW QUESTION # 47
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 # 48
What is supported when importing custom property values to SolarWinds* Hybrid Cloud Observability (HCO)?
- A. incoming values validated before being written
- B. importing values from .json file format
- C. importing complex .xls or .xlsx files
- D. incoming values can contain special characters
Answer: A
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 # 49
Which benefit does Anomaly-Based Alerting add to the Hybrid Cloud Observability (HCO) alerting engine?
- A. removes the requirement for the user to configure set of trigger conditions
- B. analyzes entity behavior and uses data to fire an alert if trigger conditions are outside established behavior
- C. resets alerts that met established trigger conditions and fired outside the scope of those established behaviors
- D. removes the requirement for any trigger condition thresholds on an alert
Answer: B
Explanation:
Anomaly-Based Alertingrepresents a shift from static thresholds to behavioral analysis in the HCO platform.
According to theSolarWinds HCO Alerting Enginedocumentation, this feature uses machine learning to establish a "baseline" for specific metrics like CPU load or memory usage over a period of 7 to 30 days.
The primary benefit is that itanalyzes entity behaviorand triggers an alert only when a metric deviates significantly from its historical "normal" for that specific day and time. For example, if a server traditionally runs at 90% CPU during a Sunday night backup, a static 80% threshold alert would trigger a "false positive" every week. Anomaly-based alerting learns this behavior and will only fire an alert if the CPU hits 90% on a Tuesday morning when the normal load is only 20%.
This reduces alert noise by focusing ontrue anomaliesrather than simple threshold violations. It does not
"remove the requirement for trigger conditions" (Options B and C); instead, it replaces a static numerical threshold with a dynamic, machine-learned threshold. The administrator still defineswhichentities to monitor andhowsensitive the anomaly detection should be.
NEW QUESTION # 50
Which two of the following configurations are available as content for web-based reports? (Choose two.)
- A. existing PerfStack projects
- B. existing diagrams
- C. existing intelligent maps
- D. existing widgets
Answer: C,D
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 # 51
A web console user reported they are unable to view reports within the web console. What is a possible cause for this issue?
- A. user is prevented from viewing all predefined reports
- B. user is prevented from viewing all reports
- C. user is prevented from viewing all limitations
- D. user is prevented from viewing all monitored entities
Answer: B
Explanation:
Visibility of the reporting module is a configurable security setting within each SolarWinds user account.
According to theSolarWinds Platform User Account Managementguide, if a user logs into the Web Console and finds the Reports section empty or inaccessible, it is likely due to anAccount Limitation.
Specifically, the "Report Limitation" field in the user's profile can be set to"No Reports". This setting acts as a total block, preventing the user from viewing any report definitions, whether they are predefined (out-of-the- box) or custom-made. This is a common configuration for restricted user roles, such as basic operators or external contractors, who need to see real-time status in dashboards but should not have access to the historical, inventory, or security data contained in the platform's reporting engine. While a user could also be restricted from seeing specific entities (Option B), this would typically just result in empty datainsidea report rather than the total inability to view the reports module itself. Setting the account to "No Reports" ensures the user isprevented from viewing all reportsglobally across the platform.
NEW QUESTION # 52
Several active directory groups have access to SolarWinds Hybrid Cloud Observability (HCO). There are three additional groups to be added, however they are not showing up on a search. Why can the additional groups not be added?
- A. missing groups have users already present in added groups
- B. missing groups exceed the maximum number of groups
- C. missing groups are distribution groups
- D. missing groups have too many users
Answer: C
Explanation:
When integrating Active Directory (AD) with the SolarWinds Platform, the system is designed to leverage AD groups for role-based access control (RBAC). According to theSolarWinds Platform Administrator Guide
, the platform specifically requiresSecurity Groupsfor authentication and permission mapping.
Active Directory contains two primary group types:Security GroupsandDistribution Groups. Distribution groups are intended purely for email lists and do not have a Security Identifier (SID) that can be used for assigning file system or application permissions. Because SolarWinds relies on the SID to grant web console access and define user rights,distribution groupswill not appear in the search results when attempting to add new Windows groups to the platform. To resolve this, the AD administrator must either convert the existing distribution groups to security groups or create new security groups containing the desired users. Once the group type is set correctly to "Security," the SolarWinds search utility will be able to resolve the group name and SID, allowing it to be imported and assigned permissions within the console.
NEW QUESTION # 53
A user account has been granted administrator rights in the web console. By default, which area is disabled for the user (i.e., unable to add, edit, schedule, or delete)?
- A. reports
- B. passwords
- C. alerts
- D. dashboards
Answer: B
Explanation:
In the SolarWinds Platform, "Administrator" rights in the Web Console grant extensive control over monitoring configurations, but they are distinct from "System Administrator" or "Security Administrator" roles. According to theSolarWinds Platform User Account Managementguide, a Web Console Administrator can manage nodes, create alerts , build reports , and customize dashboards.
However, for security reasons, the ability to managepasswords-specifically the credentials used for polling (SNMP strings, WMI service accounts, or external integration secrets)-is often restricted. While an admin canassignan existing credential to a node, the ability to add, edit, or view the clear-text/obfuscated passwords within the centralizedCredential Libraryis a separate, higher-level security permission. This prevents a standard Web Administrator from potentially harvesting sensitive service account passwords from the database. This "separation of duties" ensures that while a user can manage the monitoring environment, they cannot necessarily compromise the security of the underlying infrastructure accounts.
NEW QUESTION # 54
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. re-order groups to apply correct permissions in order
- B. add users as individual users and configure permissions
- C. remove users' accounts and create individual accounts
- D. remove impacted groups and add all users individually
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 # 55
Which type of modern dashboard widget is represented?
- A. table
- B. KPI
- C. custom HTML
- D. counter
Answer: B
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 # 56
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. perform customizations with SQL queries
- C. personalize user experience and focus on specific elements
- D. monitor devices and elements not shown in default views
Answer: A,C
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 # 57
Which two of the following items are required to use Anomaly-Based Alerts in SolarWinds Hybrid Cloud Observability (HCO)? (Choose two.)
- A. advanced machine-learning feature
- B. AIOps and machine-learning module
- C. Platform Connect
- D. internet connection
Answer: A,C
Explanation:
Anomaly-Based Alertingis a premier feature of Hybrid Cloud Observability that moves beyond static thresholds to identify performance deviations based on historical behavior. According to theSolarWinds HCO Administrator Guide, this feature relies on cloud-assisted analytics to process complex datasets. To enable this, two specific components are required:
* Advanced Machine-Learning Feature: This is the functional logic within the HCO platform that identifies patterns and establishes "normal" baselines for metrics like CPU load or interface utilization.
* Platform Connect: This is the essential bridge that links the self-hosted HCO instance to the SolarWinds cloud-based AIOps engine. Because anomaly detection requires significant computational power to analyze long-term historical trends, the heavy processing is often offloaded. Platform Connect ensures that the necessary metadata can be analyzed securely to generate the dynamic thresholds used for these alerts.
WithoutPlatform Connect, the local server cannot access the machine-learning models required to calculate what constitutes an "anomaly" versus standard operational variance. This architecture allows HCO to provide high-level AIOps capabilities without requiring massive localized hardware for every installation.
NEW QUESTION # 58
Which two of the following metrics are supported within Hybrid Cloud Observability (HCO) anomaly-based alerting? (Choose two.)
- A. percent packet loss
- B. disk space usage
- C. average CPU load
- D. interface utilization
Answer: A,C
Explanation:
Anomaly-Based Alertingin HCO is currently focused on high-cardinality performance metrics that exhibit clear cyclical patterns (daily or weekly cycles). According to theSolarWinds Platform Alerting Guide, the machine learning engine is optimized for metrics where "normal" behavior varies significantly based on time of day.
The two primary supported metrics for this feature are:
* Average CPU Load (A): CPU utilization is highly variable; a server might be idle at night but busy during business hours. Anomaly detection learns these patterns to prevent false positives during scheduled peak times.
* Percent Packet Loss (D): Network stability is a critical indicator of environmental health. By establishing a baseline for packet loss, the system can distinguish between a minor, expected "blip" in a high-traffic environment and a true anomaly that indicates a failing circuit or network congestion.
While metrics like "Disk Space Usage" (Option B) are critical, they are generally "linear" or "incremental" rather than cyclical; a disk filling up is a trend that is usually better handled by standard predictive or static threshold alerts. Similarly, while interface utilization is important, the initial release of anomaly-based features prioritizedNode-levelperformance metrics like CPU and Packet Loss to provide the most immediate value for identifying server and core network health deviations.
NEW QUESTION # 59
A user reported they could not see data related to monitored nodes beyond their geographical location within SolarWinds* Hybrid Cloud Observability (HCO). Other staff within the organization do not have the same problem. What is the likely cause of the issue?
- A. account has been limited to nodes within the geographical location
- B. nodes beyond the user's geographical location are displayed in widgets that are hidden from the user
- C. nodes outside the user's geographical location are not monitored
- D. view limitations for those nodes beyond the user's geographical location are applied to views
Answer: A
Explanation:
In the SolarWinds Platform, data visibility is controlled at the account level through a security feature known as Account Limitations. According to theSolarWinds Platform User Account Managementdocumentation, when a single user has restricted visibility while others do not, it points to a specificAccount Limitation applied to that user's profile.
Account limitations act as a persistent filter on the database queries performed by the Web Console during that user's session. If an administrator has configured a limitation based on a custom property like "Location" or "Region," the user will only see entities that match that specific criteria. For example, if the user's account is limited to Location = New York, they will be unable to see nodes, alerts, or reports associated with Location = London, even if those nodes are active and being monitored by the system.
This is a fundamental tool for multi-tenant environments or large enterprises where different teams are responsible for different geographic or logical segments of the network. It is more effective than "View Limitations" (Option D) because an account limitation follows the user across the entire platform, including search results, alerts, and reports, whereas a view limitation only affects a specific dashboard page. Options B and C are unlikely because they would typically affect multiple users or indicate a major monitoring gap rather than a user-specific visibility issue.
NEW QUESTION # 60
Which two of the following actions can be achieved through the My Deployment page in the web console?
(Choose two.)
- A. Send diagnostics to SolarWinds technical support.
- B. Perform a centralized upgrade of an existing deployment.
- C. Activate licenses for installed products.
- D. Set up a SolarWinds platform high availability (HA) pool.
Answer: B,D
Explanation:
TheMy Deploymentpage is the centralized administrative hub for managing the health and scale of the SolarWinds Platform. According to theSolarWinds Platform Installation and Upgrade Guide, this page simplifies complex infrastructure tasks that previously required logging into the individual server consoles.
* Centralized Upgrade (B): The "Updates & Evaluations" tab allows administrators to download and orchestrate the upgrade of the main polling engine and all additional polling engines from a single interface. This "Centralized Upgrade" feature ensures all components are updated in the correct order.
* High Availability (HA) Pool Setup (D): The "High Availability" tab provides the wizard-driven interface to create and manage HA pools. This allows you to link a primary server with a standby server to ensure near-zero downtime in the event of a hardware or software failure.
While you canviewlicense status (Option A) or trigger diagnostics (Option C), license activation is typically handled via the License Manager, and diagnostic transmission is often a sub-function of the technical support workflow rather than the primary architectural focus of the "My Deployment" management page.
NEW QUESTION # 61
Which two of the following ways can objects be selected when creating custom reports?
- A. PostgreSQL query
- B. dynamic query builder
- C. PowerShell script
- D. static selection
Answer: B,D
Explanation:
When creating a web-based report in the SolarWinds Platform, the first step is defining the "Selection Method" for the entities you want to include. According to theSolarWinds Platform Reporting Guide, the platform offers two primary user-friendly ways to define the scope of a report:
* Static Selection: This method allows the administrator to manually pick specific nodes, interfaces, or applications from a list. This is best suited for reports targeting a fixed set of infrastructure, such as
"Core Data Center Switches".
* Dynamic Query Builder: This is the most powerful method for automated reporting. It allows you to define a set of rules-such as "Vendor is Cisco" and "Department is Finance"-that automatically update the report's content as new devices are added to monitoring that match those criteria.
While advanced users can useSWQL(SolarWinds Query Language) orSQLto define a custom selection, PostgreSQL(Option B) is not used as the backend database for the SolarWinds Platform. Furthermore, while PowerShell(Option C) can be used toextractdata via the SolarWinds Information Service (SWIS) API, it is not a selection method used within the native Web-Based Report builder interface.
NEW QUESTION # 62
A SolarWinds* Hybrid Cloud Observability (HCO) user account is to be used to run a NOC view in an operations center. The view is to run continuously without being logged out. Which setting should be configured within the user account to accomplish this goal?
- A. grant account manage view permissions
- B. set account expiration date to 1 year from now
- C. disable session timeout default settings
- D. grant account manage dashboard permissions
Answer: C
Explanation:
For Network Operations Centers (NOCs) that display SolarWinds dashboards on large wall-mounted monitors, maintaining a continuous session is vital. By default, the SolarWinds Platform implements a security timeout (often 15 to 20 minutes of inactivity) that automatically logs a user out to protect the console.
According to theSolarWinds Platform Administrator Guide, to prevent this for a dedicated NOC account, the administrator mustdisable session timeout default settings (A). This is found within the "Advanced" section of the specific User Account settings. When this toggle is enabled, the platform ignores the global session timeout for that specific login, allowing the dashboard to refresh indefinitely without requiring manual re- authentication.
While granting management permissions (Options B and C) might allow the user tocreatethe view, it does nothing to prevent the session from expiring. Similarly, an "Account Expiration Date" (Option D) only controls the long-term validity of the account, not the duration of an individual active web session. Disabling the timeout is the standard procedural requirement for any "Service Account" or "Display Account" used in a continuous monitoring environment.
NEW QUESTION # 63
......
Pass SolarWinds Certified Professional Observability-Self-Hosted-Fundamentals Exam With 77 Questions: https://testking.testpassed.com/Observability-Self-Hosted-Fundamentals-pass-rate.html