Free XK0-006 Practice Test Questions and Answers (2026) Practice Questions

The kill command sends signals to processes. To force the termination of a non-responsive process, the SIGKILL signal (signal number 9) should be used. This signal cannot be caught or ignored by the process, and the kernel will terminate it immediately. The default kill command and kill -15 both send SIGTERM, which is a request for graceful termination that a non-responsive process might ignore. Signal 1 (SIGHUP) is typically used to signal a daemon to reload its configuration.

A. kill PID sends the default SIGTERM (15) signal, which requests a graceful shutdown and can be ignored by a non-responsive process.

B. kill -1 PID sends the SIGHUP signal, which is typically used to have a daemon re-read its configuration file, not terminate it.

D. kill -15 PID explicitly sends the SIGTERM signal, which is the same as the default and is not a forced termination.

1. GNU Coreutils. (2022). kill invocation. In GNU Coreutils manual. Section 23.2. Retrieved from https://www.gnu.org/software/coreutils/manual/htmlnode/kill-invocation.html (Describes signal numbers and their meanings

including SIGKILL as 9).

2. Red Hat Enterprise Linux 9 Documentation. (2023). Chapter 9. Managing processes. Section 9.3.2. Terminating processes. Retrieved from https://access.redhat.com/documentation/en-us/redhatenterpriselinux/9/html/configuringbasicsystemsettings/managing-processesconfiguring-basic-system-settings (Specifies that kill -9 sends the SIGKILL signal to immediately stop a process).

3. Bovet

D. P.

& Cesati

M. (2005). Understanding the Linux Kernel

3rd Edition. O'Reilly Media. Chapter 10

Signals

p. 405. (Explains that SIGKILL and SIGSTOP are two special signals that cannot be caught or ignored).

In Linux shells like Bash, assigning a variable with VAR=value creates a shell variable, which is only available within the current shell session. To make the variable accessible to child processes (subsequently executed commands), it must be converted into an environment variable. The export command is used for this purpose. It marks the specified variable for export to the environment of child processes. The syntax export ENABLEAUTH=1 both declares the variable and exports it in a single step, fulfilling the requirement.

A. let is a shell builtin used for evaluating arithmetic expressions, not for setting environment variables.

B. This command creates a local shell variable, which is not inherited by child processes or sub-shells.

C. This command substitution reassigns the variable's existing value to itself; it does not export it.

1. GNU Bash Reference Manual. (2022). 4.2 Bash Builtin Commands. "The export builtin command marks the names of shell variables to be passed to child processes in the environment." Retrieved from https://www.gnu.org/software/bash/manual/bash.html#index-export

2. Sobell

M. G. (2018). A Practical Guide to Linux Commands

Editors

and Shell Programming. Pearson Education. Chapter 8

"The Bourne Again Shell

" section on "User-Created Variables

" explains the difference between local and environment variables and the use of export.

3. University of Cambridge

Computing Service. (n.d.). Introduction to the Unix shell for data processing. Section "Variables". "To make a variable available to other programs we run from the shell

we must export it."

The docker ps command is used to list all currently running containers. This command provides a snapshot of the active containers, including their container ID, the image they are based on, the command being run, creation time, status, ports, and names. This is the most direct way for an administrator to validate which containers are in a running state to begin troubleshooting an application accessibility issue.

A. docker start is used to start one or more containers that are in a stopped state, not to list them.

C. docker run creates and starts a new container from a specified image; it does not list existing containers.

D. docker images lists the container images that have been downloaded to the local host, not the running container instances.

1. Docker Inc. (2024). "docker ps". Docker Docs. Retrieved from https://docs.docker.com/engine/reference/commandline/ps/. The official documentation specifies

"List containers. The default is to show only running containers."

2. Pahl

C.

& Jamshidi

P. (2016). Microservices: A Systematic Mapping Study. In 6th International Conference on Cloud Computing and Services Science (CLOSER) (pp. 137-146). SCITEPRESS – Science and Technology Publications. DOI: 10.5220/0005789201370146. The paper discusses container management

