CompTIA XK0-006 - CompTIA Linux+ V8 Exam

Environment variables in Linux can exist either locally within a shell or be exported to child processes. CompTIA Linux+ V8 emphasizes the distinction between shell variables and environment variables, as this affects how applications inherit configuration values.

Option D, export ENABLE_AUTH=1, is the correct choice because it both assigns the variable and marks it for export to the environment. Once exported, the variable becomes available to all subsequently executed commands and child processes spawned from the current shell. This behavior is required when applications or scripts rely on environment variables for configuration.

Option B, ENABLE_AUTH=1, only sets a shell-local variable. While it is accessible within the current shell session, it is not inherited by child processes unless explicitly exported. Option A, let ENABLE_AUTH=1, performs arithmetic evaluation and does not export the variable. Option C incorrectly assigns the output of a command substitution and does not set the desired value.

Linux+ V8 documentation highlights export as the correct mechanism for making variables available system-wide within a user session. Therefore, the correct answer is D.

The correct answer is C. export PATH=$PATH:$HOME/.local/bin because it correctly appends the directory $HOME/.local/bin to the existing PATH environment variable. The PATH variable defines a list of directories that the shell searches when a user enters a command without specifying its full path. By adding a directory to PATH, executables within that directory can be run directly from the command line.

In this case, the administrator installed a program in $HOME/.local/bin, which is not always included in the default PATH for all systems or users. By using export PATH=$PATH:$HOME/.local/bin, the existing PATH is preserved and extended to include the new directory. The use of $PATH ensures that previously defined directories remain accessible, while the colon (:) separates multiple directory entries.

Option A is incorrect because it literally assigns the string “PATH” instead of referencing the current PATH variable, effectively breaking command lookup.

Option B and D are incorrect because they attempt to assign a value to $PATH, which is invalid syntax. Environment variables should be assigned using their name (PATH), not with a dollar sign.

From a Linux+ perspective, managing environment variables is a fundamental skill in user and system configuration. Properly configuring the PATH variable ensures efficient command execution and usability, especially when installing custom or user-specific applications. For persistence, this change is typically added to shell configuration files like ~/.bashrc or ~/.profile.

Performance troubleshooting in CompTIA Linux+ V8 requires the ability to correlate metrics from tools like top, vmstat, and iostat. In this case, the iostat output provides the most critical data point: %iowait is at 70.38%.

The %iowait metric (also shown as wa in top) represents the percentage of time that the CPU was idle while there were outstanding disk I/O requests. Essentially, the CPU is waiting for the storage subsystem (hard drives or SSDs) to complete read or write operations. A value as high as 70% indicates a severe bottleneck in the storage layer. This " I/O wait " causes the system to feel sluggish or unresponsive because processes are stuck in an uninterruptible sleep state while waiting for data from the disk.

The top output also shows that the overall CPU is 79.2% idle, which confirms that the problem is NOT a lack of computational power (overutilization), making Option B incorrect. The system has 154 zombie processes, which might indicate poorly written software, but zombies themselves do not consume resources or cause slowness. There is no evidence of swap exhaustion (Option A) or a need for patching (Option D) provided in the statistics.

According to Linux+ V8 best practices, when high I/O wait is detected, administrators should investigate disk health, controller performance, or application-level disk usage (e.g., a database performing heavy indexing).

Therefore, high storage I/O latency is the verified explanation for the server slowness.

Comprehensive and Detailed Explanation From Exact Extract:

The lsscsi command is used to list information about SCSI devices (including storage arrays) that are attached to the system. This is critical when integrating a new storage array because it allows the administrator to verify that the operating system detects the new device at the SCSI layer, which is the underlying interface for most enterprise storage solutions. lsscsi outputs a list of recognized SCSI devices, their device nodes, and associated information.

Other options:

B. lsusb: Lists USB devices, not storage arrays on SCSI/SATA/SAS.

C. lsipc: Displays information on IPC (inter-process communication) facilities, unrelated to hardware detection.

D. lshw: Lists hardware details and can show storage, but lsscsi is specifically designed for SCSI device detection and is the most direct method for this task.

The correct answer is D. lm_sensors because it is the standard Linux utility used to monitor hardware sensor data, including motherboard temperature, CPU temperature, fan speeds, and voltage levels. The lm_sensors package provides tools such as the sensors command, which reads data from hardware monitoring chips embedded on the motherboard and displays real-time environmental and thermal information.

In Linux system management, monitoring hardware health is critical for maintaining system stability and preventing overheating issues. After installing and configuring lm_sensors (typically using the sensors-detect command), administrators can run sensors to view temperature readings for various components, including the motherboard chipset.

Option A (ipmitool) is partially related but incorrect in this context. While ipmitool can retrieve hardware monitoring data (including temperature) via IPMI interfaces, it requires compatible server hardware with IPMI support. It is not universally applicable across all Linux systems and is more specialized for enterprise server environments.

Option B (dmidecode) is incorrect because it retrieves hardware information from the system BIOS/firmware, such as manufacturer details, serial numbers, and hardware specifications. It does not provide real-time sensor data like temperature readings.

Option C (lspci) is also incorrect because it lists PCI devices and provides information about connected hardware components, but it does not include environmental or thermal data.

From a Linux+ perspective, lm_sensors is the most appropriate and commonly used tool for monitoring system temperatures and other hardware metrics, making it essential for proactive system management and troubleshooting.

This scenario falls under the Security domain of the CompTIA Linux+ V8 objectives and focuses on system hardening and service minimization. The Nmap scan output reveals that port 23 (Telnet) is open on the system, which represents a significant security risk.

Telnet is an insecure, legacy protocol that transmits authentication credentials and session data in plaintext, making it vulnerable to interception through packet sniffing or man-in-the-middle attacks. Linux+ V8 documentation explicitly emphasizes the principle of least functionality, which states that unnecessary or insecure services should be disabled and removed entirely rather than merely restricted.

