Top 4 Graceful degradation Interview Questions
Browse 4 real-world technical and behavioral interview questions about Graceful degradation. Review scenarios, edge cases, and architectural best practices.
One managed service in your primary region is having a bad day and your product is down with it. What can you do during the outage, and what should you have designed before it?
During the event your only levers are the ones already built: fail over, serve degraded from cache, or shed the dependent feature. Beforehand the work is finding your transitive dependencies on foundational services, making the running system statically stable, and choosing which features are allowed to fail alone.
A network blip lasting under a minute leaves two database primaries having each accepted writes, and you spend the next day degraded. Why does a short fault produce a long recovery, and what would you have changed?
Recovery time is set by how much state diverged, not by how long the fault lasted, so seconds of dual writes can take a day to reconcile. The prevention is a single writer enforced by quorum and fencing; the mitigation is designing the write path so repair is mechanical rather than forensic.
Checkout calls pricing, tax, fraud, inventory and a session store. Which of those are you willing to carry on without, and what does the shopper see?
Sort each dependency by what the loss looks like. Price and payment authorisation must fail closed because the loss is unrecoverable; personalisation degrades silently. Tax and fraud sit between, and the answer is a written policy with a bounded exposure, not a timeout value.
You promise 99.9 percent availability and you call five services that each promise the same. What have you committed to?
Nines only mean something as a downtime budget over a stated window, and dependencies in series multiply: five hard dependencies at three nines each put your own ceiling near 99.4 percent, so the target is met by removing dependencies from the critical path rather than by asking each owner for more nines.