where listing running instances (docker ps) is a fundamental operational task.

The git reset command is the most appropriate tool for discarding local, uncommitted changes. Specifically, git reset --hard will reset the staging area and the working directory to match the most recent commit (HEAD). This effectively discards all modifications made to tracked files since the last commit, which aligns with the engineer's need to revert the changes that broke the application. It provides a clean state based on the last known good version in the commit history.

A. git pull is used to fetch changes from a remote repository and merge them into the local branch, which is unrelated to discarding local changes.

C. git rebase is a complex command used to rewrite commit history by changing a branch's base commit. It does not discard uncommitted local changes.

D. git stash saves local changes to a temporary area to be reapplied later. Its purpose is to save work, not discard it permanently.

1. Chacon

S.

& Straub

B. (2014). Pro Git (2nd ed.). Apress. Chapter 7.3

"Git Tools - Reset Demystified". (Explains in detail how git reset --hard discards changes in the working directory and staging area). Available at https://git-scm.com/book/en/v2/Git-Tools-Reset-Demystified.

2. The Git Community. (n.d.). git-reset Documentation. Retrieved from https://git-scm.com/docs/git-reset. (The official documentation states that git reset --hard "Resets the index and working tree. Any changes to tracked files in the working tree since are discarded.").

The getent (get entries) command is designed to retrieve entries from administrative databases specified in the Name Service Switch configuration (/etc/nsswitch.conf). Using getent passwd accounting specifically queries the password database for the user "accounting." The output format mirrors the /etc/passwd file, providing the username, user ID (UID), group ID (GID), GECOS field, home directory, and the user's assigned login shell. This single command provides all the information requested in the question, making it the most direct and correct tool for the task.

B. The id command displays the user ID (UID), group ID (GID), and group memberships, but it does not show the user's home directory or default shell.

C. The /etc/shadow file contains secure user account information like password hashes and aging policies, not the user's home directory or assigned shell.

D. The who command lists users who are currently logged into the system. It does not provide the detailed account configuration information requested.

1. The GNU C Library. (2023). Manual

Section 30.1 The Name Service Switch. The documentation explains that getent displays entries from databases supported by the Name Service Switch

which includes passwd.

2. Canonical Ltd. (2023). Ubuntu Server Guide

User Management

User Information. The guide details the use of commands like getent to look up user information from various sources

including local files and network services.

3. Linux man-pages project. (2023). getent(1) Manual Page. The manual page explicitly states getent retrieves entries from NSS databases and shows the syntax getent database [key ...].

The task requires two simultaneous actions: viewing a log file in real time and saving that same output to another file. The tail -f command follows a file, printing new lines to standard output as they are added, which satisfies the "real time" viewing requirement. The tee command reads from standard input and writes to both standard output (the screen) and a specified file. By piping (|) the output of tail -f to tee logfile.txt, the administrator can see the real-time log updates on the terminal while tee simultaneously saves an identical copy to logfile.txt.

A. The > redirection operator sends standard output to logfile.txt instead of the screen, so the administrator would not see the log in real time.

B. The pipe | operator is used to send the output of one command to the input of another command, not directly to a file. This syntax is incorrect.

C. The >> redirection operator appends standard output to logfile.txt. Similar to >, the output would not be displayed on the screen for real-time review.

1. The GNU Project. (2020). GNU Coreutils Manual

Section 11.1 tail: Output the last part of files and Section 14.1 tee: Redirect output to multiple files or processes. The documentation describes the -f option for tail and the function of tee to split output.

2. Stanford University. (2019). CS107: Computer Organization & Systems

Lecture 03: The UNIX Command Line. Course materials cover I/O redirection and pipes

explaining the distinct functions of >

>>

|

and the utility of tee for splitting output streams.

3. Red Hat Enterprise Linux 8 Documentation. (2023). Configuring basic system settings

Chapter 25. Managing log files. Section 25.1.2 discusses using tail and other utilities for monitoring log files in real time.

