# Knowledge Check: Containers → Kubernetes

---

**1. Does Kubernetes replace Docker/containers?**

*Answer:* No — Kubernetes orchestrates containers across many machines; it runs on top of the
same container concepts this course taught, not instead of them.

---

**2. Name one thing Kubernetes adds that a single-machine `docker run`/Compose setup
fundamentally can't do.**

*Answer:* Any reasonable answer from: scheduling across multiple machines, automatic
reconciliation to a desired state after a failure, service discovery across many changing
instances, automated health-based replacement, demand-based scaling, or coordinated rollout
across a fleet.

---

**3. What does "desired state" mean, in the sense this lesson introduced it?**

*Answer:* You declare what SHOULD be running; the orchestrator continuously works to make actual
reality match that declaration, including automatically after a failure — rather than a person
having to manually notice and fix drift.

---

**4. Why doesn't this course teach Kubernetes directly, ending here instead?**

*Answer:* This course's job was building the container/Linux/Git foundation Kubernetes assumes
— ROOT 05 builds on exactly this foundation to teach Kubernetes itself.

## Instructor Notes

**Facilitation:** Question 2 is worth collecting several different answers from the group — the
variety itself is evidence the "why Kubernetes" question actually landed.

**Approximate timing:** 5 minutes.