DevOps Engineer interview question · Most asked
How do you plan and test disaster recovery as a DevOps engineer?
Summary
Agree on RTO and RPO per system with the business, choose a recovery strategy that meets them (backup and restore, pilot light, warm standby, active-active), automate the recovery steps (infrastructure as code, scripted restores, DNS failover), and test them regularly with real restores and failover exercises, measuring actual recovery times.
Longer Answer
Common gaps found in tests: backups that cannot be restored (missing keys or permissions), restores far slower than expected, dependencies forgotten (DNS, secrets, container registries, third-party services), runbooks that are out of date, and knowledge held by one person. Store backups in separate accounts or regions with immutability to survive ransomware or account compromise.
Key Points
- RTO/RPO per system.
- Strategy to match objectives.
- Automate recovery; test regularly.
- Isolated, immutable backups.
More most-asked DevOps Engineer questions
- Design a CI/CD pipeline for a containerised microservice from commit to production.
- What are DORA metrics, and how would you use them without gaming them?
- 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?
- Your CI pipeline takes 45 minutes. How would you speed it up?
- How do you secure the CI/CD pipeline itself against supply-chain attacks?
- What does 'build once, deploy many' mean, and why does it matter?