# Reflection: You Proved Persistence, You Didn't Just Trust It

## Reflection questions

1. Before this module, would you have assumed container data persists by default? How
   expensive would that wrong assumption be in a real production incident?
2. Why did this module insist on actually DESTROYING a container to test persistence, rather
   than just describing the concept?

## Real Ops takeaway

**"I assumed it would persist" is one of the most expensive assumptions in real operations
work.** You didn't just learn that volumes persist data — you personally destroyed a container
and confirmed data loss, then destroyed another and confirmed data survival, with the SAME
sequence of commands each time except for one deliberate volume configuration. That's the level
of confidence "verify, don't assume" is supposed to give you, and it's exactly the discipline
ROOT 02's troubleshooting framework already built.

This module is complete. Continue to the next module.

## Instructor Notes

**Discussion questions for a live classroom:** question 1 works well as a real cautionary
example — ask if anyone has heard of (or experienced) a real data-loss incident caused by this
exact wrong assumption.

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