To execute a script by its name alone, without prepending its path (e.g., ./script.sh), the directory containing the script must be listed in the PATH environment variable. The PATH variable is a colon-separated list of directories that the shell searches for executables. The command export PATH=$PATH:/home/user/scripts appends the new directory /home/user/scripts to the existing list of directories in the PATH. This makes any executable file within that directory runnable from any location in the filesystem by simply typing its name. The export command makes this variable available to subsequently executed commands.

A. The SHELL variable defines the user's login shell (e.g., /bin/bash), not the search path for executables. This command has incorrect syntax and purpose.

B. The TERM variable specifies the terminal type being used (e.g., xterm, vt100). It has no effect on how the shell finds and executes commands.

D. This command uses incorrect syntax. alias is a separate shell builtin for creating command shortcuts, and export is used for environment variables.

1. The GNU Project. (2022). Bash Reference Manual

Section 6.7 Bash Variables. The manual defines the PATH variable as "The search path for commands. It is a colon-separated list of directories in which the shell looks for commands."

2. Massachusetts Institute of Technology (MIT) OpenCourseWare. (2020). 6.003

The Shell. Lecture notes describe the PATH variable and its role in command execution

explaining how to modify it to include new directories.

3. The Linux Documentation Project. (2004). Bash Guide for Beginners

Chapter 3. The Bash environment. Section 3.2.2 discusses shell initialization files and the importance of setting the PATH variable correctly.

The docker image pull command (or its shorthand docker pull) is the standard command used to download a Docker image from a container registry, such as the default Docker Hub. When docker image pull debian is executed, Docker contacts the registry, finds the image named "debian," and downloads its layers to the local machine. If no specific tag is provided, Docker defaults to pulling the image with the latest tag.

A. docker image init debian is an invalid command; init is not a valid subcommand for docker image.

C. docker image import debian creates a new filesystem image from the contents of a tarball, not from a remote repository.

D. docker image save debian is used to export an existing local image to a tar archive; it does not download an image.

1. Docker Inc.

Official Docker Documentation

docker image pull command reference. The documentation states: "Pull an image or a repository from a registry... Most of your images will be created on top of a base image from Docker Hub."

2. Turnbull

J. (2018). The Docker Book: Containerization is the new virtualization (2nd ed.). Chapter 3

"Working with Docker images

" explicitly demonstrates using docker pull to download images from Docker Hub.

3. Massachusetts Institute of Technology (MIT) OpenCourseWare

6.033 Computer System Engineering

Spring 2018. Lecture 20

"Containers

" discusses the Docker ecosystem

including the role of Docker Hub and the pull command for retrieving images.

To achieve the objective of archiving Ann's home directory, you must invoke tar with the -cvf flags, which stand for create a new archive, verbose output, and specify the filename of the archive (/tmp/ann.tar), followed by the target directory to be archived (/home/ann). Uncompressed .tar is chosen here because no compression flags (like -z for gzip or -j for bzip2) were paired with the correct corresponding file extensions in the available objects.

To extract the files into Joe's directory, you must use the -xvf flags to extract the verbose file /tmp/ann.tar. Crucially, you must use the -C (capital C) flag, which tells the tar command to change its working directory to the specified path (/home/joe) before extracting the files, ensuring they are placed directly into Joe's home directory rather than the current working directory.

Free Software Foundation. (2023). GNU tar manual, Section 3.2: How to Create Archives. Official GNU Documentation.

Free Software Foundation. (2023). GNU tar manual, Section 3.3: How to Extract Members from an Archive. Official GNU Documentation.

Free Software Foundation. (2023). GNU tar manual, Section 6.1: Changing the Working Directory (-C). Official GNU Documentation.

The parted utility is used to configure the newly added drive, identified here as /dev/sdc (since absolute paths are required and the current working directory is /). The first command, parted -s /dev/sdc mklabel gpt, initializes the raw drive with a GUID Partition Table (GPT) label. The second command, parted -s /dev/sdc mkpart primary ext4 1 10G, creates the actual partition named "primary" with an ext4 filesystem signature, starting at 1MB and ending at 10GB. Finally, the mkfs utility formats the newly created partition block. Passing ext4 and /dev/sdc1 creates the command mkfs.ext4 /dev/sdc1, which formally builds the ext4 filesystem on the partition so it can be mounted.

