Your company wants to run a critical service active-active in two cloud regions. What are the main DevOps challenges and how would you handle them?
What the interviewer wants to hear
- Data replication and consistency is the hardest part
- Global traffic routing and failover with health checks
- Deploy region by region, never both at once
- Identical infrastructure through IaC; avoid drift
- Test failover regularly; capacity for one region to take all load
Model answer
The hardest part is data. I would work with developers to decide which data needs strong consistency and which can be eventually consistent, and pick a database that supports multi-region writes or route writes for each record to a home region to avoid conflicts. For traffic, a global load balancer or latency-based DNS with health checks sends users to the nearest healthy region. Both regions are built from the same IaC modules so they stay identical. Releases go region by region, with a bake time and automatic rollback, so one bad change cannot take down both. Each region must have enough capacity, or fast autoscaling, to take all traffic if the other fails. Most importantly, we practise failover with regular game days, because untested failover usually fails when you need it. Cost and cross-region data transfer also need tracking.
Can you answer it under time pressure?
Take a timed hard round and get scored on every answer.
More hard DevOps Engineer questions
- You are asked to build an internal platform so 30 product teams can deploy services to Kubernetes on their own. How would you design it?
- How would you secure the software supply chain from source code to a running container in production?
- Your DORA metrics show a 30% change failure rate and long recovery times. How would you bring them down without slowing teams down?
- How do you plan and carry out a Kubernetes version upgrade for production clusters with minimal risk?
- Leadership asks you to cut the cloud bill for your Kubernetes platform by 30 percent without hurting reliability. How do you approach it?
- You are the incident commander for a major outage affecting all customers. Describe how you run the incident from first page to postmortem.
- Design CI/CD for a monorepo with 60 services and 200 engineers where full builds take over an hour.
- Design a disaster recovery plan for a platform whose business requires an RTO of 1 hour and an RPO of 5 minutes for the loss of a whole cloud region.
- Several teams will share one Kubernetes cluster. How would you isolate tenants and secure the cluster?