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

w shows currently logged-in users and their processes.

man shows manual pages.

id shows UID/GID for current user.

host is a DNS lookup tool.

Reference:

CompTIA Linux+ XK0-005 Study Guide, Domain 5.0 – Troubleshooting

“Use the w command to list current users and their activities.”

The chgrp command is used to change the group ownership of files and directories. By using this

command, the administrator can assign the files in the newly created directory to the human

resources group, which will allow the users in that group to access them. The other commands are

not relevant for this task. For example:

chattr is used to change the file attributes, such as making them immutable or append-only1.

chage is used to change the password expiration information for a user account2.

chcon is used to change the security context of files and directories, which is related to SELinux3.

:

The CompTIA Linux+ Certification Exam Objectives mention that the candidate should be able to

“manage file and directory ownership and permissions” as part of the Hardware and System

Configuration domain4.

The web search result 2 explains how to use the chgrp command with examples.

The web search result 3 compares the chmod and chgrp commands and their effects on file

permissions.

The command visudo -c can be used to check the validity of the sudo rules in the /etc/sudoers file.

The visudo command is a tool for editing and validating the /etc/sudoers file, which defines the rules

for the sudo command. The -c option checks the syntax and logic of the file and reports any errors or

warnings. The command visudo -c will verify the sudo rules and help the administrator avoid any

mistakes. This is the correct command to use for this task. The other options are incorrect because

they either do not check the validity of the file (test, sudo, or cat) or do not exist (sudo vi

check). : CompTIA Linux+ (XK0-005) Certification Study Guide, Chapter 18: Securing Linux Systems,

page 546.

File attributes are preventing file modification, which is causing the error message. The output

of lsattr /home/user/data.txt shows that the file has the immutable attribute (i) set, which means

that the file cannot be changed, deleted, or renamed. The command setfacl -b

/home/user/data.txt tries to remove the ACL from the file, but fails because of the immutable

attribute. The administrator needs to remove the immutable attribute first by using the

command chattr -i /home/user/data.txt and then try to remove the ACL again. The other options are

incorrect because they are not supported by the outputs. The administrator is using a highly

privileged account, as shown by the # prompt. The filesystem is mounted with the correct options, as

shown by the output of mount | grep /home. SELinux file context is not denying the ACL changes, as

shown by the output of ls -Z /home/user/data.txt. : CompTIA Linux+ (XK0-005) Certification Study

Guide, Chapter 11: Managing Files and Directories, pages 357-358.

The command dd if=/dev/sdc1 of=/dev/sdd1 copies the data from the input file (if) /dev/sdc1 to the

output file (of) /dev/sdd1, byte by byte. This is the correct way to clone a partition. The other options

are incorrect because they either compress the data (tar -cvzf), synchronize the files (rsync), or copy

the files over a network (scp), which are not the same as cloning a partition. : CompTIA Linux+ (XK0-

005) Certification Study Guide, Chapter 10: Managing Storage, page 321.

The system has reached its maximum permitted throughput, therefore iowait is increasing. The output of iostat -x shows that the device sda has an average throughput of 44.01 MB/s, which is equal to the disk maximum throughput of 44 Mbps. The output also shows that the device sda has an average iowait of 99.99%, which means that the CPU is waiting for the disk to complete the I/O requests. This indicates that the disk is the bottleneck and the system is slow due to the high iowait. The other options are incorrect because they are not supported by the outputs. The system has not reached its maximum IOPS, as the device sda has an average IOPS of 563.50, which is lower than the disk maximum IOPS of 690. The system is not mostly idle, as the output of top shows that the CPU is 100% busy. The system does not have a partitioned disk, as the output of lsblk shows that the device sda has only one partition sda1. : CompTIA Linux+ (XK0-005) Certification Study Guide, Chapter 17: Optimizing Linux Systems, pages 513-514.

The command gzip can extract files that are compressed with the gzip format, which has the

extension .gz. This is the correct command to use for the software package. The other options are

incorrect because they either compress files (bzip2 -z), unzip files that are compressed with the zip

format (unzip -v or funzip), or have the wrong options (-v or -z instead of -d). : CompTIA Linux+ (XK0-

005) Certification Study Guide, Chapter 11: Managing Files and Directories, page 353.

The user has the wrong shell assigned to the account, which is causing the issue. The output 1 shows

that the user’s shell is set to /bin/false, which is not a valid shell and will prevent the user from

logging in. The output 2 shows that the user’s home directory has the correct permissions (drwxr-xr-

x), and the output 3 shows that the user entered the correct password and was accepted by the SSH

