ced4568andClaude Sonnet 5
7f6e1857c0
Upgrades six PARTIAL modules to the gold-module standard (lesson/demonstration/ knowledge-check/guided-exercise/lab(s)/reflection), preserving every existing lab activity_id and scenario_id: root-06-m03 (jobs/cronjobs/daemonsets), root-07-m04 (ingress/networkpolicy), root-07-m02 (configuration/secrets, converted in place from a bare 5-lab bank), root-09-m02 (serviceaccounts/rbac), root-09-m03 (network/supply-chain security), root-10-m03 (troubleshooting framework). root-05-m01 (20-task kubectl-fluency bank) gets a minimal bookending lesson + reflection rather than a full redesign, since each task already carries its own explanation. root-12-m01, root-capstone-m01, and root-09-m04 are promoted to READY via documented exceptions (no new activities) where adding one would misrepresent their intentional design. Wires a new rootnode-security-assessment (exam, 60min, hint_policy disabled) using the existing Phase 3B assessment engine: 3 required hands-on CORE scenarios + 4 random-draw pools covering SecurityContext, RBAC, network policy, and the 7 previously-unwired CKS MCQs. Wires the previously-unwired readiness-probe-task scenario as an OPTIONAL practice lab in root-10-m01, using the existing is_required model. Adds root-11-m01-devops-platform-thinking — an honest, lesson-only ROOT 11 orientation module naming DevOps/platform engineering practices already exercised in ROOT 05-10/12, explicit that GitOps/CI-CD/IaC/observability need lab infrastructure this platform doesn't yet provide. No fake labs. Adds infra/scripts/validate-course-content.js: cross-checks the DB against scenario/content files for duplicate ids, orphans, invalid references, cycles, sequence collisions, instructor-notes leakage, and (new) self-paced content deferring explanation to a live instructor. 0 errors against the resulting 22 courses/modules, 163 activities, 98 scenario files. No application code changed — every gap was satisfiable with existing tables (course_modules, module_activities, assessment_definitions) and the existing content-delivery pipeline. Co-Authored-By: Claude Sonnet 5 <[email protected]>
47 lines
2.0 KiB
Markdown
47 lines
2.0 KiB
Markdown
# 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.
|