LPIC-2 Linux Kernel and System Startup — Timed 30 Questions

Question 1

A system administrator needs to ensure that a custom kernel module loads automatically at boot. The module is named 'my_driver' and is built for the current kernel. Which configuration file should be modified to ensure the module loads automatically?

Accepted Answer

Add a configuration file in /etc/modules-load.d/. Option C is correct because systemd-based Linux distributions use /etc/modules-load.d/ to specify kernel modules that should be loaded automatically at boot. Placing a configuration file (e.g., my_driver.conf) containing the module name 'my_driver' in this directory instructs systemd-modules-load.service to load the module during early boot. This is the modern, distribution-agnostic method for ensuring a custom kernel module loads automatically.

Answer

Add the insmod command in /etc/rc.local

Answer

Add the module name to /etc/modules.conf

Answer

Add a configuration file in /etc/modprobe.d/

Question 2

During boot, the kernel outputs a message indicating that a required device driver is not found. Which command can be used to rebuild the initramfs to include the missing driver?

Accepted Answer

dracut. Dracut is the standard tool for building initramfs images on modern Red Hat-based distributions (RHEL, CentOS, Fedora). When a required kernel driver is missing during boot, you can use `dracut --force` to rebuild the initramfs, which will automatically include the currently loaded kernel modules and any specified in configuration files. This ensures the missing driver is available early in the boot process.

Answer

mkinitrd

Answer

grub-mkconfig

Answer

mkinitcpio

Question 3

A server with a custom kernel fails to boot after a kernel update. The system displays a kernel panic: 'VFS: Unable to mount root fs on unknown-block(0,0)'. The root filesystem is on an LVM volume. What is the most likely cause?

Accepted Answer

The initramfs is missing LVM support.. The kernel panic 'VFS: Unable to mount root fs on unknown-block(0,0)' indicates the kernel cannot locate the root filesystem. Since the root filesystem resides on an LVM volume, the initramfs must contain LVM tools and modules to activate the volume group and logical volumes before the kernel can mount the root. If the initramfs was not rebuilt after the kernel update, it will lack LVM support, causing the boot failure.

Answer

The GRUB configuration is pointing to the wrong kernel partition.

Answer

The kernel does not have the necessary device drivers compiled in.

Answer

The root filesystem is formatted with an unsupported filesystem.

Question 4

A system administrator wants to change the default kernel boot parameters temporarily to debug a boot issue. Which step should be taken at the GRUB menu to modify kernel parameters for the next boot only?

Accepted Answer

Select the kernel entry and press 'e' to edit the boot parameters.. Option A is correct because pressing 'e' at the GRUB menu allows you to edit the boot parameters for the selected kernel entry temporarily. This modifies the kernel command line only for the current boot, without persisting changes to disk. After editing, pressing Ctrl+X or F10 boots the system with the modified parameters, making it ideal for debugging boot issues.

Answer

Edit /etc/default/grub and run update-grub to apply changes.

Answer

Press 'c' to enter the command line and modify parameters.

Answer

Press 'Esc' to access the advanced options menu.

Question 5

After installing a new kernel, the system administrator notices that the system boots to the old kernel by default. Which command should be used to update the GRUB configuration to boot the new kernel?

Accepted Answer

update-grub. The `update-grub` command (which is a wrapper for `grub-mkconfig -o /boot/grub/grub.cfg`) scans the installed kernels and regenerates the GRUB configuration file, automatically setting the newest kernel as the default boot entry. This ensures the system boots the newly installed kernel on the next reboot.

Answer

grub-install

Answer

mkinitrd

Answer

grub-set-default

Question 6

A developer has compiled a custom kernel with a new feature. The kernel modules are installed in /lib/modules/$(uname -r)/. However, when the system boots, the kernel fails to load some modules with 'Exec format error'. What is the most likely cause?

Accepted Answer

The modules were compiled against a different kernel version.. The 'Exec format error' indicates that the kernel module binary is incompatible with the running kernel. This most commonly occurs when modules are compiled against a different kernel version (e.g., different kernel source tree or configuration), as the module's vermagic string must exactly match the kernel's vermagic. The kernel's module loader checks this version magic before loading; a mismatch causes the exec format error.

Answer

The kernel configuration has disabled module loading.

Answer

The modules have incorrect file permissions.

Answer

