How should I use these Linux Kernel and System Startup practice questions?

Read each scenario carefully and choose your answer before revealing the explanation. Then check why your choice was right or wrong. Repeat until the reasoning feels automatic.

Can I practise just Linux Kernel and System Startup questions in a focused session?

Yes — use the session launcher on this page to start a 10-, 20-, 30- or 50-question session drawn entirely from the Linux Kernel and System Startup domain.

LPIC-2 · topic practice

Linux Kernel and System Startup practice questions

Practise Linux Professional Institute Certification Level 2 LPIC-2 Linux Kernel and System Startup practice questions — original exam-style scenarios with answer choices, explanations, and analysis of common mistakes.

Courseiva uses original exam-style practice questions designed for learning and revision. The goal is to understand the concepts, recognise exam patterns, and improve through explanations — not memorise copied exam dumps.

Reviewed byJohnson Ajibi· MSc IT Security

20 questionsDomain: Linux Kernel and System Startup

Practice 10 questions Browse domain →

What the exam tests

What to know about Linux Kernel and System Startup

Linux Kernel and System Startup questions test whether you can apply the concept in context, not just recognise a definition.

How the topic appears in realistic exam-style scenarios.

Which detail in the question changes the correct answer.

How to eliminate plausible but wrong options.

How to connect the question back to the wider exam objective.

Watch out for

Common Linux Kernel and System Startup exam traps

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

Practice set

Linux Kernel and System Startup questions

20 questions · select your answer, then reveal the explanation

Question 1mediummultiple choice

Read the full Linux Kernel and System Startup explanation →

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?

Trap 1: Add the insmod command in /etc/rc.local

While possible, rc.local is not the recommended method for loading modules at boot.

Trap 2: Add the module name to /etc/modules.conf

/etc/modules.conf is not a standard file in modern Linux distributions.

Trap 3: Add a configuration file in /etc/modprobe.d/

/etc/modprobe.d/ is for modprobe options, not for auto-loading modules.

Study all Linux Kernel and System Startup common traps →

A
Add the insmod command in /etc/rc.local
Why wrong: While possible, rc.local is not the recommended method for loading modules at boot.
B
Add the module name to /etc/modules.conf
Why wrong: /etc/modules.conf is not a standard file in modern Linux distributions.
C
Add a configuration file in /etc/modules-load.d/
/etc/modules-load.d/ is the standard location for specifying modules to load at boot.
D
Add a configuration file in /etc/modprobe.d/
Why wrong: /etc/modprobe.d/ is for modprobe options, not for auto-loading modules.

Full breakdown with real-world context →

Question 2easymultiple choice

Read the full Linux Kernel and System Startup explanation →

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?

Trap 1: mkinitrd

mkinitrd is deprecated in favor of dracut or update-initramfs.

Trap 2: grub-mkconfig

grub-mkconfig updates GRUB configuration, not initramfs.

Trap 3: mkinitcpio

mkinitcpio is specific to Arch Linux.

Study all Linux Kernel and System Startup common traps →

A
mkinitrd
Why wrong: mkinitrd is deprecated in favor of dracut or update-initramfs.
B
grub-mkconfig
Why wrong: grub-mkconfig updates GRUB configuration, not initramfs.
C
mkinitcpio
Why wrong: mkinitcpio is specific to Arch Linux.
D
dracut
dracut is the standard tool for building initramfs on many distributions.

Full breakdown with real-world context →

Question 3hardmultiple choice

Read the full Linux Kernel and System Startup explanation →

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?

Trap 1: The GRUB configuration is pointing to the wrong kernel partition.

The error is about mounting root fs, not kernel location.

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

Drivers may be present but LVM activation fails.

Trap 3: The root filesystem is formatted with an unsupported filesystem.

The error is about unknown-block, not filesystem type.

Study all Linux Kernel and System Startup common traps →

A
The GRUB configuration is pointing to the wrong kernel partition.
Why wrong: The error is about mounting root fs, not kernel location.
B
The kernel does not have the necessary device drivers compiled in.
Why wrong: Drivers may be present but LVM activation fails.
C
The root filesystem is formatted with an unsupported filesystem.
Why wrong: The error is about unknown-block, not filesystem type.
D
The initramfs is missing LVM support.
The kernel cannot access the LVM volume without LVM modules in initramfs.

