SeniorCI/CD & DevOps for QA
How do you implement rollback strategies in your deployment pipeline?
- rollback
- deployment safety
- incident response
Answer it first, then compare. Nothing here is saved or scored.
Model answer
Rollback options: (1) Redeploy previous version: simplest, works if no database changes. (2) Feature flag disable: turn off the problematic feature without deploying. (3) Blue-green switch: instant traffic switch to previous environment. (4) Database rollback: reverse migration if the schema changed (risky, test thoroughly). (5) GitRevert + redeploy: revert the commit and run the full pipeline. Best practice: decide the rollback strategy before deploying, not during an incident. Automate rollback triggers based on error rate spikes or health check failures.
What interviewers listen for
- Pipeline shapeYou design stages by failure cost and runtime budget, not by tool feature lists.
- Parallelisation craftYou can shard a real suite and explain the state-isolation choices you made.
- Quality gatesYou know which checks block merge, which warn, and why those defaults are correct.
- Shift-left fluencyYou talk about ownership transfer, not just earlier execution.