Files
rootnode-academy/content/root/root-02-linux-administration-networking/m02-storage-and-filesystems/03-knowledge-check.md
T
ced4568andClaude Sonnet 5 e007bcf000 feat(root02): author Linux Administration & Networking
Adds all 6 ROOT 02 modules (Linux system administration, storage & filesystems, the
Networking Mental Model, Linux network inspection, DNS & HTTP, Linux troubleshooting) — 37
activities, each with a real lesson, demonstration/guided exercise, knowledge check, hands-on
Lab, and reflection. The Networking Mental Model module (M3) gets deliberately extra depth per
its "critical module" designation, with no lab by design — conceptual mastery via knowledge
check and guided exercise, matching root-05-m00's own precedent.

Adds 6 new hands-on Linux/networking scenarios plus 2 MCQs: linux-service-inspection (inspects
the platform's own real nginx without touching it — a genuinely safe, real service-inspection
target that avoids ever risking the Lab's own connectivity), linux-service-lifecycle (start/
verify/stop a fully controllable service), linux-storage-inspection, linux-network-inspection
(ip/ss/getent/curl, each framed as answering one specific diagnostic question),
linux-dns-http-diagnosis (a genuine DNS-resolves-but-wrong-port failure, diagnosed and fixed),
and linux-troubleshooting-framework (a real missing-config-file failure, resolved via the
RootNode Observe/Evidence/Hypothesis/Test/Repair/Validate/Prevent framework). All tested
end-to-end via the real scenario-validation API, including negative tests confirming they fail
when unsolved.

Wires rootnode-linux-networking-assessment (2 required + 4 random-draw scenarios) using the
existing Phase 3B assessment engine.

Co-Authored-By: Claude Sonnet 5 <[email protected]>
2026-08-26 17:07:46 -05:00

1.1 KiB

Knowledge Check: Storage and Filesystems


1. df -h / shows only 23% used, but you suspect one directory is unusually large. Does df alone answer that?

Answer: No — df reports overall filesystem usage, not per-directory. You need du -sh <path> pointed at the suspect directory (or directories) to answer that.


2. What makes data in a container's writable layer different from data in /home?

Answer: By convention and design, a container's own writable layer is meant to be disposable — data there disappears when the container is destroyed, unless explicitly persisted elsewhere (a topic ROOT 04 covers directly). /home data is expected to persist normally.


3. What does "mounting" a filesystem actually mean?

Answer: Attaching a filesystem so it becomes accessible at a specific directory path — / itself is a mount point, and additional filesystems can be mounted at other paths.

Instructor Notes

Facilitation: Question 2 previews ROOT 04's volume/bind-mount content directly — worth naming that connection explicitly.

Approximate timing: 5 minutes.