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

Question 1

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 2

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 3

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

Accepted Answer

insmod. insmod (B) is correct because it directly inserts a kernel module into the running kernel by loading the specified .ko file, making it a core module-management command. modprobe (C) is also correct because it intelligently loads or removes modules while automatically resolving and loading any dependent modules via the modules.dep database. The other options, while related to modules, are not the two commands typically cited for managing (loading) modules in this context: lsmod (A) only lists currently loaded modules, rmmod (D) only removes a module, and depmod (E) only regenerates the module dependency file.

Answer

lsmod

Answer

rmmod

Answer

depmod

Question 4

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.. 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 5

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/ pseudo-filesystem exposes kernel parameters as writable files, so commands like echo 1 > /proc/sys/net/ipv4/ip_forward change the running kernel's behavior immediately without a reboot. Option D is correct because the sysctl command (e.g., sysctl -w net.ipv4.ip_forward=1) is the standard user-space utility that writes to those same /proc/sys entries, applying the change at runtime. Option A is not correct because modprobe loads or unloads kernel modules and passes module parameters; it does not modify existing kernel tunables. Option B is not correct because editing /etc/sysctl.conf only changes the persistent configuration file, and sysctl --system applies it at boot or when explicitly invoked, but the question asks about runtime modification methods themselves. Option E is not correct because kernel command-line parameters in /etc/default/grub only take effect after regenerating the bootloader configuration and rebooting.

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 6

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 most likely cause is that the kernel command line contains the 'ro' parameter. This parameter explicitly requests a read-only root mount, which persists after boot if no remount (e.g., by init or systemd) is performed. Option C is not the most likely because a damaged filesystem usually causes boot failures or drops to emergency mode, not a successful boot with a read-only root.

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 7

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 8

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

Accepted Answer

modprobe. The standard command to add a kernel module to the running kernel is `modprobe`, which loads the specified module and automatically resolves and loads any dependencies. `insmod` can also insert a module at runtime, but it requires the exact path to the `.ko` file and does not handle dependencies, so it is the lower-level alternative rather than the best answer. `rmmod` removes a module, and `depmod` regenerates module dependency information; neither adds a module.

Answer

insmod

Answer

rmmod

Answer

depmod

Question 9

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 10

Match each Linux boot component to its role.

Accepted Answer

GRUB: Bootloader that loads the kernel and initramfs.. The correct matches are: GRUB loads kernel and initramfs; initramfs is a temporary root filesystem; kernel manages hardware and processes; init/systemd is the first process. Common confusions include MBR being mistaken for a kernel loader and initramfs for GRUB config storage.

Answer

MBR: Loads the Linux kernel.

Answer

initramfs: Contains the GRUB configuration.

Question 11

A system administrator needs to include a custom kernel module in the initramfs to support a root filesystem on a USB device. Which command should be used to rebuild the initramfs with the updated kernel?

Accepted Answer

dracut. Dracut is the correct tool for rebuilding the initramfs on modern Red Hat-based distributions (e.g., RHEL, CentOS, Fedora). It automatically detects and includes kernel modules required for the root filesystem, including those for USB storage devices, and regenerates the initramfs image with the updated kernel module.

Answer

update-initramfs

Answer

mkinitrd

Answer

grub-mkconfig

Question 12

A system administrator compiled a custom kernel module for a new hardware device. After copying the .ko file to /lib/modules/$(uname -r)/, the module is not loading automatically at boot. What is the most likely cause?

Accepted Answer

The module is blacklisted in /etc/modprobe.d/.. A blacklist entry in /etc/modprobe.d/ explicitly prevents the kernel from loading the module at boot, regardless of its presence in /lib/modules/$(uname -r)/. The modprobe system reads these configuration files during early boot and skips any module listed with a 'blacklist' directive, which is the most likely cause when a module is present but fails to load automatically.

Answer

The module needs to be added to /etc/modules.

Answer

The module has a dependency error.

Answer

The kernel version does not match the module.

Question 13

Which three steps are required to build a kernel module from source located outside the kernel tree? (Choose three.)

Accepted Answer

Run 'make modules_install'.. 'make modules_install' copies the compiled kernel module (.ko file) to the appropriate directory under /lib/modules/$(uname -r)/, making it available for loading. This step is essential after building a module from external source to ensure it is installed in the correct location for the running kernel.

Answer

Edit the kernel configuration.

Answer

Use the kernel's top-level Makefile.

Question 14

A system administrator has multiple kernel modules that depend on each other. Module A must be loaded before module B. How can this dependency be ensured automatically when using modprobe?

Accepted Answer

