# Reflection: One Model, Reused Everywhere From Here On

## Reflection questions

1. Before this module, how would you have described "the network is broken" to a colleague?
   How would you describe it now, more precisely?
2. This module deliberately avoided subnet math. Do you feel that cost you anything real, given
   the module's actual goal (reasoning about WHERE a failure is, not calculating addresses)?

## Real Ops takeaway

**Every networking topic for the rest of ROOT_ is this same chain, viewed from a different
altitude.** A container's published port is still "port," a Kubernetes Service is still "how do
I reach the right destination via a stable address," Ingress is still "routing decisions," and
NetworkPolicy is still "which subnets/ports are allowed to reach which." You are not about to
learn a new mental model in ROOT 04 or ROOT 05 — you're about to see this SAME one applied one
layer up, repeatedly. That's why this module got extra weight: the investment compounds.

This module is complete. Continue to Module 4, where these ideas become real commands.

## Instructor Notes

**Discussion questions for a live classroom:** question 1 is worth collecting several answers
before and after — the change in precision is itself the evidence this module worked.

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

**Milestone note:** this is the "critical module" this course was built around — consider
confirming as a group that everyone can walk the full chain (host→interface→IP→subnet→gateway→
routing→DNS→port→TCP/UDP→application) from memory before moving on.