Free Software Foundation (FSF). GNU Parted User Manual. Section 2.4.5 (mklabel) and Section 2.4.6 (mkpart). Official GNU Project Documentation.

Kerrisk, M. Linux System Administration - System Manager's Manual. mkfs.ext4(8) and parted(8). Linux man-pages project.

This scenario represents a classic DNS troubleshooting situation covered in the Troubleshooting

domain of the CompTIA Linux+ V8 objectives. Although the DNS zone file has been updated correctly

on the BIND server, the system continues to resolve the domain name to an outdated IP address. This

behavior strongly indicates DNS caching rather than a configuration error in the zone file itself.

Modern Linux systems that use systemd-resolved cache DNS responses locally to improve

performance and reduce external queries. Even after a DNS record is updated on the authoritative

server, cached results may persist until the cache expires or is manually cleared. The nslookup output

showing a non-authoritative answer further confirms that the response is being served from a cache

rather than directly from the updated zone data.

The correct solution is to flush the local DNS cache so the system can retrieve the updated record

from the DNS server. The command resolvectl flush-caches clears all cached DNS entries maintained

by systemd-resolved, forcing fresh queries to authoritative name servers. This aligns directly with

Linux+ V8 documentation for resolving name resolution inconsistencies caused by stale cache

entries.

The other options are incorrect for the following reasons. systemd-resolve query www.abc.com

performs a DNS lookup but does not clear cached entries. systemd-resolve status only displays

resolver configuration and statistics. service nslcd reload reloads the Name Service LDAP daemon

and is unrelated to DNS resolution or caching.

Linux+ V8 emphasizes identifying whether issues originate from services, configuration, or cached

data. In this case, flushing the DNS cache is the correct and least disruptive corrective action.

Therefore, the correct answer is D. resolvectl flush-caches.

Part 1 (Metadata Restoration): When a logical volume is accidentally removed, the operation modifies the Volume Group (VG) metadata. Fortunately, LVM automatically creates a backup of the pre-change metadata in the /etc/lvm/archive directory. To revert the mistake, you must restore the VG to its prior state using the vgcfgrestore command pointing specifically to the archived file created just before the deletion. Using the backup directory (/etc/lvm/backup/) would be incorrect as it contains the current (post-deletion) state.

Part 2 (Volume Activation): Once the metadata is successfully restored, the logical volume configuration exists again, but LVM leaves restored volumes in an inactive state to prevent accidental data corruption. To make the volume block device available to the kernel for use, it must be explicitly activated using lvchange -a y (activate yes) targeting the logical volume.

Part 3 (Mounting): With the volume active (confirmed by the blkid output showing the block device and its XFS filesystem), the final step is to mount it to access the underlying data. The command history context on the left pane (cat /etc/fstab) implies that a persistent mount point is already configured for this volume. Running mount -a safely reads /etc/fstab and mounts all configured filesystems, including the newly recovered volume.

Red Hat Enterprise Linux 9: Configuring and Managing Logical Volumes: Section "Recovering a volume group metadata". This official vendor documentation dictates that vgcfgrestore -f /etc/lvm/archive/ is the correct administrative procedure for restoring accidentally removed logical volumes.

Linux Programmer's Manual (man-pages): * vgcfgrestore(8): "Restore volume group configuration from a file."

lvchange(8): Outlines the -a, --activate [a|e|l|s]{y|n} parameter utilized to control the availability of the logical volumes.

mount(8): Specifies that the -a parameter mounts all filesystems of a given type mentioned in fstab, providing a safe method to mount configured persistent volumes.