Full breakdown with real-world context →

Question 4mediummultiple choice

Read the full Linux Kernel and System Startup explanation →

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?

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

This makes permanent changes, not temporary.

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

The command line is for advanced commands, not editing boot entries.

Trap 3: Press 'Esc' to access the advanced options menu.

Esc returns to the previous menu.

Study all Linux Kernel and System Startup common traps →

A
Select the kernel entry and press 'e' to edit the boot parameters.
Pressing 'e' allows temporary editing of boot entries.
B
Edit /etc/default/grub and run update-grub to apply changes.
Why wrong: This makes permanent changes, not temporary.
C
Press 'c' to enter the command line and modify parameters.
Why wrong: The command line is for advanced commands, not editing boot entries.
D
Press 'Esc' to access the advanced options menu.
Why wrong: Esc returns to the previous menu.

Full breakdown with real-world context →

Question 5easymultiple choice

Read the full Linux Kernel and System Startup explanation →

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?

Trap 1: grub-install

grub-install installs GRUB to disk, not update configuration.

Trap 2: mkinitrd

mkinitrd rebuilds initramfs, not GRUB configuration.

Trap 3: grub-set-default

grub-set-default sets the default entry but does not update the kernel list.

Study all Linux Kernel and System Startup common traps →

A
grub-install
Why wrong: grub-install installs GRUB to disk, not update configuration.
B
mkinitrd
Why wrong: mkinitrd rebuilds initramfs, not GRUB configuration.
C
grub-set-default
Why wrong: grub-set-default sets the default entry but does not update the kernel list.
D
update-grub
update-grub regenerates the GRUB configuration file.

Full breakdown with real-world context →

Question 6hardmultiple choice

Read the full Linux Kernel and System Startup explanation →

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?

Trap 1: The kernel configuration has disabled module loading.

If module loading is disabled, the error would be different.

Trap 2: The modules have incorrect file permissions.

Permission errors would be 'Permission denied', not 'Exec format error'.

Trap 3: The modules are not properly ordered in the dependency file.

Dependency order does not cause exec format errors.

Study all Linux Kernel and System Startup common traps →

A
The kernel configuration has disabled module loading.
Why wrong: If module loading is disabled, the error would be different.
B
The modules were compiled against a different kernel version.
Exec format error occurs when module version doesn't match kernel.
C
The modules have incorrect file permissions.
Why wrong: Permission errors would be 'Permission denied', not 'Exec format error'.
D
The modules are not properly ordered in the dependency file.
Why wrong: Dependency order does not cause exec format errors.

Full breakdown with real-world context →

Question 7easymultiple choice

Read the full Linux Kernel and System Startup explanation →

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

Trap 1: dmesg

dmesg shows kernel messages, but not specifically boot parameters.

Trap 2: lsmod

lsmod lists loaded kernel modules.

Trap 3: cat /proc/version

/proc/version shows kernel version, not boot parameters.

Study all Linux Kernel and System Startup common traps →

A
cat /proc/cmdline
/proc/cmdline contains the boot parameters.
B
dmesg
Why wrong: dmesg shows kernel messages, but not specifically boot parameters.
C
lsmod
Why wrong: lsmod lists loaded kernel modules.
D
cat /proc/version
Why wrong: /proc/version shows kernel version, not boot parameters.

Full breakdown with real-world context →

Question 8mediummulti select

Read the full Linux Kernel and System Startup explanation →

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

Trap 1: lsmod

lsmod lists loaded modules, does not manage them.

Trap 2: rmmod

rmmod removes modules, but the question asks for managing, including loading.

Trap 3: depmod

depmod generates dependency files, not manage modules directly.

Study all Linux Kernel and System Startup common traps →

A
lsmod
Why wrong: lsmod lists loaded modules, does not manage them.
B
insmod
insmod loads a single module directly.
C
modprobe
modprobe is used to load and unload modules with dependency resolution.
D
rmmod
Why wrong: rmmod removes modules, but the question asks for managing, including loading.
E
depmod
Why wrong: depmod generates dependency files, not manage modules directly.