The modules are not properly ordered in the dependency file.

Question 7

A system administrator needs to find out which kernel parameters were passed at boot time. Which command displays the kernel boot parameters?

Accepted Answer

cat /proc/cmdline. The correct command is `cat /proc/cmdline` because the Linux kernel stores the boot parameters (also known as the kernel command line) passed by the bootloader (e.g., GRUB) in the virtual file `/proc/cmdline`. Reading this file directly displays the exact parameters used during boot, such as `root=`, `quiet`, or `splash`.

Answer

dmesg

Answer

lsmod

Answer

cat /proc/version

Question 8

Which TWO of the following commands are used to manage kernel modules? (Select TWO.)

Accepted Answer

insmod. B (insmod) is correct because it directly inserts a kernel module into the running kernel, though it does not resolve dependencies automatically. C (modprobe) is correct because it is the recommended tool for managing kernel modules, as it automatically loads dependencies and handles module parameters via configuration files in /etc/modprobe.d/.

Answer

lsmod

Answer

rmmod

Answer

depmod

Question 9

Which THREE factors can cause a kernel panic during boot? (Select THREE.)

Accepted Answer

Corrupted kernel image. A corrupted kernel image (Option B) is a direct cause of kernel panic during boot because the bootloader (e.g., GRUB) loads the kernel into memory, and if the binary is damaged (e.g., due to disk errors or incomplete update), the CPU will attempt to execute invalid instructions, triggering a fatal kernel panic. The kernel performs integrity checks early in startup, and any mismatch between expected and actual code will halt the system with a panic message.

Answer

Too many kernel modules loaded

Answer

Filesystem errors on the root partition

Question 10

A company runs a critical web server on a custom-built Linux distribution. The server has been stable for months, but after a recent kernel update from version 5.10 to 5.15, the server experiences intermittent crashes. The crashes occur under heavy load and are accompanied by kernel oops messages mentioning a NULL pointer dereference in a network driver. The network driver is a third-party module that was compiled against the old kernel. The system administrator has recompiled the module against the new kernel, but the crashes persist. The server has 64 GB of RAM and uses a bonded network interface with two 10 GbE NICs. The kernel oops trace points to a function in the bonding driver. Which of the following is the most likely cause of the crashes?

Accepted Answer

Check the kernel configuration changes between versions 5.10 and 5.15 that affect the bonding driver.. Option C is correct because the crashes persist after recompiling the third-party network driver, and the oops trace points to the bonding driver. This indicates that the issue is likely due to changes in the kernel's internal APIs or data structures between versions 5.10 and 5.15 that affect the bonding driver, not the third-party module. The bonding driver is part of the kernel itself, so it must be compatible with the new kernel version; checking kernel configuration changes (e.g., modifications to `struct net_device`, bonding sysfs interfaces, or locking mechanisms) is the appropriate next step.

Answer

Increase the system memory to reduce memory pressure.

Answer

Update the firmware on the network interface cards.

Answer

Recompile the network driver module with debugging enabled.

Question 11

A systems administrator is troubleshooting a server that fails to boot after a kernel upgrade. The boot process hangs at the stage where the kernel attempts to mount the root filesystem. Which of the following is the most likely cause?

Accepted Answer

The root= parameter in the kernel command line points to a non-existent device.. When the kernel fails to mount the root filesystem during boot, the most common cause is an incorrect or missing `root=` parameter in the kernel command line. This parameter specifies the device (e.g., `/dev/sda1` or `UUID=...`) that the kernel should mount as the root filesystem; if it points to a non-existent device, the kernel cannot proceed past the mount stage, resulting in a hang or kernel panic.

Answer

The root filesystem is formatted with an unsupported filesystem type.

Answer

The initrd image is missing from the /boot partition.

Answer

The GRUB bootloader is not installed on the MBR.

Question 12

Which TWO of the following are valid methods to modify kernel parameters at runtime without rebooting?

Accepted Answer

Writing to files in /proc/sys/ using echo. Option C is correct because the /proc/sys/ directory exposes kernel tunable parameters as virtual files, and writing a new value to these files (e.g., echo 1 > /proc/sys/net/ipv4/ip_forward) immediately changes the corresponding kernel parameter at runtime without requiring a reboot. This is a direct interface to the kernel's sysctl mechanism.

Answer