Add options module_a softdep=module_b to /etc/modprobe.d/. The `softdep` directive in a modprobe configuration file (e.g., `/etc/modprobe.d/*.conf`) allows you to declare a soft dependency where one module should be loaded before another, without creating a hard dependency in the module symbol table. When `modprobe` processes this directive, it ensures that module A is loaded before module B automatically, even if there is no explicit symbol dependency between them.

Answer

Use depmod to generate dependency information

Answer

Use insmod to load module A first, then module B in a startup script

Answer

Add module B to the /etc/modules file

Question 15

After installing a new kernel on a system using GRUB2, which command should be run to update the boot menu configuration file?

Accepted Answer

grub-mkconfig -o /boot/grub/grub.cfg. After installing a new kernel on a system using GRUB2, the boot menu configuration file must be regenerated to include the new kernel entry. The command `grub-mkconfig -o /boot/grub/grub.cfg` reads the configuration snippets in `/etc/default/grub` and scripts in `/etc/grub.d/`, then writes the updated GRUB2 configuration to the specified output file (`/boot/grub/grub.cfg`). This is the standard method on most Linux distributions that use GRUB2 (e.g., Debian, Ubuntu, RHEL 7+).

Answer

grub-install /dev/sda

Answer

update-grub

Answer

grub2-mkconfig -o /boot/grub2/grub.cfg

Question 16

During kernel development, a developer modifies only a few source files in a module directory. Which make target should be used to rebuild only that module without compiling the entire kernel?

Accepted Answer

make M=./drivers/net. The `M=./drivers/net` argument tells the kernel build system to build only the module(s) in the specified directory as external modules, without recompiling the entire kernel tree. This is the standard way to rebuild a single kernel module after modifying its source files, leveraging the already configured kernel build environment.

Answer

make oldconfig && make

Answer

make modules

Answer

make modules_install

Question 17

An administrator needs to disable IPv6 on a running system without rebooting and make the change permanent across reboots. Which set of commands should be used?

Accepted Answer

echo 1 > /proc/sys/net/ipv6/conf/all/disable_ipv6 && edit /etc/sysctl.conf to add net.ipv6.conf.all.disable_ipv6=1. It combines a runtime sysctl command to immediately disable IPv6 on the running system without a reboot, and a persistent configuration in /etc/sysctl.conf to ensure the setting survives reboots. The /proc/sys/net/ipv6/conf/all/disable_ipv6 file controls the IPv6 stack at runtime, and sysctl.conf applies the kernel parameter at boot time.

Answer

modprobe -r ipv6

Answer

Edit /boot/grub/grub.cfg to add ipv6.disable=1

Answer

sysctl -w net.ipv6.conf.all.disable_ipv6=1

Question 18

Which THREE of the following are standard steps in compiling and installing a custom Linux kernel from source? (Choose three.)

Accepted Answer

make menuconfig. `make menuconfig` is a standard step that launches a text-based menu-driven interface for configuring kernel options before compilation. This step allows the user to select which features, drivers, and modules to include in the kernel build, generating the `.config` file that guides the subsequent compilation.

Answer

make modules_install

Answer

make oldconfig

Question 19

Refer to the exhibit. A system administrator has configured the above in /etc/default/grub. After running update-grub, what will be the boot menu behavior?

Accepted Answer

The menu will be displayed for 10 seconds, then the default entry boots automatically.. The configuration shown in /etc/default/grub includes GRUB_TIMEOUT=10 and GRUB_TIMEOUT_STYLE=menu (or the default style if unset). After running update-grub, the boot menu will be displayed for 10 seconds, and then the default entry (set by GRUB_DEFAULT) will boot automatically. This is the standard behavior when GRUB_TIMEOUT is set to a positive integer and the timeout style is 'menu'.

Answer

The boot menu will be hidden for 0 seconds (i.e., not hidden), and the default entry boots immediately.

Answer

The menu will be displayed but with no timeout; it will wait indefinitely for user input.

Answer

The boot menu will be hidden unless Shift is pressed, and the default entry will boot after 10 seconds.

Question 20

During boot, the system displays 'unable to mount root fs on unknown-block'. What is the most likely cause?

Accepted Answer

Missing filesystem driver in initramfs. The error 'unable to mount root fs on unknown-block' indicates that the kernel cannot find a driver for the filesystem or block device containing the root filesystem. This typically occurs when the initramfs lacks the necessary kernel module (e.g., ext4, xfs, or a storage controller driver like ahci or nvme) to access the root device. The initramfs is responsible for loading essential drivers before the kernel mounts the real root filesystem; if the driver is missing, the mount fails.

Answer

Corrupted init binary

Answer

Wrong block device order

Answer

Incorrect root= parameter