DevOps Engineer interview question · Most asked
A release worked in staging but failed in production. How do you prevent that class of problem?
Summary
Reduce unintended differences: promote the same artifact, define all environments from the same infrastructure code and manifests with small explicit overlays, keep dependency versions and feature flags in sync, and detect drift automatically with diffs and GitOps reconciliation.
Longer Answer
Some differences are intentional (scale, endpoints, credentials, data volume); document them and test scale separately. Show config and flag differences between staging and production in release PRs.
Key Points
- One artifact promoted.
- Config as code with minimal overlays.
- Same dependency versions.
- Automated drift detection.
Deep dive: DevOps in Production: It Worked in Staging
Explanation
What interviewers look for
Separating intended from accidental differences.
More most-asked DevOps Engineer questions
- Design a CI/CD pipeline for a containerised microservice from commit to production.
- Pods keep restarting with OOMKilled under load. How do you investigate and fix it?
- How do you handle database schema migrations in an automated deployment pipeline?
- How do you handle secrets in CI/CD pipelines securely?
- What happens when you type a URL into a browser and press Enter?
- A rollback after a release made the outage worse because the database had already been migrated. How do you design releases so rollbacks are always safe?
- What are DORA metrics, and how would you use them without gaming them?
- Every deployment produces a burst of 502s. What do you check?