# Knowledge Check: DevOps & Platform Thinking

---

**1. A colleague says "DevOps is the team that handles our servers." What's wrong with that
statement?**

*Answer:* DevOps describes a set of PRACTICES (shared ownership, fast feedback loops,
automation) for how development and operations work together — not a separate team that
operations gets handed off to. Treating it as a team name misses the point that these practices
are meant to be shared across engineering, not isolated in one group.

---

**2. Which ROOT_ course's central skill is most directly an example of "declarative thinking"
applied outside Kubernetes objects specifically?**

*Answer:* ROOT 05's desired-state model is the direct root of declarative thinking generally —
Infrastructure as Code applies the exact same principle (describe what should exist, let
automation enforce it) to cloud infrastructure rather than Kubernetes objects specifically.

---

**3. True or false: platform engineering's main goal is building the most technically
sophisticated internal tooling possible.**

*Answer:* False. Its main goal is reducing COGNITIVE LOAD for other engineers via self-service,
golden-path tooling — sophistication that doesn't make another engineer's job easier isn't the
point, even if it's technically impressive.

---

**4. Why can't this course build a hands-on GitOps or CI/CD Lab the same way ROOT 05-10 built
Kubernetes Labs?**

*Answer:* Those require different infrastructure the current Lab platform doesn't provide (a
Git repository + deployment-automation tool like ArgoCD for GitOps; a CI runner for CI/CD) — see
`docs/ROOT11_DEVOPS_PLATFORM_SCOPE.md`. Building a fake version of either would teach an
inaccurate mental model, which is worse than honestly deferring the hands-on practice.

## Instructor Notes

**Facilitation:** Question 4 is worth stating plainly in a live classroom — students should
understand this is a genuine platform limitation being handled honestly, not an oversight.

**Approximate timing:** 5 minutes.