Fault Tolerance and Failure Scenarios Questions
Designing systems resilient to component failures: timeouts, retries with exponential backoff, circuit breakers, bulkheads. Discuss cascading failure prevention and graceful degradation. At Staff level, demonstrate thinking about multi-layer failures (service failures, database failures, network partitions) and how to detect and recover from them.
EasyTechnical
93 practiced
Explain the difference between a timeout and a deadline in a distributed microservice context. Give concrete examples of when to use short client-side timeouts versus longer server-side deadlines, describe how they interact to prevent resource leaks and runaway work, and explain how deadlines should influence retry and cancellation policies.
MediumSystem Design
79 practiced
Design a bulkhead strategy for a single service that handles both critical payment processing and best-effort analytics ingestion. Include process isolation, thread pools, connection pools, circuit breakers, and resource quotas so analytics failures cannot impair payment processing.
HardTechnical
86 practiced
Discuss approaches for end-to-end cancellation and deadline propagation across asynchronous chains that include HTTP calls, message queues, and background workers. Describe practical mechanisms (context objects, headers, cancellation tokens), limitations when work is buffered, and strategies to abort safely without leaving inconsistent state.
MediumTechnical
64 practiced
Implement a thread-safe exponential backoff with full jitter function in Python 3 that retries a callable. The function should accept callable, max_attempts, initial_delay_ms, multiplier, max_delay_ms, and max_total_time_ms, and should raise the last exception if all retries fail. Do not use third-party retry libraries and ensure accurate timing in the presence of exceptions.
HardTechnical
68 practiced
Design a recovery and reconciliation algorithm for an eventually-consistent distributed cache that may serve stale reads after failover. The solution should limit load on the origin store during cache warm-up, prioritize critical keys, and converge to the latest state without overwhelming downstream services or showing duplicate/inconsistent results to users.
Unlock Full Question Bank
Get access to hundreds of Fault Tolerance and Failure Scenarios interview questions and detailed answers.
Sign in to ContinueJoin thousands of developers preparing for their dream job.