SolarWinds Observability Self Hosted Fundamentals 問題集 練習問題・模擬試験｜日本語版＆英語版対応

Explanation: The SolarWinds Platform provides distinct tools for visualizing different aspects of environmental health and performance. AppStack is primarily an entity-relationship mapping tool. According to the SolarWinds SAM Administrator Guide, "The AppStack Environment view provides a powerful layer of troubleshooting visibility by exposing all participating objects in your environment, as well as their relationships to one another". It allows administrators to customize which entities (nodes, applications, volumes, etc.) are visible and how they are grouped to show dependencies. Conversely, PerfStack (Performance Analysis) is the engine used for metric correlation. As stated in the SolarWinds Platform Administrator Guide, PerfStack allows users to "drag and drop performance metrics from multiple entities onto a single chart to correlate data over time". While AppStack excels at showing what is connected, PerfStack excels at showing how specific metrics (CPU, Latency, IOPS) across those connected entities interact. Therefore, a combination is required where AppStack handles the entities and PerfStack handles the metrics. Specifically, you use AppStack to identify the scope of entities involved in a performance bottleneck and then transition those entities into a PerfStack project to perform a deep-dive analysis of the metrics. This modular approach ensures that troubleshooting is both contextually aware (via AppStack) and data-driven (via PerfStack)

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, an Account Limitation must be applied. According to the SolarWinds Platform User Account Management documentation, account limitations act as a security filter that restricts what the user can see throughout the entire Web Console. By navigating to Settings > All Settings > Manage Accounts, selecting the user, and editing their Report 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.

Explanation: In Hybrid Cloud Observability (HCO), specifically within the AlertStack feature, related alerts are grouped into clusters to reduce "alert fatigue" and provide a unified view of an incident. According to the SolarWinds 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 is auto-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.