# Reflection: You Now Have a Repeatable Checklist

## Reflection questions

1. Before this module, if someone said "check whether the service is healthy," what would you
   have actually done? How does that compare to the five-question checklist now?
2. You started and stopped a service you fully controlled this module. What's different about
   doing the same thing to a service you DIDN'T start, on a machine you don't fully understand
   yet?

## Real Ops takeaway

**The five-question checklist works on ANY unfamiliar Linux system, not just this Lab.** Running
process, listening port, config location, logs, and current state — this is genuinely how
experienced engineers approach a machine they've never touched before. You'll use this exact
checklist again in ROOT 04 when a container "doesn't seem to be working," and again in
Kubernetes when a Pod isn't behaving as expected — the tools change, the checklist doesn't.

This module is complete. Continue to the next module.

## Instructor Notes

**Discussion questions for a live classroom:** question 2 is worth real discussion time — the
honest answer is "you should be more careful and inspect more before acting," a good early
seed for the least-privilege/caution habits ROOT 09 formalizes much later.

**Approximate timing:** 5-8 minutes live discussion; 5 minutes self-paced writing.