Quick Answer
The answer is the `runlevel` command and the `who -r` command. These two tools are the standard methods to display the current runlevel in a SysV init system because they directly query the system’s init state from the `/var/run/utmp` file, where the current and previous runlevels are recorded. The `runlevel` command outputs both the previous and current runlevel in a simple two-column format, while `who -r` provides the same current runlevel along with the timestamp of the last runlevel change, making it equally valid for this purpose. On the Linux Professional Institute Certification Level 1 LPIC-1 exam, this question tests your understanding of legacy SysV init management, a topic that often appears alongside systemd comparisons. A common trap is assuming `init` or `telinit` show the runlevel—they change it, not display it. Remember the mnemonic: “Runlevel reveals, who -r reveals the same.”
This LPIC-1 practice question tests your understanding of administrative tasks. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Which TWO commands can be used to display the current runlevel of a SysV init system?
init 3
Why wrong: This changes runlevel to 3, not displays it.
who -r
The 'who -r' command displays the current runlevel and process since last boot.
telinit
Why wrong: telinit is used to send signals to init, typically to change runlevel, not display current.
runlevel
The runlevel command prints the previous and current runlevel.
systemctl get-default
Why wrong: This is for systemd, not SysV init.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
who -r
The `who -r` command displays the current runlevel and the time it was last changed, making it a valid way to check the runlevel in a SysV init system. The `runlevel` command directly outputs the previous and current runlevel, which is the standard tool for this purpose.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
init 3
Why it's wrong here
This changes runlevel to 3, not displays it.
who -r
Why this is correct
The 'who -r' command displays the current runlevel and process since last boot.
Related concept
Read the scenario before looking for a memorised answer.
telinit
Why it's wrong here
telinit is used to send signals to init, typically to change runlevel, not display current.
runlevel
Why this is correct
The runlevel command prints the previous and current runlevel.
Related concept
Read the scenario before looking for a memorised answer.
systemctl get-default
Why it's wrong here
This is for systemd, not SysV init.
Common exam traps
The trap here is that candidates confuse commands that change runlevels (like `init` or `telinit`) with those that display them, or mistakenly apply systemd commands like `systemctl get-default` to SysV init systems.
Detailed technical explanation
In SysV init, runlevels are defined in `/etc/inittab` and range from 0 to 6, with S for single-user mode. The `runlevel` command reads `/var/run/utmp` to determine the current and previous runlevel, while `who -r` parses the same utmp file to display the runlevel and timestamp. A subtle behavior is that if the system has not changed runlevels since boot, `runlevel` may show 'N' as the previous runlevel.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A practitioner preparing for the LPIC-1 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Administrative Tasks — study guide chapter
Learn the concepts, then practise the questions
Administrative Tasks practice questions
Targeted practice on this topic area only
All LPIC-1 questions
522 questions across all exam domains
Linux Professional Institute Certification Level 1 LPIC-1 study guide
Full concept coverage aligned to exam objectives
LPIC-1 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise LPIC-1 questions linked to GNU and Unix Commands.
Practise LPIC-1 questions linked to Devices, Filesystems and FHS.
Practise LPIC-1 questions linked to Linux Installation and Package Management.
Practise LPIC-1 questions linked to Essential System Services and Networking.
Practise LPIC-1 questions linked to Administrative Tasks.
Practise LPIC-1 questions linked to Shells, Scripting and Data Management.
Practise LPIC-1 questions linked to System Architecture.
Practise LPIC-1 questions linked to LPIC-1 fundamentals.
Practise LPIC-1 questions linked to LPIC-1 scenario.
Practise LPIC-1 questions linked to LPIC-1 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Administrative Tasks — This question tests Administrative Tasks — Read the scenario before looking for a memorised answer..
The correct answer is: who -r — The `who -r` command displays the current runlevel and the time it was last changed, making it a valid way to check the runlevel in a SysV init system. The `runlevel` command directly outputs the previous and current runlevel, which is the standard tool for this purpose.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Which TWO commands can be used to display the current runlevel of a system?
mediumWhy D: The `runlevel` command displays the previous and current runlevel of a SysV init system. The `who -r` command also shows the current runlevel along with the process ID of the init daemon. Both are standard tools for querying runlevel information on systems using SysV init.
Last reviewed: Jun 11, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.