LPIC-1 System Architecture Practice Question
A Linux workstation appears to hang early in the boot process after the initramfs is loaded. The administrator wants to add kernel boot parameters temporarily from the GRUB 2 menu without making a permanent change. Which action should the administrator take?
⚠ Common exam trap
Candidates often confuse the persistent configuration files and the GRUB command shell with the menu edit feature, when only editing the selected entry applies a temporary kernel parameter for a single boot.
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
✓
At the GRUB menu, press e to edit the selected entry, append the parameters to the linux line, and press Ctrl+X or F10 to boot.
GRUB 2 allows one-time modification of a boot entry from the menu. Pressing e opens the entry for editing, where the kernel command line can be appended, then Ctrl+X or F10 boots with those in-memory changes. Nothing is written to configuration files, so the modification applies only to that boot, which is ideal for testing parameters during troubleshooting.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
At the GRUB menu, press e to edit the selected entry, append the parameters to the linux line, and press Ctrl+X or F10 to boot.
Why this is correct
Pressing e at the GRUB 2 menu opens an editable view of the chosen entry, where the kernel command line on the linux line can be modified in memory. Booting with Ctrl+X or F10 uses those edits for that single boot only and does not persist them to disk, exactly matching the request for a temporary kernel parameter change to diagnose the hang.
- ✗
At the GRUB menu, press c to open the command line and run the normal command.
Why it's wrong here
Pressing c drops into the GRUB command shell, which is useful for manually loading modules and booting a kernel when the menu is broken. It does not present the existing entry with its kernel line for simple editing, so appending parameters there requires manually specifying the kernel and initrd paths. It is a heavier, error-prone approach compared with editing the entry directly.
- ✗
Boot normally, then use sysctl -w to apply the parameters and reboot.
Why it's wrong here
sysctl adjusts runtime kernel parameters exposed under /proc/sys, such as network or memory tunables. Kernel boot parameters passed on the command line, like those controlling console or early initramfs behavior, are consumed during early boot and cannot be set through sysctl. This approach also cannot affect the pre-boot hang because it requires a successful boot first.
- ✗
Edit /etc/default/grub, add the parameters to GRUB_CMDLINE_LINUX, and reboot.
Why it's wrong here
Editing /etc/default/grub and regenerating the configuration makes a persistent change to the boot menu entries. That alters the system permanently for every future boot, which contradicts the requirement for a temporary, one-time parameter addition. It also requires running the configuration generator afterward, so it is both persistent and more steps than needed.
Go deeper
Related to this question
About these practice questions
One of 402 original LPIC-1 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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official LPI exam blueprint
This LPIC-1 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-1 exam.