SNMP is used to monitor network devices by collecting status and performance information and allowing centralized management and alerting.

Log aggregation is the process of collecting and consolidating logs from multiple sources into a single location, making it easier to analyze and manage system events.

Version control rollback operations are a core DevOps skill covered in the Linux+ V8 objectives. When changes in a local Git repository break an application and must be reverted, the administrator must choose a command that directly undoes those changes.
The command git reset is the most appropriate option in this scenario. It allows the engineer to move the current branch pointer (HEAD) to a previous commit, effectively discarding or undoing local changes.
Depending on the reset mode (--soft, --mixed, or --hard), the engineer can control whether changes are preserved in the staging area or working directory. This flexibility makes git reset the primary tool for reverting problematic local changes.
The other options are not suitable. git pull fetches and merges changes from a remote repository and does not revert local modifications. git rebase rewrites commit history and is used to reapply commits on top of another base, not to undo broken changes. git stash temporarily saves uncommitted changes for later use but does not revert the repository to a stable state.
Linux+ V8 documentation emphasizes that git reset is commonly used during local development when changes need to be undone quickly before being shared with others. Therefore, the correct answer is B.

In Linux troubleshooting, identifying which ports are listening for connections is a foundational skill.
According to CompTIA Linux+ V8, the ss (socket statistics) utility is the modern replacement for the older netstat command. It is used to dump socket statistics and provides information similar to netstat, but it is faster and can display more detailed TCP and state information.
To check if a specific port (like 449) is open locally, the administrator would run ss -an | grep 449.
* -a: Displays both listening and non-listening (for established connections) sockets.
* -n: Shows numerical port numbers instead of attempting to resolve them to service names (e.g., showing 443 instead of https).
* | grep 449: Filters the output to show only lines containing the desired port number.
If the output shows a line with the state LISTEN on port *:449 or 127.0.0.1:449, the service is successfully running and bound to that port.
The other options are incorrect for the following reasons: ip link (Option A) is used to manage network interfaces (layer 2) and does not show port information (layer 4). dig (Option B) is a DNS lookup tool and cannot check port status. tracepath (Option C) is used to trace the network path to a host and detect MTU issues; it does not report on the state of specific local ports.
Therefore, ss is the verified tool for this troubleshooting task.

The correct answer is A. High CPU load because the uptime command output clearly shows elevated load averages (7.75, 5.72, 5.17), which indicate that the system is experiencing significant processing demand.
Load average represents the number of processes that are either actively using the CPU or waiting for CPU time. When this value is consistently higher than the number of available CPU cores, it suggests that the CPU is overloaded and processes are being delayed.
In this scenario, the application is not completing tasks within the expected time frame, which aligns with CPU contention. When too many processes compete for CPU resources, scheduling delays occur, causing slower execution of applications and services. This is a common performance bottleneck in Linux systems.
Option B (Insufficient disk space) is incorrect because disk space issues typically manifest as write failures or application errors related to storage, not high load averages.
Option C (Network latency) is incorrect because network issues would not directly impact the system's load average. Tools like ping or netstat would be more relevant for diagnosing such problems.
Option D (Memory leak) is partially plausible but not the most direct conclusion from the given data. A memory leak would typically be identified through high memory usage using tools like free, top, or vmstat, rather than load average alone.
From a Linux+ troubleshooting perspective, analyzing load average is critical for diagnosing performance issues. High load values strongly indicate CPU resource exhaustion, which directly impacts application responsiveness and task completion times.