# Reflection: You Fixed the Real Problem, Not the Suspected One

## Reflection questions

1. Before running any commands in this module's Lab, what would you have guessed was broken?
   Was your guess right?
2. Why does correctly categorizing a failure (DNS vs. routing vs. TCP vs. application) matter
   more than just "trying things until something works"?

## Real Ops takeaway

**"DNS must be broken" is one of the most common wrong first guesses in real incident response
— and disproving or confirming it takes seconds, not minutes.** The habit this module builds —
categorize the failure precisely before attempting a fix — is what separates a five-minute
diagnosis from an hour of trying unrelated things. This exact reasoning, applied to Kubernetes
Services/Ingress/DNS later, is one of the most valuable transferable skills in this entire
program.

This module is complete. Continue to the final module of this course.

## Instructor Notes

**Discussion questions for a live classroom:** question 1 works well as a live poll before
revealing the Lab's actual root cause — the gap between instinct and evidence is the lesson.

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