What's a good rollback strategy?
mediumAnswer
- (1) Previous model version always available in registry.
- (2) Deployment supports instant revert (K8s rolling update revert, feature flag toggle).
- (3) Automated triggers: on-guardrail-breach → auto-rollback.
- (4) Manual: single-command / one-click.
- (5) Monitor rollback executed correctly (metric returns to baseline).
- (6) Post-mortem after rollback: what broke + how to prevent.
- Rule: rollback should be seconds to minutes, not hours.
- Practice quarterly.
Check yourself — multiple choice
- Random
- Previous version in registry + instant revert mechanism + auto trigger on guardrail + manual one-click + verify metric returns + post-mortem; seconds-to-minutes speed; practice quarterly
- Just redeploy
- Not real
Rollback: previous ready + instant revert + auto trigger + practice.
#deployment
Practise MLOps & Data Quality
215 interview questions in this topic.