Option D, disabling and removing the Telnet service on the server, is the best and most secure solution. This action eliminates the vulnerable service completely, ensuring that it cannot be exploited internally or externally. In secure Linux environments, Telnet should be replaced with SSH, which provides encrypted communication and strong authentication mechanisms.

Option A, blocking port 23 with a firewall, reduces exposure but does not eliminate the underlying risk. If the firewall rules are misconfigured or bypassed, the Telnet service would still be available. Linux+ V8 best practices recommend removing insecure services rather than relying solely on perimeter controls.

Option B is unrelated, as changing passwords does not address the risk of plaintext credential transmission. Option C is incorrect because closing ports at the network switch level is not an appropriate or scalable solution for host-level service hardening and does not address internal access risks.

Linux+ V8 documentation consistently highlights service auditing, port scanning, and removal of insecure protocols as essential system hardening steps. Therefore, the most effective and secure remediation is to disable and remove the Telnet service.

This issue is directly related to SELinux enforcement, which is a key topic in the Security domain of CompTIA Linux+ V8. The logs clearly indicate that SSH key-based authentication is failing due to an SELinux access control violation rather than a traditional file permission or SSH configuration problem.

The most important clue is the AVC denial message, which shows that the sshd process is being denied read access to the authorized_keys file. The security context of the file is listed as unconfined_u:object_r:home_root_t:s0. Under a targeted SELinux policy, SSH is only permitted to read authorized_keys files that are labeled with the correct SELinux type, typically ssh_home_t.

Because SELinux is running in enforcing mode, it actively blocks access that violates policy rules, even if standard UNIX permissions are correct. Although the file permissions (600) are acceptable for an authorized_keys file, SELinux does not rely solely on traditional permissions. The mismatch between the expected SELinux context and the actual context prevents sshd from accessing the file, causing SSH to fall back to password authentication.

Option D correctly identifies the root cause: the authorized_keys file does not have the correct SELinux security context. This is a well-documented Linux+ V8 troubleshooting scenario, commonly resolved by restoring the correct context using commands such as restorecon or by ensuring the file resides in a properly labeled home directory.

The other options are incorrect. Restarting sshd does not fix SELinux labeling issues. The policy itself is functioning as intended, and file ownership alone does not override SELinux access controls.

Linux+ V8 documentation emphasizes that SELinux denials must be addressed by correcting file contexts rather than weakening security controls. Therefore, the correct answer is D.

This performance-based question tests correct use of the tar utility for backup and restore operations, which is part of System Management in CompTIA Linux+ V8. The key detail is that the backup is explicitly described as uncompressed, so the correct archive file must be a plain .tar file rather than .tar.gz, .tgz, or .tar.bz2.

For the backup command, the correct syntax is:

tar -cvf /backups/application.tar -C /opt/ application

Here, -c creates the archive, -v enables verbose output, and -f specifies the archive filename. The -C /opt/ option changes to the /opt/ directory before archiving, and application is then archived relative to that location. This is the correct Linux+ method because it avoids storing unnecessary leading path components in the archive.

For the restore command, the correct syntax is:

tar -xvf /backups/application.tar -C /opt/

Here, -x extracts the archive, -v displays files being restored, and -f identifies the archive file. The -C /opt/ option ensures the archived application directory is restored back into /opt/, recreating /opt/application correctly.

The other file choices such as /backups/application.tar.gz, /backups/application.tgz, and /backups/application.tar.bz2 are incorrect because they indicate compressed backups, which the question specifically rules out. Likewise, options such as -xzvf or -xjvf are used for gzip- or bzip2-compressed archives and would not apply here.

Therefore, the verified correct PBQ answers are:

Backup: tar -cvf /backups/application.tar -C /opt/ application

Restore: tar -xvf /backups/application.tar -C /opt/

Log management is a critical system management function highlighted in CompTIA Linux+ V8, particularly in multi-server environments. As the number of systems and applications grows, managing logs locally on each server becomes inefficient and error-prone.

The best solution is to implement a centralized log aggregation solution, making option B correct. Centralized logging collects logs from multiple systems and applications into a single, secure location. This simplifies monitoring, searching, correlation, auditing, and incident response. Common solutions include syslog servers, ELK/EFK stacks, and SIEM platforms.

Linux+ V8 documentation emphasizes centralized logging as a best practice for availability, troubleshooting, and security analysis. It enables administrators to detect patterns, investigate incidents, and maintain compliance more effectively than isolated log files.

The other options are insufficient on their own. On-demand retrieval does not scale well. Log backups protect data but do not simplify analysis. Log rotation manages disk usage but does not address distributed log complexity.

Therefore, the correct answer is B. Implement a centralized log aggregation solution.

Firewall configuration is a key topic in the Security domain of CompTIA Linux+ V8. DNS primarily uses UDP port 53, but TCP port 53 is also required for zone transfers, large responses, and certain reliability scenarios. In this case, the administrator explicitly needs to allow DNS over TCP from a specific network.

The correct command is ufw allow 53/tcp from 10.0.0.0/24. This rule allows incoming TCP traffic on port 53 only from the specified subnet, following the principle of least privilege. Linux+ V8 documentation emphasizes restricting firewall rules by source network whenever possible to minimize attack surfaces.

Option A is incorrect because UFW service aliases like dns are not always guaranteed to map explicitly to TCP, and the syntax is incomplete. Option B is invalid because ufw enable is used to enable the firewall globally and does not define rules. Option D disables firewall protections and introduces a major security risk.

Linux+ V8 best practices stress precise, minimal firewall rules instead of broad or disabling actions. Therefore, C is the correct and secure choice.