- A
kill -9 1234 (SIGKILL)
SIGKILL cannot be caught and kills immediately.
- B
kill -15 1234 (SIGTERM)
Why wrong: SIGTERM is the default and can be caught.
- C
kill -2 1234 (SIGINT)
Why wrong: SIGINT is also catchable.
- D
kill -1 1234 (SIGHUP)
Why wrong: SIGHUP can be caught and handled.
LFCS Operation of Running Systems Practice Question
This LFCS practice question tests your understanding of operation of running systems. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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.
A process (PID 1234) is hung and cannot be killed with SIGTERM. To force termination, which signal should be sent?
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
kill -9 1234 (SIGKILL)
SIGKILL (signal 9) is the correct choice because it cannot be caught, blocked, or ignored by the process. Unlike SIGTERM, which allows the process to perform cleanup, SIGKILL immediately terminates the process at the kernel level, making it the only reliable way to force-kill a hung process that ignores other signals.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
kill -9 1234 (SIGKILL)
Why this is correct
SIGKILL cannot be caught and kills immediately.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
kill -15 1234 (SIGTERM)
Why it's wrong here
SIGTERM is the default and can be caught.
- ✗
kill -2 1234 (SIGINT)
Why it's wrong here
SIGINT is also catchable.
- ✗
kill -1 1234 (SIGHUP)
Why it's wrong here
SIGHUP can be caught and handled.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse SIGTERM (15) as a 'force kill' signal, not realizing that a hung process can ignore it, while SIGKILL (9) is the only signal that guarantees termination.
Detailed technical explanation
How to think about this question
Under the hood, SIGKILL (9) bypasses the process's signal handlers entirely and is delivered directly to the kernel's task management, which immediately removes the process from the run queue and frees its resources. A real-world scenario is a zombie or D-state process (uninterruptible sleep) where even SIGKILL may fail; in such cases, a system reboot or kernel intervention is required. Note that SIGKILL cannot be sent to PID 1 (init/systemd) as a safety measure.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Operation of Running Systems — study guide chapter
Learn the concepts, then practise the questions
- →
Operation of Running Systems practice questions
Targeted practice on this topic area only
- →
All LFCS questions
513 questions across all exam domains
- →
Linux Foundation Certified System Administrator LFCS study guide
Full concept coverage aligned to exam objectives
- →
LFCS practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related LFCS practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
User and Group Management practice questions
Practise LFCS questions linked to User and Group Management.
Operation of Running Systems practice questions
Practise LFCS questions linked to Operation of Running Systems.
Essential Commands practice questions
Practise LFCS questions linked to Essential Commands.
Networking practice questions
Practise LFCS questions linked to Networking.
Service Configuration practice questions
Practise LFCS questions linked to Service Configuration.
Storage Management practice questions
Practise LFCS questions linked to Storage Management.
LFCS fundamentals practice questions
Practise LFCS questions linked to LFCS fundamentals.
LFCS scenario practice questions
Practise LFCS questions linked to LFCS scenario.
LFCS troubleshooting practice questions
Practise LFCS questions linked to LFCS troubleshooting.
Practice this exam
Start a free LFCS practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this LFCS question test?
Operation of Running Systems — This question tests Operation of Running Systems — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: kill -9 1234 (SIGKILL) — SIGKILL (signal 9) is the correct choice because it cannot be caught, blocked, or ignored by the process. Unlike SIGTERM, which allows the process to perform cleanup, SIGKILL immediately terminates the process at the kernel level, making it the only reliable way to force-kill a hung process that ignores other signals.
What should I do if I get this LFCS question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
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 →
Keep practising
More LFCS practice questions
- A system administrator needs to ensure the Apache httpd service starts automatically on system boot. Which command shoul…
- Which THREE of the following are valid methods to mount an NFS filesystem on a client?
- Refer to the exhibit. The administrator wants to create a RAID 1 array using /dev/sdb1 and /dev/sdc1. Which command shou…
- A system administrator needs to list all files in the current directory, including hidden files, in a long listing forma…
- A user wants to find all files in /var/log that have been modified within the last 2 days. Which command should they use…
- A user needs to view the contents of a compressed log file /var/log/syslog.gz without first decompressing it. Which comm…
Last reviewed: Jun 25, 2026
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.
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.