Top 8 Resilience Interview Questions
Browse 8 real-world technical and behavioral interview questions about Resilience. Review scenarios, edge cases, and architectural best practices.
One tenant bursts to ten times their normal traffic and every other customer's latency doubles. Your global rate limit was never hit. How would you design for fairness instead?
A global limit protects the service from overload but says nothing about how capacity is divided, so one tenant can consume most of it while staying under the ceiling. Fairness needs per-tenant accounting: a token bucket for the steady-state contract, a concurrency limit so expensive requests cannot hog workers, and round-robin queueing so a burst queues behind itself.
A dependency that normally answers in 80ms starts taking eight seconds. What in your service reacts, and in what order?
A timeout shorter than the caller's patience is the only defence that works without cooperation. Retries need idempotency, jitter and a budget or they amplify the outage; a breaker must trip on latency as well as errors; and a bulkhead is what stops one slow dependency consuming every thread.
How do you isolate a degraded dependency and halt a cascading failure before thread pool exhaustion takes down the entire microservice ecosystem?
Analyzing architectural resilience patterns, including circuit breakers, bulkheads, adaptive load shedding, and the mitigation of retry storms. Use this distributed systems answer to show the decision, trade-off, and evidence rather than a memorised definition. It also connects resilience to the point an interviewer is testing.
The business says the system must be highly available. How do you turn that into a number, and what does that number cost?
Convert the phrase into an error budget over a stated window, derived from what an outage costs the business rather than from a round number of nines. Each additional nine roughly multiplies cost, because it forces redundancy, cross-region failover and operational maturity that the previous nine did not need.
How do you prevent a malformed Kafka payload from poison-pilling a critical partition without violating strict financial audit requirements?
An architectural examination of Dead Letter Queues, atomic offset management, and schema enforcement in high-throughput Kafka consumers. Use this distributed systems answer to show the decision, trade-off, and evidence rather than a memorised definition. It also connects KAFKA to the point an interviewer is testing.
You are pushing a configuration change into the mobile core tonight. How do you stop one change taking the whole network down?
Blast radius is a property of the change process, not of the redundancy diagram - identical config applied to both halves of a resilient pair fails both. You need staged exposure with soak time, subscriber-visible health checks, a management path that survives the outage, and a rollback that has been executed.
How do you prevent a distributed frontend from becoming a single point of failure when remote modules inevitably crash or timeout?
Assess candidate's ability to architect fault-tolerant micro-frontends, manage distributed dependencies, and implement robust error handling in a Module Federation setup.
When a transatlantic cable is severed and your multi-region database inevitably enters split-brain, how do you resolve the conflicting writes without data loss?
An uncompromising examination of split-brain resolution, quorum consensus, fencing tokens, and why timestamp-based last-write-wins is fundamentally flawed. Use this distributed systems answer to show the decision, trade-off, and evidence rather than a memorised definition. It also connects databases to the point an interviewer is testing.