# Knowledge Check: Linux System Administration

---

**1. What are the five questions this module opened with?**

*Answer:* What is running? Who started it? Where is its configuration? Where are its logs? How
do I verify its state?

---

**2. Why doesn't this Lab environment have `systemctl`?**

*Answer:* This Lab's container doesn't run systemd as PID 1 — its boot script starts k3s
directly instead, the same way most containers don't run a full init system. The concepts
(inspecting a running service's process/config/logs/state) are the same regardless of which
supervisor manages it.

---

**3. A process exists (`pgrep` finds a PID) but the service seems unreachable. What's the next
thing to check?**

*Answer:* Whether it's actually listening on the expected port (`ss -lnt`) — a running process
and a reachable service are two separate facts; the process could have started but failed to
bind its port.

---

**4. Where does a well-behaved Linux service typically write what it's doing?**

*Answer:* A log file, usually under `/var/log/`.

## Instructor Notes

**Facilitation:** Question 2 is worth confirming explicitly if any student has prior systemd
experience — set the expectation before the Lab, not after a confusing error.

**Approximate timing:** 5 minutes.