CompTIA XK0-006 Online Practice Questions and Exam Preparation

CompTIA XK0-006 Online Questions & Answers

• Question 151:

  An administrator must secure an account for a user who is going on extended leave.

  Which of the following steps should the administrator take? (Choose two)

  A. Set the user's files to immutable.
  B. Instruct the user to log in once per week.
  C. Delete the user's /home folder.
  D. Run the command passwd -l user.
  E. Change the date on the /home folder to that of the expected return date.
  F. Change the user's shell to /sbin/nologin.
  D. Run the command passwd -l user.
  F. Change the user's shell to /sbin/nologin.

  ---

  Explanation

  Comprehensive and Detailed 250 to 350 words of Explanation From Linux+ V8 documents:

  Securing dormant or temporarily unused user accounts is a best practice emphasized in the Security domain of CompTIA Linux+ V8. When a user goes on extended leave, the goal is to prevent unauthorized access while preserving the user's data and account for future use.

  The most effective approach is to disable authentication and interactive login access without deleting the account. Option D , running passwd -l user, locks the user's password by prepending an invalid character to the encrypted password in /etc/shadow. This prevents password-based authentication while retaining the account, files, and ownership information. Linux+ V8 documentation highlights password locking as a standard method for temporarily disabling accounts.

  Option , changing the user's shell to /sbin/nologin, further strengthens account security by preventing F interactive shell access entirely. Even if another authentication mechanism were attempted, the user would be denied a login shell. This is a common defense-in-depth measure and is explicitly referenced in Linux+ V8 objectives for access control and account hardening.

  The other options are incorrect or inappropriate.

  Option A (immutable files) does not prevent account access and may interfere with system operations.

  Option B defeats the purpose of securing an inactive account.

  Option C deletes user data, which is unnecessary and risky.

  Option E has no security effect, as filesystem timestamps do not control access.

  Linux+ V8 stresses that secure account management should be reversible, auditable, and minimally disruptive . Locking the password and disabling the login shell meet these criteria and are commonly used together in enterprise environments.

• Question 152:

  A systems administrator attempts to edit a file as root, but receives the following error:

  

  Which of the following commands allows the administrator to edit the file?

  A. chown root /etc/resolv.conf
  B. chattr -i /etc/resolv.conf
  C. chmod 750 /etc/resolv.conf
  D. chgrp root /etc/resolv.conf
  B. chattr -i /etc/resolv.conf

  ---

  Explanation

  This scenario involves Linux file attributes and falls under the System Management domain of the CompTIA Linux+ V8 objectives. Although the administrator is operating as the root user, the system prevents the file from being modified. This behavior indicates that standard UNIX permissions are not the root cause of the problem.

  The critical clue is provided by the lsattr /etc/resolv.conf output, which shows the immutable (i) attribute set on the file. When a file is marked immutable, it cannot be modified, deleted, renamed, or written to by any user, including root. This restriction overrides normal file permissions and ownership settings.

  The chattr command is used to modify extended file attributes on Linux filesystems such as ext4. The option - i specifically removes the immutable attribute, restoring the file's ability to be edited. Therefore, running chattr -i /etc/resolv.conf allows the administrator to open and modify the file successfully.

  The other options do not resolve the issue. chown root changes file ownership, but the file is already owned by root. chmod 750 modifies permission bits, but permissions are ignored when the immutable attribute is set. chgrp root changes the group ownership, which also has no effect when immutability is enforced.

  Linux+ V8 documentation highlights immutable files as a security and stability feature, commonly used to protect critical configuration files from accidental or unauthorized changes. Administrators must explicitly remove this attribute before making modifications.

• Question 153:

  A Linux administrator tries to install Ansible in a Linux environment. One of the steps is to change the owner and the group of the directory /opt/Ansible and its contents.

  Which of the following commands will accomplish this task?

  A. groupmod -g Ansible -n /opt/Ansible
  B. chown -R Ansible:Ansible /opt/Ansible
  C. usermod -aG Ansible /opt/Ansible
  D. chmod -c /opt/Ansible
  B. chown -R Ansible:Ansible /opt/Ansible

  ---

  Explanation

  Comprehensive and Detailed Explanation From Exact Extract:

  The chown command is used to change the owner and group of files and directories. The -R (recursive) flag ensures that all contents within the directory are also updated. The correct syntax is chown -R owner:group directory. So, chown -R Ansible:Ansible /opt/Ansible will change the owner and group for /opt/Ansible and everything inside it to "Ansible".

  Other options:

  A. groupmod is used to modify group properties, not ownership of directories or files.

  C. usermod is for modifying user properties or group memberships.

  D. chmod changes permissions, not owner/group.

  CompTIA Linux+ Study Guide: Exam XK0-006, Sybex, Chapter 6: "User and Group Management", Section:"Managing File Ownership and Permissions" CompTIA Linux+ XK0-006 Objectives, Domain 1.0: System Management

• Question 154:

  Which of the following best describes journald?

  A. A system service that collects and stores logging data
  B. A feature that creates crash dumps in case of kernel failure
  C. A service responsible for keeping the filesystem journal
  D. A service responsible for writing audit records to a disk
  A. A system service that collects and stores logging data

  ---

  Explanation

  journald, part of systemd , is the core logging service in modern Linux systems and is covered under Linux+ V8 logging and monitoring objectives.

  The correct description is A. systemd-journald collects, stores, and indexes logging data from the kernel, system services, and applications. Logs are stored in a structured, binary format and can be queried using journalctl. Journald supports metadata tagging, log filtering, and centralized logging integration.

  Option B refers to kernel crash dump mechanisms like kdump.

  Option C describes filesystem journaling (such as ext4 journaling). Option D refers to auditd, which manages security audit logs.

  Linux+ V8 documentation clearly distinguishes journald from other logging and auditing services.