daemon, but the session was closed immediately due to the invalid shell. The other options are

incorrect because they are not supported by the outputs. : CompTIA Linux+ (XK0-005) Certification

Study Guide, Chapter 13: Managing Network Services, page 413.

The command that will satisfy the requirement of having all files that are created by the user named

web have read-only permissions by the owner is echo “umask 377” >> /home/web/.bashrc. This

command will append the umask 377 command to the end of the .bashrc file in the web user’s home

directory. The .bashrc file is a shell script that is executed whenever a new interactive shell session is

started by the user. The umask command sets the file mode creation mask, which determines the

default permissions for newly created files or directories by subtracting from the maximum

permissions (666 for files and 777 for directories). The umask 377 command means that the user

does not want to give any permissions to the group or others (3 = 000 in binary), and only wants to

give read permission to the owner (7 - 3 = 4 = 100 in binary). Therefore, any new file created by the

web user will have read-only permission by the owner (400) and no permission for anyone

else. : CompTIA Linux+ (XK0-005) Certification Study Guide, Chapter 8: Managing Users and

Groups; Umask Command in Linux | Linuxize

The command restorecon -R -v /var/www/html will best resolve the issue. The issue is caused by the

incorrect SELinux context of the web server files under the /var/www/html directory. The output of ls

-Z /var/www/html shows that the files have the type user_home_t, which is not allowed for web

content. The command restorecon restores the default SELinux context of files based on the policy

rules. The options -R and -v are used to apply the command recursively and verbosely. This command

will change the type of the files to httpd_sys_content_t, which is the correct type for web content.

This will allow the web server to access the files and serve the pages to the browser. The other

options are incorrect because they either disable SELinux entirely (sed -i

's/SELINUX=enforcing/SELINUX=disabled/' /etc/selinux/config or setenforce 0), which is not a good

security practice, or enable an unnecessary boolean (setsebool -P httpd_can_network_connect_db

on), which is not related to the issue. : CompTIA Linux+ (XK0-005) Certification Study Guide, Chapter

18: Securing Linux Systems, page 535.

The command semanage port -a -t http_port_t -p tcp 6379 adds a new port definition to the SELinux

policy and assigns the type http_port_t to the port 6379/tcp. This allows the web application to run

on this port and accept connections from users. This is the correct way to resolve the issue. The other

options are incorrect because they either delete a port definition (-d), use the wrong protocol

(top instead of tcp), or list the existing port definitions (-l). : CompTIA Linux+ (XK0-005) Certification

Study Guide, Chapter 18: Securing Linux Systems, page 535.

The most probable cause of the connectivity issue is that the network interface cable is not

connected to a switch. This can be inferred from the output of the ip link list dev eth0 command,

which shows that the network interface eth0 has the NO-CARRIER flag set. This flag indicates that

there is no physical link detected on the interface, meaning that the cable is either unplugged or

faulty. The other options are not valid causes of the issue. The address ac:00:11:22:33:cd is a valid

Ethernet address, as it follows the format of six hexadecimal octets separated by colons. The

Ethernet broadcast address should be ff:ff:ff:ff:ff:ff, which is the default value for all interfaces. The

network interface eth0 is not using an old kernel module, as it shows the UP flag, which indicates

that the interface is enabled and ready to transmit data. : CompTIA Linux+ (XK0-005) Certification

Study Guide, Chapter 14: Managing Networking

https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/Linux+_XK0-005/page_145_img_1.jpg

To create an appropriate device label, format and create an ext4 file system on the new partition, you

can use the following commands:

To create a GPT (GUID Partition Table) label on the new drive /dev/sdc, you can use the parted

command with the -s option (for script mode), the device name (/dev/sdc), the mklabel command,

and the label type (gpt). The command is:

parted -s /dev/sdc mklabel gpt

To create a primary partition of 10 GB on the new drive /dev/sdc, you can use the parted command

with the -s option, the device name (/dev/sdc), the mkpart command, the partition type (primary),

the file system type (ext4), and the start and end points of the partition (1 and 10G). The command

is:

parted -s /dev/sdc mkpart primary ext4 1 10G

To format and create an ext4 file system on the new partition /dev/sdc1, you can use the mkfs

command with the file system type (ext4) and the device name (/dev/sdc1). The command is:

mkfs.ext4 /dev/sdc1

You can verify that the new partition and file system have been created by using the lsblk command,

which will list all block devices and their properties.

part for

detailed answer of

each part.

Explanation:

Part 1

Here is the step-by-step command construction process:

