[2026年08月09日]Observability-Self-Hosted-Fundamentals試験問題集で100%合格率Observability-Self-Hosted-Fundamentals試験！
試験問題集リアルSolarWinds Certified Professional問題集77解答を試そう！
SolarWinds Observability-Self-Hosted-Fundamentals 認定試験の出題範囲：
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
質問 # 31
Which two of the following data categories appear in an AppStack view? (Choose two.)
- A. SNMP pollers
- B. servers
- C. NetFlow
- D. database instances
正解：B、D
解説：
AppStackis designed to provide a "top-to-bottom" visual representation of the IT infrastructure layers that support an application. According to theSolarWinds Platform Administrator Guide, the AppStack Environment view automatically maps relationships between specific monitored entities.
The two primary categories that appear in this view aredatabase instances (A)andservers (C). In a typical application stack, the "Server" represents the physical or virtual hardware, while the "Database Instance" (monitored via AppInsight for SQL, Oracle, etc.) represents the software layer running on that server.
AppStack visually links these so that if a database instance shows a critical status, an administrator can instantly see which server it is hosted on and if there are underlying infrastructure issues. Other common categories include Applications, Transactions, Virtual Hosts, Clusters, and Volumes.
NetFlow(Option B) is a traffic analysis technology used in the NetFlow Traffic Analyzer (NTA) and is generally not a primary "entity" category in the standard AppStack environment map.SNMP Pollers(Option D) are the backend mechanisms used to collect data; they are a configuration component rather than a logical infrastructure entity that would be represented as a layer in an application dependency stack.
質問 # 32
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 manage views permission
- 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 default set of user permissions
正解：C
解説：
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.
質問 # 33
Which two of the following statements apply to predefined alerts on SolarWinds Hybrid Cloud Observability (HCO)? (Choose two.)
- A. trigger and reset conditions of predefined alerts cannot be directly edited
- B. predefined alerts with send an e-mail action require default recipients to be configured in default send email action
- C. trigger and reset actions of predefined alerts cannot be directly edited
- D. predefined alerts with send an e-mail action will forward notifications to the product registration email as a default
正解：A、B
解説：
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.
質問 # 34
What are custom properties and how are they used?
- A. static fields used to identify nodes in SQL database
- B. built-in attributes used for dynamic device grouping
- C. static, pre-defined fields automatically applied to all monitored nodes
- D. user-defined fields to store additional node or element information
正解：D
解説：
Custom Propertiesare one of the most versatile features of the SolarWinds Platform, providing a way to extend the metadata associated with monitored objects. TheSolarWinds Platform Administrator Guidedefines them as "user-defined fieldsthat 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.
* Reporting: Reports can be generated to show the uptime of all nodes belonging to a specific "Owner" or "Cost Center".
Because they are user-defined, they provide the necessary flexibility to map technical monitoring data to real- world business structures.
質問 # 35
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 missing devices were configured for SNPMvS.
- B. The missing devices were included in the discovery ignore list.
- C. The preferred polling method in the discovery job was set to WML
- D. The network discovery timeout was too short
正解：B
解説：
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.
質問 # 36
Which two of the following items are required to use Anomaly-Based Alerts in SolarWinds Hybrid Cloud Observability (HCO)? (Choose two.)
- A. Platform Connect
- B. AIOps and machine-learning module
- C. advanced machine-learning feature
- D. internet connection
正解：A、C
解説：
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.
質問 # 37
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. no limitation
- C. new limitation
- D. default
正解：B
解説：
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.
質問 # 38
Which statement regarding SolarWinds* Hybrid Cloud Observability (HCO) groups is accurate?
- A. group status rollup mode options do not apply to all members
- B. groups cannot be a member of another group
- C. group status rollup mode is set to "show best status" by default
- D. groups can be created based on custom properties
正解：D
解説：
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.
質問 # 39
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 departments
- C. access to monitored data by device types
- D. polling of devices by location
正解：B、C
解説：
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.
質問 # 40
What two of the following reasons apply to creating custom views in SolarWinds' web console? (Choose two.)
- A. perform customizations with SQL queries
- B. limit user access to specific elements
- C. personalize user experience and focus on specific elements
- D. monitor devices and elements not shown in default views
正解：B、C
解説：
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.
質問 # 41
What is supported when importing custom property values to SolarWinds* Hybrid Cloud Observability (HCO)?
- A. incoming values can contain special characters
- B. importing complex .xls or .xlsx files
- C. importing values from .json file format
- D. incoming values validated before being written
正解：D
解説：
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.
質問 # 42
Which two of the following settings can be configured while adding a single node for monitoring within
"manage nodes"? (Choose two.)
- A. select statistics and resources
- B. create custom properties
- C. configure rediscovery interval
- D. add device studio pollers
正解：A、B
解説：
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.
質問 # 43
Multiple users have access to SolarWinds Hybrid Cloud Observability (HCO) reports. All users are permitted to view and run existing reports, however restrictions for a smaller group of users are needed for editing and creating reports. How should these restrictions be accomplished?
- A. remove reports view from menu bar for any user without edit permissions
- B. set allow alert management rights to yes for select users with edit permissions
- C. set alert limitation category to default for select users with edit permissions
- D. remove manage reports button for any user without edit permissions
正解：D
解説：
The ability to create or modify reports is a high-level administrative function in the SolarWinds Platform, distinct from the ability to simply view them. According to theSolarWinds Platform User Account Managementguide, this is controlled by theReport Managementright.
To restrict a specific group of users from creating or editing reports while still allowing them to view existing ones, the administrator mustremove the "Manage Reports" permissionfrom their user accounts. When this right is set to "No," the"Manage Reports" buttonis hidden from the "All Reports" view for that user. They can still click on and run any report they have access to, but they will lack the interface options to enter the
"Report Builder," change schedules, or delete entries. This provides a secure way to delegate report consumption to the wider team while centralizing report creation within a smaller group of "power users" or administrators. Option D is incorrect as it refers toAlerts, which is a separate permission set entirely.
質問 # 44
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 reset conditions to contain the desired nodes and interfaces.
- B. Create a critical status-based alert and change the interface utilization status.
- C. Modify the scope on the trigger conditions to contain the desired nodes and interfaces.
- D. Use an account limitation to limit the alert to desired devices and interfaces.
正解：C
解説：
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.
質問 # 45
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. view existing reports
- D. manage reports
正解：A、C
解説：
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.
質問 # 46
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. remove users' accounts and create individual accounts
- B. add users as individual users and configure permissions
- C. remove impacted groups and add all users individually
- D. re-order groups to apply correct permissions in order
正解：B、D
解説：
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.
質問 # 47
Which feature halts the alert escalation process?
- A. reset actions
- B. reset conditions
- C. acknowledgement
- D. trigger actions
正解：C
解説：
Alert escalation in the SolarWinds Platform allows for a tiered response to critical issues (e.g., emailing a technician immediately, then emailing a manager if the issue persists for 30 minutes). According to the SolarWinds HCO Alerting Enginedocumentation, the primary mechanism for a human operator to pause this automated progression isacknowledgement.
When an active alert is acknowledged via the Web Console, several things happen:
* The alert is moved to the "Acknowledged" category, signaling to other team members that the issue is being addressed.
* The "Acknowledge" timestamp and the user's name are recorded.
* The escalation chain is halted.Any further actions defined in the "Escalation" tab of the alert configuration-which were scheduled to fire after a certain duration-are cancelled.
It is important to note that acknowledging an alert doesnotclear the alert or stop the "Reset Conditions" from being monitored. If the node stays down, the alert remains active, but no furthernewescalation emails will be sent. The alert will only truly disappear once the environment returns to a healthy state and the reset conditions are met.
質問 # 48
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 17777
- D. TCP 17790
正解：B
解説：
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.
質問 # 49
An agent software has been deployed to the Windows domain controller, however the server is being polled through WMI. What is causing this irregularity?
- A. configure polling engine to accept agent data
- B. agent polling is not supported
- C. edit the node and change the polling method
- D. agent did not install correctly
正解：C
解説：
In the SolarWinds Platform, the method used to poll a node (SNMP, WMI, or Agent) is a specific property assigned to the node record in the database. According to theSolarWinds Platform Agent Managementguide, simply installing the agent software on a remote server does not automatically convert the existing node record to use that agent for data collection.
If a node was originally added to the system viaWMI, the platform will continue to attempt to poll it via WMI over the network using RPC/DCOM, even if the SolarWinds Agent is successfully installed and running on the target machine. To fix this "irregularity" and take advantage of the agent's encrypted, single-port communication, an administrator mustedit the node and change the polling method (D).
By going toManage Nodes, selecting the domain controller, and clicking "Edit Properties," the admin must find the "Polling Method" section and select "Agent". Once saved, the Polling Engine will stop using WMI network calls and will instead wait for the agent to provide the data (if in Agent-Initiated mode) or reach out to the agent via the agent's port (if in Server-Initiated mode). This change ensures that the monitoring load is shifted to the agent and that the communication adheres to the desired security profile.
質問 # 50
Which two of the following conclusions can be made from the shown AppStack view? (Choose two.)
- A. A filter is applied to show entities related to an application.
- B. The option to hide categories with no objects is selected.
- C. The user's account is given administrator access rights.
- D. The storage resource monitor (SRM) is not installed.
正解：A、B
解説：
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.
質問 # 51
The built-in custom property, AssetTag, was set to mandatory after device monitoring had been set up. Which two of the following results can be expected from this action? (Choose two.)
- A. asset tag must be provided for all existing monitored devices when edited
- B. asset tag must be provided after the action for all existing monitored devices
- C. asset tag must be provided immediately for all existing monitored devices
- D. asset tag must be provided for all existing monitored devices when polled
正解：A、B
解説：
Custom properties can be configured as "Mandatory" to ensure data integrity across the platform. According to theSolarWinds Platform Administrator Guide, changing a property like AssetTag to mandatory after nodes already exist creates an enforcement requirement.
The system does not retroactively block polling or delete nodes (Option B and D are incorrect), but it enforces the requirement during administrative interaction. Specifically:
* Requirement after the action (A): Moving forward, any new node added to the system will require the AssetTag field to be populated before the node can be saved.
* Requirement when edited (C): For existing nodes that do not yet have an AssetTag, the platform will permit them to exist and be polled normally. However, the next time an administrator attempts toeditthe properties of that node, the Web Console will block the "Save" action until a value is provided for the mandatory AssetTag field. This ensures that as the environment is managed over time, the metadata is gradually backfilled until all mandatory requirements are satisfied.
質問 # 52
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. configure refresh rates
- C. configure network operations center (NOC) mode
- D. apply account limitations
正解：A、B
解説：
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.
質問 # 53
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. removes the requirement for any trigger condition thresholds on an alert
- D. resets alerts that met established trigger conditions and fired outside the scope of those established behaviors
正解：B
解説：
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.
質問 # 54
Which two of the following items are required to use Anomaly-Based Alerts in SolarWinds Hybrid Cloud Observability (HCO)? (Choose two.)
- A. Platform Connect
- B. AIOps and machine-learning module
- C. advanced machine-learning feature
- D. internet connection
正解：A、C
解説：
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.
質問 # 55
......
あなたを余裕でObservability-Self-Hosted-Fundamentals試験合格させます！100%高合格率保証：https://www.jpntest.com/shiken/Observability-Self-Hosted-Fundamentals-mondaishu
Observability-Self-Hosted-Fundamentals問題集本日限定！無料アクセス可能に！：https://drive.google.com/open?id=1O5uxeeMsaqI1F7FScjFgHJmrP2fhIJxD