Choose the operational result that the available evidence supports. Each answer tests a boundary that a single green controller signal cannot establish.
Review these lessons
- Mesh identity: require encrypted peers and narrow service access
- Database pool pressure: bound waiting before the database collapses
- Node autoscaling: make pending Pods schedulable before traffic rises
- Event schema evolution: release consumers before new event shapes
- DNS cutovers: budget for resolver caches and mixed destinations
- Synthetic transactions: measure the route a user actually takes
Other checks
- DevOps checks
- DevOps stateful operations decisions
- DevOps operations decisions
- DevOps advanced delivery decisions
Common Mistakes
- Do not treat a cached DNS answer as a failed zone edit without checking delegation.
- Do not infer a successful business write from an HTTP health response.