Comprehensive and Detailed Explanation From Exact Extract:
The kill command is used to send signals to processes. The -9 option sends the SIGKILL signal, which immediately terminates the process and cannot be caught or ignored by the process. This is used as a last resort when a process is not responding to the default (SIGTERM, -15) or other signals. The SIGKILL signal guarantees termination.
Other options:
A). Default kill sends SIGTERM (-15), which requests a graceful shutdown but can be ignored.
B). -1 sends SIGHUP, used to reload configuration, not terminate.
D). -15 sends SIGTERM, not guaranteed to kill an unresponsive process.
Reference:
CompTIA Linux+ Study Guide: Exam XK0-006, Sybex, Chapter 3: " Managing Processes " , Section: " Sending Signals to Processes " CompTIA Linux+ XK0-006 Objectives, Domain 1.0: System Management

The correct answer is B. Inventory because the Ansible inventory is the component responsible for defining managed hosts and their grouping structure, along with associated variables for each host or group. The inventory file (which can be static or dynamic) lists systems that Ansible manages and organizes them into logical groups such as web servers, database servers, or development environments.
Inventories can include host-specific variables (host_vars) and group-specific variables (group_vars), allowing administrators to customize configurations per host or group. This flexibility is essential for large- scale automation where different systems require slightly different configurations. Inventory files can be written in INI or YAML format, and dynamic inventories can integrate with cloud providers to automatically discover hosts.
Option A (Modules) is incorrect because modules are individual units of work in Ansible that perform tasks such as installing packages or managing services. They do not define hosts or groups.
Option C (Playbooks) is incorrect because playbooks define the sequence of tasks to be executed on hosts, but they rely on the inventory to know which hosts to target.
Option D (Handlers) is incorrect because handlers are special tasks triggered by notifications (e.g., restarting a service after a configuration change), not for defining infrastructure.
From a Linux+ perspective, understanding Ansible inventory is crucial for automation and orchestration. It enables structured management of systems, supports scalability, and allows precise control over configurations across different environments, making it a foundational concept in infrastructure automation.

File extraction and backup restoration are fundamental System Management tasks covered in CompTIA Linux+ V8. In this scenario, the administrator must extract the contents of an existing backup file into a target directory.
The correct command is option B, which uses cpio in extract mode. The command changes into the destination directory (/var/www/html/) using pushd, extracts the archive contents with cpio -idv, and then returns to the original directory with popd. This ensures that files are restored into the correct location without modifying paths inside the archive.
The cpio utility is commonly used for backups created with cpio -o and supports reading archive data from standard input. Linux+ V8 documentation includes cpio as a valid and supported archive format for backup and restore operations.
The other options are incorrect. Option A incorrectly assumes the backup is a gzip-compressed tar archive.
Option C creates a new archive instead of extracting one. Option D assumes the file is a ZIP archive, which is not indicated by the .bkp extension.
Linux+ V8 emphasizes using the correct tool based on the archive format and restoring files into the intended directory. Therefore, the correct answer is B.

see the solution in Explanation below.
Explanation:


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/

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.