ExpertDistinguishedDistributed Systems & Scale75 minutesPro answer

SDV-008

Degrade a dependency graph under severe overload without guessing

Turn business priority and dependency criticality into coordinated admission, brownout, and recovery policies across a large service graph.

Load SheddingBlast RadiusReliabilitySlo

Interview prompt

Problem context

A marketplace has 180 services and several fan-out paths. Flash demand plus a degraded database causes retries, queue growth, and pool exhaustion. Teams independently tune timeouts and circuit breakers, so local protections sometimes amplify global failure. Define an architecture and governance model for graceful system-wide degradation.

Skills being evaluated

systems thinkingoverload controlpolicy governancecross-team reliability

The full reasoning guide is part of Pro

The scenario and evaluation focus above remain public. Pro unlocks the structured answer, trade-off analysis, follow-up probes, common weak answers, rubric, related reasoning, and any architecture diagram.

Sign in to continue

What the full guide covers

Clarify the decision
Establish scale assumptions
Functional and non-functional requirements
High-level architecture
Data model and flow
Consistency and transaction boundaries
Failure modes and recovery
Security and privacy
Observability and SLOs
Capacity and cost
Alternatives and trade-offs
Evolution and migration
What Staff and Principal candidates should emphasize