Mid-LevelCI/CD & DevOps for QA
What is blue-green deployment and how does QA validate it?
- blue-green
- deployment strategy
- validation
Answer it first, then compare. Nothing here is saved or scored.
Model answer
Blue-green maintains two identical production environments. "Blue" serves live traffic while "green" gets the new release. After green passes validation, traffic switches to green. QA role: (1) Smoke test the green environment before switching. (2) Verify critical paths, login, core business flows. (3) Validate data compatibility - does the new version work with the existing database? (4) Test rollback - can you switch back to blue if issues arise? (5) Monitor after switch - compare error rates and performance between blue baseline and green.
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.