Full breakdown with real-world context →

Question 9hardmulti select

Read the full Linux Kernel and System Startup explanation →

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

Trap 1: Too many kernel modules loaded

Too many modules may cause memory issues but not a panic directly.

Trap 2: Filesystem errors on the root partition

Filesystem errors typically cause a mount failure, not a kernel panic.

Study all Linux Kernel and System Startup common traps →

A
Too many kernel modules loaded
Why wrong: Too many modules may cause memory issues but not a panic directly.
B
Corrupted kernel image
A corrupted vmlinuz or bzImage can cause a panic during decompression or execution.
C
Hardware incompatibility
Hardware that triggers a bug or unsupported feature can cause a panic.
D
Filesystem errors on the root partition
Why wrong: Filesystem errors typically cause a mount failure, not a kernel panic.
E
Missing device drivers for storage controllers
If the kernel cannot access the root filesystem due to missing drivers, it may panic.

Full breakdown with real-world context →

Question 10hardmultiple choice

Read the full Linux Kernel and System Startup explanation →

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?

Trap 1: Increase the system memory to reduce memory pressure.

Memory pressure is not the issue; the problem is a NULL pointer dereference.

Trap 2: Update the firmware on the network interface cards.

Firmware update is unlikely to fix a kernel API incompatibility.

Trap 3: Recompile the network driver module with debugging enabled.

Recompiling with debugging may provide more info but does not fix the underlying issue.

Study all Linux Kernel and System Startup common traps →

A
Increase the system memory to reduce memory pressure.
Why wrong: Memory pressure is not the issue; the problem is a NULL pointer dereference.
B
Update the firmware on the network interface cards.
Why wrong: Firmware update is unlikely to fix a kernel API incompatibility.
C
Check the kernel configuration changes between versions 5.10 and 5.15 that affect the bonding driver.
Kernel API changes in the bonding driver could cause the third-party module to dereference a NULL pointer.
D
Recompile the network driver module with debugging enabled.
Why wrong: Recompiling with debugging may provide more info but does not fix the underlying issue.

Full breakdown with real-world context →

Question 11hardmultiple choice

Read the full Linux Kernel and System Startup explanation →

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?

Trap 1: The root filesystem is formatted with an unsupported filesystem…

This would typically produce an error message, not a hang.

Trap 2: The initrd image is missing from the /boot partition.

An initrd is not always required; the kernel can mount root directly.

Trap 3: The GRUB bootloader is not installed on the MBR.

This would prevent the bootloader from loading entirely, not cause a hang at root mount.

Study all Linux Kernel and System Startup common traps →

A
The root= parameter in the kernel command line points to a non-existent device.
A missing root device causes the kernel to hang while waiting for the device to appear.
B
The root filesystem is formatted with an unsupported filesystem type.
Why wrong: This would typically produce an error message, not a hang.
C
The initrd image is missing from the /boot partition.
Why wrong: An initrd is not always required; the kernel can mount root directly.
D
The GRUB bootloader is not installed on the MBR.
Why wrong: This would prevent the bootloader from loading entirely, not cause a hang at root mount.

Full breakdown with real-world context →

Question 12easymulti select

Read the full Linux Kernel and System Startup explanation →

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

Trap 1: Using modprobe to load kernel modules with parameters

modprobe loads modules, not modifies existing parameters.

Trap 2: Editing /etc/sysctl.conf and running sysctl --system

This applies settings from files, but it's not a direct runtime modification.

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

This requires a reboot to take effect.

Study all Linux Kernel and System Startup common traps →

A
Using modprobe to load kernel modules with parameters
Why wrong: modprobe loads modules, not modifies existing parameters.
B
Editing /etc/sysctl.conf and running sysctl --system
Why wrong: This applies settings from files, but it's not a direct runtime modification.
C
Writing to files in /proc/sys/ using echo
Writing directly to /proc/sys/ files changes parameters immediately.
D
Using the sysctl command to set parameters
sysctl modifies parameters in /proc/sys/ immediately.
E
Adding parameters to the kernel command line in /etc/default/grub
Why wrong: This requires a reboot to take effect.