1. Move the private key (likely named server1 based on the provided details) to the .ssh directory:

mv ~/server1 ~/.ssh/id_rsa

This command moves the private key (assuming it's named server1) from the home directory (~) to

the .ssh directory and renames it to id_rsa (which is the default SSH private key file name).

2. Set the correct permissions for the private key file:

chmod 600 ~/.ssh/id_rsa

The private key file should be readable and writable only by the owner to maintain security.

3. Connect to the server using the private key and the correct port (2222):

ssh -i ~/.ssh/id_rsa -p 2222 admin@server1

This command tells ssh to use the specified private key (-i ~/.ssh/id_rsa), connect on port 2222 (-p

2222), and log in as the admin user on server1.

Part 2: Setting File Permissions

The correct command to set the file permissions based on the screenshots would likely involve using

chmod. Here is the command to set permissions correctly:

chmod 600 ~/.ssh/id_rsa

This restricts the private key's permissions so that only the user can read and write it.

Part 3: Setting Ownership

If ownership needs to be set, the command would look like this:

chown comptia:comptia ~/.ssh/id_rsa

This command ensures that the file is owned by the correct user (comptia) and the correct group

(comptia).

In part 4, it asks you to select the proper file for editing to enable remote server access. Based on

standard SSH configuration requirements, the proper file to edit for remote server access would be

~/.ssh/config.

Here’s why:

~/.ssh/config: This file allows you to set up configuration options for different hosts, including

specifying ports, user names, and the identity file (private key). You would add the necessary

configuration for server1 to this file for easier access.

Other options:

~/.ssh/authorized_keys: This file lists public keys that are authorized to log in to the local system. It's

not meant for configuring remote access to another server.

~/.ssh/known_hosts: This file stores the host keys of servers you’ve connected to. It doesn’t allow for

editing remote access settings.

~/.ssh/server1: This seems like a private key file or another custom file, but it’s not typically used to

configure SSH options.

For configuring access to server1 on port 2222, you would add a block like this to the ~/.ssh/config

file:

Host server1

HostName server1

Port 2222

User admin

IdentityFile ~/.ssh/id_rsa

below.

Explanation:

yum install httpd

systemct1 --now enable httpd

systemct1 status httpd

netstat -tunlp | grep 80

pkill

systemct1 restart httpd

systemct1 status httpd

Production web servers should use certificates issued by trusted Certificate Authorities (CAs).

B is correct: This describes the proper process—generate a private key, create a CSR (Certificate

Signing Request), send it to a CA, and use the returned signed certificate for HTTPS.

Incorrect Options:

A: SSH keys are for SSH, not HTTPS/TLS.

C: Self-signed certs are insecure in production.

D: Irrelevant to HTTPS; /dev/random is used for entropy generation.

Reference:

CompTIA Linux+ XK0-005 Study Guide, Chapter 11

man openssl

The best commands to use to generate a list of rogue process names that have a TCP listener on a

network interface are

A. netstat -antp | grep LISTEN and

B. lsof -iTCP | grep LISTEN. These commands

will show the process ID (PID) and name of the processes that are listening on TCP ports, which can

be used to identify any suspicious or unauthorized processes. The other commands are either not

specific enough, not valid, or not relevant for this task. For example:

C . lsof -i:22 | grep TCP will only show the processes that are listening on port 22, which is typically

used for SSH, and not any other ports.

D . netstat -a | grep TCP will show all the TCP connections, both active and listening, but not the

process names or IDs.

E . nmap -p1-65535 | grep -i tcp will scan all the TCP ports on the local host, but not show the process

names or IDs.

F. nmap -sS 0.0.0.0/0 will perform a stealth scan on the entire internet, which is not only impractical,

but also illegal in some countries.

The correct sequence of commands to expand a volume group using a new disk is fdisk, pvcreate,

vgextend. The fdisk command can be used to create a partition on the new disk with the type 8e

(Linux LVM). The pvcreate command can be used to initialize the partition as a physical volume for

LVM. The vgextend command can be used to add the physical volume to an existing volume group.

The partprobe command can be used to inform the kernel about partition table changes, but it is not

necessary in this case. The vgcreate command can be used to create a new volume group, not

expand an existing one. The lvextend command can be used to extend a logical volume, not a volume

group. The lvcreate command can be used to create a new logical volume, not expand a volume

group. The mkfs command can be used to create a filesystem on a partition or a logical volume, not

expand a volume group. : CompTIA Linux+ (XK0-005) Certification Study Guide, Chapter 14:

Managing Disk Storage, pages 462-463.