매달, 우리는 1000명 이상의 사람들이 시험 준비를 잘하고 시험을 잘 통과할 수 있도록 도와줍니다.
SolarWinds Observability Self-Hosted Fundamentals 온라인 연습
최종 업데이트 시간: 2026년03월09일
당신은 온라인 연습 문제를 통해 SolarWinds Observability Self Hosted Fundamentals 시험지식에 대해 자신이 어떻게 알고 있는지 파악한 후 시험 참가 신청 여부를 결정할 수 있다.
시험을 100% 합격하고 시험 준비 시간을 35% 절약하기를 바라며 Observability Self Hosted Fundamentals 덤프 (최신 실제 시험 문제)를 사용 선택하여 현재 최신 75개의 시험 문제와 답을 포함하십시오.
정답:
Explanation:
Custom properties can be configured as "Mandatory" to ensure data integrity across the platform. According to the SolarWinds 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 to edit the 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.
정답:
Explanation:
AppStack is a specialized visualization tool designed to show the "stack" of dependencies between different layers of an IT environment. According to the SolarWinds Platform Administrator Guide, AppStack has two defining characteristics:
Automatic Relationship Gathering (A): The tool uses the data already collected by various modules (SAM, VMAN, SRM) to automatically map how applications, database instances, servers, virtual hosts, and storage volumes are linked. This eliminates the need for manual manual line-drawing in most cases.
Customizable Visual Mapping (B): It provides an interactive environment view where users can filter by status, application name, or site to see a visual map of the infrastructure. This allows a user to click on a failing application and see exactly which virtual host or storage array might be causing the failure due to its relationship.
Options C and D describe PerfStack (Performance Analysis), which is the tool used for time-series correlation and dragging metrics onto charts. AppStack focuses on the structure of the environment, whereas PerfStack focuses on the performance data of the entities within that structure.
정답:
Explanation:
SolarWinds agents support two communication modes: "Server-Initiated" (Passive) and "Agent-Initiated" (Active). According to the SolarWinds Platform Agent requirements and port information, the direction of communication determines which firewall ports must be open.
When an agent is configured for Agent-Initiated communication (where the agent on the managed node reaches out to the SolarWinds server), it uses TCP 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.
정답:
Explanation:
The alerting engine in the SolarWinds Platform uses a "Scope" and "Condition" logic to determine when an action should fire. According to the SolarWinds Platform Alerting Guide, the "Scope" defines which objects the alert engine should evaluate, while the "Condition" defines what performance metric triggers the alert.
To limit an alert to a specific set of router interfaces, the administrator must modify 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 a user sees in the console, not how the backend alerting engine processes data.
정답:
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 the SolarWinds Platform User Account Management guide, a Web Console Administrator can manage nodes, create alerts, build reports, and customize dashboards.
However, for security reasons, the ability to manage passwords―specifically the credentials used for polling (SNMP strings, WMI service accounts, or external integration secrets)―is often restricted. While an admin can assign an existing credential to a node, the ability to add, edit, or view the clear-text/obfuscated passwords within the centralized Credential Library is 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.
정답:
Explanation:
SolarWinds provides several ways to handle maintenance windows, but they have different impacts on historical data. According to the SolarWinds Platform Administrator Guide, "Unmanaging" a node (Option D) stops all polling entirely, resulting in "gaps" in your historical charts.
To prevent notifications while preserving data collection, the best practice is to Mute the devices during maintenance. When a device is "Muted" (also known as "Pause Actions"), the platform continues to poll the device and record its status and performance metrics (CPU, Memory, Latency) into the database. However, the alerting engine is instructed to suppress any notification actions (emails, scripts, etc.) for that specific entity. This ensures that you have a full historical record of the device's behavior during the maintenance period―showing exactly when it went down and came back up―without flooding the IT team with unnecessary alerts.
정답:
Explanation:
The My Deployment page is the centralized administrative hub for managing the health and scale of the SolarWinds Platform. According to the SolarWinds 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 can view license 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.
정답:
Explanation:
To prevent "alert noise" caused by temporary performance spikes, the SolarWinds Platform allows for threshold persistence. According to the SolarWinds 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 only sustained high utilization triggers an action is to set 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.
정답:
Explanation:
AlertStack in Hybrid Cloud Observability (HCO) uses alert clusters to group related active alerts into a single actionable incident. According to the SolarWinds HCO Alerting documentation, 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 metrics and events (Audit/Events) to give a comprehensive picture of the environment's health.
정답:
Explanation:
In the SolarWinds Platform, visibility of specific reports is managed through Report Limitations.
According to the SolarWinds Platform Reporting Guide, even if a user has general permissions to view nodes, an administrator can restrict their access to specific reports to ensure data privacy or to simplify their workspace.
By creating a report limitation, you define a rule―such as filtering by a custom property or report category―and apply it directly to a user's account settings. Once applied, the user will only see the reports that match the criteria of that limitation when they navigate to the Reports section of the Web Console. This is different from a standard Account Limitation (Option D), which restricts the visibility of the nodes themselves across the entire platform. Using a report-specific limitation allows the user to still monitor the nodes in real-time views while preventing them from accessing sensitive historical or inventory data contained in specific PDF or web-based reports.
정답:
Explanation:
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 the SolarWinds 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 chooses what to 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 to create or 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 assigned after a 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.
정답:
Explanation:
Account Limitations are security filters applied at the user or group level to control data visibility
within the Web Console. According to the SolarWinds Platform User Account Management guide, these limitations do not affect how data is collected (polling), but rather who can 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 the Polling Engines, which is managed via the "Manage Nodes" section rather than user-facing account limitations.
정답:
Explanation:
Anomaly-Based Alerting is a premier feature of Hybrid Cloud Observability that moves beyond static thresholds to identify performance deviations based on historical behavior. According to the SolarWinds 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.
Without Platform 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.
정답:
Explanation:
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 Engine documentation, the primary mechanism for a human operator to pause this automated progression is acknowledgement.
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 does not clear the alert or stop the "Reset Conditions" from being monitored. If the node stays down, the alert remains active, but no further new escalation emails will be sent. The alert will only truly disappear once the environment returns to a healthy state and the reset conditions are met.
정답:
Explanation:
The SolarWinds Platform utilizes a centralized Action Manager to handle alert notifications and remediations efficiently. According to the SolarWinds Platform Alerting Guide, alert actions (such as sending an email, executing a script, or posting to a Slack channel) are often treated as reusable objects. When multiple alerts (Alert A and Alert B) share the same action from the Action Manager, they are essentially pointing to a single configuration entry in the database.
If an administrator edits Alert A and modifies the parameters of that shared trigger action, the change is not isolated to just that alert's workflow. Instead, the trigger action is updated in the manager. Because Alert B is linked to that same action ID, it will immediately reflect the updated configuration the next time it triggers. This behavior is designed to simplify administration; for example, if a primary on-call email address changes, an admin only needs to update the action once rather than editing every individual alert. However, it requires caution: if a user intended to change the action for Alert A only, they should instead "Copy" the action or create a new one to avoid inadvertently altering the behavior of Alert B and all other alerts sharing that centralized action.