The standard tool for managing the system hostname on modern Linux distributions using systemd is hostnamectl. According to the CompTIA Linux+ V8 objectives, the command hostnamectl set-hostname < name > is the correct and permanent way to change the server ' s identity.
When an administrator runs hostnamectl set-hostname comptia1, the utility updates the various types of hostnames recognized by the system:
* Static Hostname: This is stored in /etc/hostname and persists across reboots.
* Transient Hostname: A temporary name received via network configuration (like DHCP).
* Pretty Hostname: A high-level, human-readable name that can include special characters.
Using hostnamectl is preferred over manually editing /etc/hostname because it immediately notifies the kernel and running services of the change, often without requiring a reboot to take effect system-wide.
The other options are incorrect. Option A, export HOSTNAME=comptia1, only changes the environment variable for the current shell session; it does not change the system ' s actual hostname and is lost when the session ends. Option B, adding the name to /etc/resolv.conf, is incorrect because that file is used for DNS resolver settings (nameservers and search domains), not for the local system ' s hostname. Option D, systemctl daemon-reload, is used to refresh systemd after configuration changes to unit files and has no functionality for changing a hostname.
Therefore, hostnamectl is the verified command for this task.

JSON (JavaScript Object Notation) is a lightweight data-interchange format that is easy for humans to read and write, and easy for machines to parse and generate. JSON is commonly used to transmit data between a server and a client, as it is language-independent and can be used in many environments.

Process scheduling and resource management are essential Linux administration skills covered in Linux+ V8.
When a process consumes excessive CPU resources, it can negatively impact overall system performance.
The correct solution is to lower the priority of the CPU-intensive task using the renice command. Niceness values influence how much CPU time a process receives relative to others. Increasing the niceness value reduces the process's priority, allowing other applications to receive CPU resources more fairly.
Option B directly addresses the issue. The other options do not. pidstat monitors processes but does not modify CPU allocation. nohup allows a process to continue running after logout but does not affect scheduling priority. bg resumes a stopped job in the background but does not reduce CPU usage.
Linux+ V8 documentation explicitly references nice and renice for managing CPU contention. Therefore, the correct answer is B.

This issue is best analyzed using a layered troubleshooting approach, as recommended in the Troubleshooting domain of CompTIA Linux+ V8. The reported symptom is intermittent or random disconnections from an NFS share, which commonly indicates a network reliability issue rather than a configuration or filesystem problem.
The most critical evidence comes from the output of ip -s link show. The network interface enp1s0 is reporting significant numbers of errors and dropped packets on both the receive (RX) and transmit (TX) paths. High packet loss at the network interface level directly affects protocols like NFS, which rely on stable, continuous TCP/IP communication. When packets are dropped or corrupted, NFS clients may experience timeouts, retransmissions, and apparent disconnections.
Although the df -h output shows that the NFS filesystem is 95% full, this alone does not typically cause random disconnections. A nearly full filesystem may lead to write failures or performance degradation, but it does not explain intermittent connectivity loss. Linux+ V8 documentation notes that filesystem capacity issues usually present as I/O errors, not transport-layer disconnects.
Options A and B can also be ruled out. If the mount point or IP address were incorrect, the NFS share would fail consistently rather than intermittently. The fact that the share is mounted and accessible confirms that the mount configuration and IP addressing are correct.
Linux+ V8 emphasizes that NFS performance and reliability are highly sensitive to network quality. Packet errors, drops, faulty NICs, cabling issues, duplex mismatches, or driver problems commonly result in unstable NFS behavior.
Therefore, the best explanation for the reported random disconnections is D. The interface is reporting a high number of errors and dropped packets.

The CA bundle path is a symlink to a file under /etc/pki/ca-trust/extracted/pem, and update-ca- trust cannot create that generated bundle while SELinux is enforcing. Restoring the default SELinux contexts on that directory allows the bundle file to be created and fixes the certificate verification failures during package installs.