Full breakdown with real-world context →

Question 13mediummultiple choice

Read the full Linux Kernel and System Startup explanation →

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?

Exhibit

Refer to the exhibit.

[    0.000000] Linux version 5.10.0-8-amd64 (debian@amd64) #1 SMP Debian 5.10.46-4 (2021-08-03)
[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-5.10.0-8-amd64 root=/dev/mapper/vg-root ro quiet
[    0.000000] Memory: 1024M/2048M available (8192K kernel code, 1024K rwdata, 2048K rodata, 512K init, 256K bss, 1024K reserved)
[    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-5.10.0-8-amd64 root=/dev/mapper/vg-root ro quiet
[    1.234567] device-mapper: ioctl: 4.43.0-ioctl (2021-02-07) initialised: dm-devel@redhat.com
[    2.345678] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
[    3.456789] systemd[1]: systemd 247 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)

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

The boot log shows the filesystem was mounted successfully, so the device exists.

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

No filesystem errors are shown in the log; EXT4 mounted cleanly.

Trap 3: SELinux is enforcing and prevents write access to the root…

SELinux does not enforce read-only mount; it controls access to files.

Study all Linux Kernel and System Startup common traps →

A
The kernel command line contains the 'ro' parameter, which remains in effect.
The 'ro' parameter causes the root filesystem to be mounted read-only unless remounted rw by init.
B
The root device /dev/mapper/vg-root does not exist.
Why wrong: The boot log shows the filesystem was mounted successfully, so the device exists.
C
The root filesystem is damaged and forces read-only mount.
Why wrong: No filesystem errors are shown in the log; EXT4 mounted cleanly.
D
SELinux is enforcing and prevents write access to the root filesystem.
Why wrong: SELinux does not enforce read-only mount; it controls access to files.

Full breakdown with real-world context →

Question 14hardmultiple choice

Read the full Linux Kernel and System Startup explanation →

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?

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

GRUB is working; the kernel itself is the issue.

Trap 2: Boot from a live CD, chroot into the system, and reinstall the new…

Reinstalling the same kernel may not resolve the issue if it is a bug.

Trap 3: Boot from a live CD, chroot into the system, and rebuild the initrd…

The initrd is likely not the cause; the kernel hangs without output, suggesting a kernel bug or missing driver.

Study all Linux Kernel and System Startup common traps →

A
Interrupt the boot process at GRUB, select the advanced options, and boot the old kernel 5.10.0-8.
This restores functionality immediately, allowing later troubleshooting of the new kernel.
B
Reinstall GRUB from a live CD to fix the bootloader configuration.
Why wrong: GRUB is working; the kernel itself is the issue.
C
Boot from a live CD, chroot into the system, and reinstall the new kernel package.
Why wrong: Reinstalling the same kernel may not resolve the issue if it is a bug.
D
Boot from a live CD, chroot into the system, and rebuild the initrd for the new kernel.
Why wrong: The initrd is likely not the cause; the kernel hangs without output, suggesting a kernel bug or missing driver.

Full breakdown with real-world context →

Question 15easymultiple choice

Read the full Linux Kernel and System Startup explanation →

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

Trap 1: rmmod

rmmod removes modules.

Trap 2: modprobe

modprobe also loads modules but handles dependencies; the question asks for directly adding without recompiling, but modprobe is more common. However, insmod is the simplest answer.

Trap 3: depmod

depmod creates module dependency files, not load modules.

Study all Linux Kernel and System Startup common traps →

A
insmod
insmod inserts a module directly.
B
rmmod
Why wrong: rmmod removes modules.
C
modprobe
Why wrong: modprobe also loads modules but handles dependencies; the question asks for directly adding without recompiling, but modprobe is more common. However, insmod is the simplest answer.
D
depmod
Why wrong: depmod creates module dependency files, not load modules.

Full breakdown with real-world context →

Question 16mediummultiple choice

Read the full Linux Kernel and System Startup explanation →

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?

Trap 1: The kernel image is corrupted.

Corrupted kernel would cause a different panic or fail to execute.

Trap 2: The init process is missing.

Init missing causes panic later, not VFS error.

Trap 3: The root filesystem is formatted with an unsupported filesystem.

Unsupported filesystem would show different error like 'unknown filesystem type'.

Study all Linux Kernel and System Startup common traps →

A
The kernel lacks the driver for the storage controller.
Missing driver prevents accessing the root filesystem.
B
The kernel image is corrupted.
Why wrong: Corrupted kernel would cause a different panic or fail to execute.
C
The init process is missing.
Why wrong: Init missing causes panic later, not VFS error.
D
The root filesystem is formatted with an unsupported filesystem.
Why wrong: Unsupported filesystem would show different error like 'unknown filesystem type'.

Full breakdown with real-world context →

Question 17hardmultiple choice

Read the full Linux Kernel and System Startup explanation →

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?

Trap 1: The kernel image is missing.

Missing kernel would prevent any boot messages.

Trap 2: The kernel lacks SATA driver support.

Most kernels include SATA drivers.

Trap 3: The initramfs was not regenerated after adding the disk.

Initramfs regeneration is not required for an additional disk unless the root filesystem changes.

Study all Linux Kernel and System Startup common traps →

A
The root filesystem UUID in /etc/fstab is incorrect.
Incorrect UUID leads to unknown-block error.
B
The kernel image is missing.
Why wrong: Missing kernel would prevent any boot messages.
C
The kernel lacks SATA driver support.
Why wrong: Most kernels include SATA drivers.
D
The initramfs was not regenerated after adding the disk.
Why wrong: Initramfs regeneration is not required for an additional disk unless the root filesystem changes.

Full breakdown with real-world context →

Question 18mediumdrag order

Read the full Linux Kernel and System Startup explanation →

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

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

5Step 5

Question 19mediumdrag order

Read the full Linux Kernel and System Startup explanation →

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

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

5Step 5

Question 20mediummatching

Read the full Linux Kernel and System Startup explanation →

Match each Linux filesystem feature to its description.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

Journaling filesystem with extents and delayed allocation

High-performance 64-bit journaling filesystem

Copy-on-write filesystem with snapshots and compression

Advanced filesystem with volume management and checksumming

Network filesystem for sharing directories over a network

Continue with 20-question session →

Free account

Track your progress over time

Create a free account to save your results and see which topics improve across sessions.

Focused Linux Kernel and System Startup sessions

Start a Linux Kernel and System Startup only practice session

Every question in these sessions is drawn from the Linux Kernel and System Startup domain — nothing else.

10 questions 20 questions 30 questions 50 questions

Browse all Linux Kernel and System Startup questions →Mixed LPIC-2 session

Frequently asked questions

What does the LPIC-2 exam test about Linux Kernel and System Startup?: Linux Kernel and System Startup questions test whether you can apply the concept in context, not just recognise a definition.
How should I use these practice questions?: Select your answer before revealing the explanation. Then read why each option is right or wrong — this active recall approach builds retention far faster than re-reading notes.
Can I practise just Linux Kernel and System Startup questions in a focused session?: Yes — the session launcher on this page draws every question from the Linux Kernel and System Startup domain. Use a 10-question session first to gauge your baseline, then move to 20 or 30 once the weak spots are clear.
Where can I practise other LPIC-2 topics?: Use the topic links above to move to related areas, or go back to the LPIC-2 question bank to see all topics.
Are these real exam questions or dumps?: These are original practice questions written to test the same concepts the LPIC-2 exam covers. They are not copied from any real exam or dump site.

Linux Kernel and System Startup only

10 questions 20 questions 30 questions 50 questions

Mixed LPIC-2 session

Track your progress

A free account saves results across sessions and highlights which topics need work.

Study resources

All LPIC-2 questions Linux Kernel and System Startup domain overview LPIC-2 exam guide

Exam traps to avoid

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

Linux Kernel and System Startup practice questions

What to know about Linux Kernel and System Startup

Common Linux Kernel and System Startup exam traps

Linux Kernel and System Startup questions

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?

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?

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?

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?

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?

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?

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

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

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

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?

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

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?

Exhibit

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

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?

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?

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

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

Match each Linux filesystem feature to its description.

Track your progress over time

Start a Linux Kernel and System Startup only practice session

Related LPIC-2 topic practice pages