Live migration involves transferring a running virtual machine (VM) from one physical host to another with no downtime. For this to succeed, the destination host must be compatible with the source. The CPU architecture (e.g., x8664) must match, as the VM's running processes cannot be transferred to an incompatible instruction set. Additionally, the destination host must have enough available physical memory to accommodate the VM's allocated RAM. Without sufficient memory, the VM cannot be started on the new host.

A. The presence or type of physical USB ports on the host servers is not a requirement for a standard live migration.

B. While mismatched network speeds can affect migration performance, they do not prevent the migration from being possible.

C. Available swap space on the host is a system resource, but it is not a direct compatibility requirement for the VM state transfer.

F. For live migration, VMs typically use shared storage, so both hosts must have access to it, but their local disk storage paths do not need to match.

- Red Hat. (2024). Configuring virtual machine migration. Red Hat Enterprise Linux 9 Documentation. Section 25.1

"Migration prerequisites and limitations

" states: "The source and destination hosts must have the same CPU architecture" and "The destination host must have enough free RAM to run the migrated virtual machine."

- VMware. (2023). vSphere vMotion. VMware vSphere 8.0 Documentation. In the "vMotion Requirements" section

it lists "Compatible processors" and "Sufficient resources on the target host" as key requirements.

The initrd (initial RAM disk) is a temporary root file system loaded into memory during the Linux boot process. Its primary role is to contain a minimal set of drivers and kernel modules (e.g., for SATA, NVMe, or RAID controllers) that are necessary for the kernel to access the actual root filesystem on a physical device. Once the real root filesystem is mounted, the system pivots to it, and the initrd is unmounted and its memory is freed. This mechanism allows for a smaller, more generic kernel that can still boot on a wide variety of hardware configurations.

A. SSH is a network service for remote access, which is started much later in the boot process, long after the initrd has served its purpose.

C. System certificates and secret keys are sensitive data stored securely on the permanent root filesystem, typically in /etc/ssl/ or similar directories, not in the temporary initrd.

D. The kernel's cryptographic subsystem initializes the random number generator devices (/dev/random, /dev/urandom), not the initrd.

1. The Linux Kernel Archives. (2020). ramfs

rootfs and initramfs. kernel.org. Section: "What is initramfs?". https://www.kernel.org/doc/Documentation/filesystems/ramfs-rootfs-initramfs.txt

2. Red Hat Enterprise Linux 8 Documentation. (2023). Chapter 25. An introduction to the boot process. Section 25.3. "The initial RAM disk". https://access.redhat.com/documentation/en-us/redhatenterpriselinux/8/html/managingmonitoringandupdatingthekernel/an-introduction-to-the-boot-processmanaging-monitoring-and-updating-the-kernel#the-initial-ram-diskan-introduction-to-the-boot-process

3. Bovet

D. P.

& Cesati

M. (2005). Understanding the Linux Kernel

3rd Edition. O'Reilly Media. Chapter 19

Section "The Role of the initrd RAM Disk".

The systemd-analyze command is a utility used to investigate systemd boot performance. The blame subcommand specifically prints a list of all running units, ordered by the time they took to initialize during startup. This directly answers the administrator's need to see how long a specific service, such as NetworkManager, took to start. It provides a clear, human-readable output for performance analysis of individual services.

A. resolvectl is used to manage network name resolution and DNS settings, not to analyze service start times.

B. journalctl is used to query and display logs from the systemd journal, but it doesn't directly provide a performance analysis of start times.

C. systemctl daemon-reload reloads the systemd manager configuration files, which is not related to viewing service start-up durations.

1. Red Hat

"Red Hat Enterprise Linux 8 Documentation

" Chapter 10. Managing services with systemd

Section 10.6.2. Determining how long the boot process takes. The documentation states

"To list all running units and the time they took to initialize

type: systemd-analyze blame".

2. Freedesktop.org

"systemd-analyze man page

" The blame command is described as: "Prints a list of all running units

ordered by the time they took to initialize."

3. University of Washington

"CSE/EE 474: Introduction to Embedded Systems

" Lab 3: Linux and systemd. The courseware instructs students to use systemd-analyze blame to "see what services are taking the longest to start."