• Question 155:

  A systems administrator receives reports from users who are having issues while trying to modify newly created files in a shared directory. The administrator sees the following outputs:

  

  Which of the following provides the best resolution to this issue?

  A. Adding a setuid bit to the user in the shared folder
  B. Manually changing the group of the newly created files
  C. Changing all directory contents to be writable and readable for everyone
  D. Adding a setgid bit to the group in the shared folder
  D. Adding a setgid bit to the group in the shared folder

  ---

  Explanation

  This scenario involves shared directory collaboration , which is a common system management task covered in the CompTIA Linux+ V8 objectives. The key issue is that users can create files in the shared directory, but other users in the same group cannot modify those files. This behavior is directly related to group ownership inheritance . By default, when a user creates a file or directory, it is owned by the user and assigned the user's primary group , not necessarily the group of the parent directory. As shown in the output, files inside /share are owned by different groups (student, student2, student3), which prevents other group members from modifying them, even though the parent directory is group-writable.

  The correct solution is to set the setgid (set group ID) bit on the shared directory , making option D correct. When the setgid bit is applied to a directory, all newly created files and subdirectories inherit the group ownership of the parent directory , rather than the creator's primary group.

  This ensures consistent group ownership and allows all members of the shared group to collaborate effectively.

  The other options are incorrect or poor practice. Option A (setuid) is intended for executables, not directories. Option B requires constant manual intervention and does not scale. Option C weakens security by granting write access to all users, violating the principle of least privilege.

  Linux+ V8 documentation explicitly recommends using the setgid bit on shared directories to manage collaborative access securely and efficiently.

• Question 156:

  After system startup, the X Window System GUI login interface is not displaying.

  Which of the following commands ensures that the GUI is started during the system startup process?

  A. systemctl isolate graphical.target
  B. systemctl unmask xwindow.service
  C. systemctl enable xwindow.service
  D. systemctl set-default graphical.target
  D. systemctl set-default graphical.target

• Question 157:

  Which of the following commands should an administrator use to convert a KVM disk file to a different format?

  A. qemu-kvm
  B. qemu-ng
  C. qemu-io
  D. qemu-img
  D. qemu-img

  ---

  Explanation

  Virtualization management is part of Linux system administration and is included in Linux+ V8 objectives. KVM virtual machines commonly use disk image formats such as qcow2, raw, or vmdk. Converting between these formats is a routine administrative task.

  The correct tool for disk image conversion is qemu-img . This utility allows administrators to create, convert, resize, and inspect virtual disk images. For example, converting a qcow2 image to raw format can be accomplished using qemu-img convert. This capability is explicitly referenced in Linux+ V8 documentation related to virtualization tooling.

  The other options are incorrect. qemu-kvm refers to the hypervisor component, not disk manipulation. qemu- ng is not a valid QEMU utility. qemu-io is used for low-level I/O testing and debugging, not image format conversion.

• Question 158:

  An administrator needs to verify the user ID, home directory, and assigned shell for the user named "accounting.

  " Which of the following commands should the administrator use to retrieve this information?

  A. getent passwd accounting
  B. id accounting
  C. grep accounting /etc/shadow
  D. who accounting
  A. getent passwd accounting

  ---

  Explanation

  User account information is centrally stored in the system's account databases, and Linux+ V8 emphasizes the use of standard tools to query this data safely and consistently.

  The getent passwd accounting command retrieves the user's entry from the passwd database , which may be sourced from local files or network services such as LDAP. This entry includes the username, user ID (UID), group ID (GID), home directory, and assigned login shell. Therefore, option A provides all the requested information in a single command.

  Option B , id accounting, displays the UID and group memberships but does not show the home directory or assigned shell. Option C is incorrect because /etc/shadow contains password hashes and expiration data, not shell or home directory information. Option D , who accounting, only shows login sessions and does not provide account configuration details.

  Linux+ V8 documentation highlights getent passwd as the preferred method for retrieving comprehensive user account information because it works across different authentication backends.

• Question 159:

  User1 reports "access denied" errors while trying to execute app. Given the following outputs:

  

  Which of the following options will remediate this issue?

  A. Providing execute permissions to user1 in the ACL
  B. Modifying the permissions for others to grant read, write, and execute
  C. Adding user1 to the wheel group
  D. Moving app to a different folder
  A. Providing execute permissions to user1 in the ACL

  ---

  Explanation

  According to the output of getfacl app, user1 has only "rw" (read and write) permissions, but lacks "x" (execute). Without execute permission, user1 cannot run the file. To allow user1 to execute app, you must update the ACL to add execute permission (e.g., setfacl -m u:user1:rwx app). Modifying "others" permissions (option B) is not secure or necessary, adding user1 to the wheel group (option C) is unrelated, and moving the file (option D) does not resolve permission issues.

  CompTIA Linux+ Study Guide: Exam XK0-006, Sybex, Chapter 7: "Securing Linux Systems", Section:"Managing File and Directory Permissions and ACLs"

  CompTIA Linux+ XK0-006 Objectives, Domain 3.0: Security

• Question 160:

  Which of the following options represents disk mirroring?

  A. RAID 0
  B. RAID 1
  C. RAID 5
  D. RAID 6
  B. RAID 1