LFCS Operation of Running Systems Practice Question
A junior administrator needs to check the current runlevel and then change the system to runlevel 3 (multi-user, no GUI) on a SysVinit-based system. Which command sequence will accomplish this?
⚠ Common exam trap
The trap here is assuming that 'chkconfig --list' shows the current runlevel, when it actually lists service configuration across runlevels.
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
✓
runlevel; init 3
On SysVinit systems, the 'runlevel' command displays the current and previous runlevel, and 'init 3' changes to runlevel 3 (multi-user, no GUI). The other options use systemd commands or incorrect utilities that do not fulfill both requirements.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
runlevel; init 3
Why this is correct
'runlevel' displays the previous and current runlevel, and 'init 3' changes the system to runlevel 3. On SysVinit systems, runlevel 3 is typically multi-user mode without a graphical interface. This sequence is correct for checking and changing runlevels on a SysVinit-based distribution.
- ✗
telinit -q; telinit 3
Why it's wrong here
'telinit -q' reloads the init configuration without changing runlevel, and 'telinit 3' changes to runlevel 3. However, 'telinit -q' does not display the current runlevel; it only reloads. To display the runlevel, you need 'runlevel' or 'who -r'. Thus, this sequence does not show the current runlevel before changing it.
- ✗
chkconfig --list; init 3
Why it's wrong here
'chkconfig --list' lists services and their runlevels, not the current runlevel. It does not show which runlevel the system is currently in. While 'init 3' correctly changes the runlevel, the first command does not provide the current runlevel, making this sequence incorrect for the task.
- ✗
systemctl get-default; systemctl isolate multi-user.target
Why it's wrong here
These commands are for systemd-based systems, not SysVinit. 'systemctl get-default' shows the default target, and 'systemctl isolate multi-user.target' changes to multi-user mode. While functionally similar, the question specifies a SysVinit-based system, so these commands are not applicable.
Go deeper
Related to this question
About these practice questions
This LFCS question is part of Courseiva's 406-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. 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 Linux Foundation exam blueprint
This LFCS practice question is part of Courseiva's free Linux Foundation 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 LFCS exam.