Using modprobe to load kernel modules with parameters

Answer

Editing /etc/sysctl.conf and running sysctl --system

Answer

Adding parameters to the kernel command line in /etc/default/grub

Question 13

Refer to the exhibit. The system boots successfully, but the root filesystem is mounted as read-only even after the boot process completes. Which of the following is the most likely cause?

Accepted Answer

The kernel command line contains the 'ro' parameter, which remains in effect.. The 'ro' parameter in the kernel command line instructs the kernel to mount the root filesystem as read-only during early boot. Even after the boot process completes, if no subsequent remount (e.g., via init scripts or systemd) is performed, the root filesystem remains read-only. This is the most direct and common cause of a root filesystem staying read-only after boot.

Answer

The root device /dev/mapper/vg-root does not exist.

Answer

The root filesystem is damaged and forces read-only mount.

Answer

SELinux is enforcing and prevents write access to the root filesystem.

Question 14

You are a systems administrator for a company that runs a critical web server on a Linux system. The server has been running stably for months, but after a recent kernel update from version 5.10.0-8 to 5.10.0-9, the server fails to boot. The boot process starts, but after the kernel loads, the system hangs with no output on the console. You have physical access to the server and can interrupt the boot process. The server uses GRUB 2 as the bootloader and the root filesystem is on an LVM logical volume. The previous kernel (5.10.0-8) is still present in /boot. Which of the following is the best course of action to restore the server to a working state?

Accepted Answer

Interrupt the boot process at GRUB, select the advanced options, and boot the old kernel 5.10.0-8.. The server fails to boot after a kernel update, but the previous kernel is still present in /boot. By interrupting GRUB 2 at boot, selecting 'Advanced options for Ubuntu' (or similar), and booting the old kernel 5.10.0-8, you bypass the problematic new kernel without modifying the bootloader or filesystem. This is the fastest, least invasive recovery method because GRUB 2 automatically detects and lists all installed kernels in /boot, including the previous one.

Answer

Reinstall GRUB from a live CD to fix the bootloader configuration.

Answer

Boot from a live CD, chroot into the system, and reinstall the new kernel package.

Answer

Boot from a live CD, chroot into the system, and rebuild the initrd for the new kernel.

Question 15

A system administrator needs to add a kernel module to the kernel at runtime without recompiling. Which command should be used?

Accepted Answer

insmod. The correct command is `insmod` because it inserts a kernel module into the running kernel without recompiling. It directly loads the specified module file (e.g., `.ko` file) into the kernel, making it available immediately. This is the standard low-level command for adding a single module at runtime.

Answer

rmmod

Answer

modprobe

Answer

depmod

Question 16

During boot, the kernel panics with 'VFS: Unable to mount root fs on unknown-block(0,0)'. Which of the following is the most likely cause?

Accepted Answer

The kernel lacks the driver for the storage controller.. The error 'VFS: Unable to mount root fs on unknown-block(0,0)' indicates the kernel cannot find a driver for the block device containing the root filesystem. This most commonly occurs when the kernel lacks the necessary storage controller driver (e.g., for SATA, NVMe, or SCSI controllers), often because the driver was built as a module and not included in the initramfs or compiled into the kernel.

Answer

The kernel image is corrupted.

Answer

The init process is missing.

Answer

The root filesystem is formatted with an unsupported filesystem.

Question 17

A technician is troubleshooting a system that fails to boot after adding a new SATA SSD and editing /etc/fstab. The error message is 'Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,17)'. What is the most likely issue?

Accepted Answer

The root filesystem UUID in /etc/fstab is incorrect.. The error 'unknown-block(8,17)' indicates the kernel cannot find the root filesystem. Block device 8,17 corresponds to /dev/sdb1 (major 8 for SCSI/SATA, minor 17). The most likely cause is an incorrect UUID in /etc/fstab, which prevents the system from mounting the root partition. The kernel can see the device, but the mount fails because the UUID specified does not match any available partition.

Answer

The kernel image is missing.

Answer

The kernel lacks SATA driver support.

Answer

The initramfs was not regenerated after adding the disk.

Question 18

Arrange the steps to configure a Linux server as an NFS client that mounts a remote export.

Question 19

Order the steps to configure a Linux system as an SSH server with key-based authentication.

Question 20

Match each Linux filesystem feature to its description.