LPIC-2 Linux Kernel and System Startup Practice Question
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)
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?
⚠ Common exam trap
Candidates often assume a successful boot implies the root filesystem is automatically remounted read-write, overlooking that the 'ro' kernel parameter persists unless explicitly overridden. They may also mistakenly attribute a read-only root to filesystem damage or SELinux, but a damaged filesystem would cause boot failures or emergency mode, and SELinux does not enforce read-only mounts.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
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 analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The kernel command line contains the 'ro' parameter, which remains in effect.
Why this is correct
The 'ro' parameter causes the root filesystem to be mounted read-only unless remounted rw by init.
- ✗
The root device /dev/mapper/vg-root does not exist.
Why it's wrong here
The boot log shows the filesystem was mounted successfully, so the device exists.
- ✗
The root filesystem is damaged and forces read-only mount.
Why it's wrong here
No filesystem errors are shown in the log; EXT4 mounted cleanly.
- ✗
SELinux is enforcing and prevents write access to the root filesystem.
Why it's wrong here
SELinux does not enforce read-only mount; it controls access to files.
Go deeper
Related to this question
About these practice questions
One of 507 original LPIC-2 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This LPIC-2 practice question is part of Courseiva's free LPI certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the LPIC-2 exam.