Quiz

2667 questions of the kind that actually get asked — in interviews, in architecture review boards, and by the person who has to run the thing at 3 AM. Every answer states the trade-off rather than the slogan, and says when the obvious choice is the wrong one.

All areas2667 Architecture Fundamentals81 Distributed Systems101 Data Architecture90 Cloud Architecture87 Networking86 API & Integration Architecture78 Reliability & Resilience88 Observability81 Performance & Capacity Engineering90 Security Architecture95 Cost Architecture & FinOps92 Business Architecture93 Architecture Communication91 Enterprise Architecture91 Legacy Modernization92 AI-Era Architecture86 Software Architecture & Engineering84 Architecture Patterns84 Architecture Decision-Making91 The Architect's Meta-Skills92 Delivery & Release Engineering93 Platform Engineering & Developer Experience92 Testing & Quality Architecture90 Data Platform Architecture88 Streaming & Real-Time Data93 Data Governance & Semantics81 Frontend & Experience Architecture91 Edge, Mobile & IoT88 Regulatory & Data Protection Architecture90 Assurance, Audit & Model Risk88

Difficulty Any beginner intermediate advanced

80 questions in Distributed Systems.

Quiz

Your cluster fails over spuriously under load, but a real leader failure takes 45 seconds to detect. How do you resolve the tension?

A fantasy-sports platform faces a synchronised traffic spike in the minutes before a major match starts. Workers are saturated. What should be shed, in what order, and what must never be shed?

An AI inference service receives computationally expensive requests with unpredictable bursts, where a single request can occupy a GPU for many seconds. Which combination of controls should it use, and in what order do they apply?

One customer's batch job saturates a shared service and degrades everyone. Rate limiting them fixes it, until the next customer does the same. What is the structural answer?

Your service is at capacity and must reject some traffic. What do you shed, and how do you decide?

Your service will exceed capacity by 30% during a known peak. Do you shed load or brown out, and how do you decide what goes first?

A flash sale causes an incident. Two hours later the fault is fixed but 4 million jobs are backed up and notifications are hours late. Walk through recovery and prevention.

A dependency degrades to 2-second latency rather than failing outright, and retries triple the load on it. Why is slow worse than down, and which mechanisms actually prevent the amplification?

A dependency degrades. Your service retries three times with exponential backoff. The dependency never recovers until you deploy a change. Why?

During a regional degradation, a mobility platform's services perform millions of retries against a slow dependency, and the dependency never recovers until traffic is manually cut. Analyse the failure and identify which four controls would have prevented it.

A long-running customer workflow spanning payment, verification, notification and fulfilment must survive worker crashes and deploys mid-flow. Compare a hand-written saga with a durable-execution engine.

A marketplace charges the customer, pays the merchant, pays the courier and takes a fee. Design the transaction, and say what happens if the courier payment fails.