Fault Tolerance, High Availability, and Disaster Recovery Questions

Keeping a system serving despite failure, from code-level resilience to infrastructure-level recovery: circuit breakers, retries with backoff and jitter, timeouts, bulkheads, graceful degradation, and preventing cascading failures, alongside redundancy, failover (active-active versus active-passive), RPO and RTO objectives, backup and restore, and multi-region failover. Covers dependency-failure isolation, chaos engineering to validate resilience, failure-mode analysis, designing to nines of availability, cost-versus-availability tradeoffs, and recovery runbooks. Spans both the patterns that isolate partial failure and the disaster-recovery planning that restores a business-critical system after a major outage.

MediumTechnical
89 practiced

Using the CAP theorem, walk through the trade-off you'd make for a financial ledger service versus an analytics event aggregator. Which guarantee does each give up during a network partition, and why?

MediumTechnical
72 practiced

Define cascading failure and walk through a realistic example: service C fails, B (which depends on C) gets overloaded, and A (which depends on B) starts degrading too. At each layer, what protection would you put in place to stop the cascade from propagating?

HardTechnical
88 practiced

You're given a timeline from an outage: a database compaction job triggers a CPU spike, latency breaches its SLO, the autoscaler overreacts and adds pods, network queues fill up, a leader election kicks off, and the system ends in a multi-region failover. Walk through a structured root-cause analysis: the immediate cause, the contributing factors, and at least three long-term changes you'd prioritize to prevent a repeat.

EasyTechnical
134 practiced

What does a disaster recovery runbook actually need to contain to be useful during a real region failure? Walk through the essential sections: owner, RTO/RPO, step-by-step actions, and verification.

HardTechnical
63 practiced

Two regions running asynchronous replication get network-partitioned, and both keep accepting writes. When the partition heals, how do you detect the divergence and reconcile the conflicting writes?

Unlock Full Question Bank

Get access to all Fault Tolerance, High Availability, and Disaster Recovery interview questions and detailed answers.

Sign in to Continue

Join thousands of developers preparing for their dream job.