Quiz

2627 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 areas2627 Architecture Fundamentals81 Distributed Systems101 Data Architecture90 Cloud Architecture77 Networking86 API & Integration Architecture78 Reliability & Resilience88 Observability81 Performance & Capacity Engineering90 Security Architecture85 Cost Architecture & FinOps82 Business Architecture93 Architecture Communication91 Enterprise Architecture91 Legacy Modernization82 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

88 questions in Reliability & Resilience.

Quiz

A service depends on four components, each independently 99.9% available, called in sequence on every request. What is the resulting availability, and what does this imply about architecture?

A stakeholder requires 99.99% availability. Your service depends on five internal services each offering 99.9%. What do you say?

A stakeholder wants a video streaming service at 99.99% availability. Walk through whether that is the right target and what it would take.

A dependency fails only under high load, so normal testing never exposes it. How should load testing, fault injection, capacity experiments and traffic shadowing be combined to find it?

A mobility platform wants to start chaos engineering. Its dispatch system is business-critical and the team is nervous. What is a responsible starting sequence, and what must exist first?

A team wants to adopt chaos engineering after reading about it. What must be in place first, what is the correct progression, and what does chaos engineering not tell you?

Leadership read about Chaos Monkey and wants chaos engineering in production next month. Your last three incidents were caused by known unfixed reliability issues. What do you say?

What is the first chaos experiment you would run on a system you have just inherited, and what must be in place first?

A crypto aggregator's upstream exchange feeds become unreliable during extreme market volatility - the moment users most need them. How should stale data, provider failover, breakers, caching and user-facing warnings interact?

An e-commerce platform designs explicit degradation modes for extreme demand events. What must be true of the mode ladder for it to work on the day?

Define three degradation modes for a real-time marketplace. What triggers each, what stops working, and how does the system return to normal?

A core internal service has run continuously for three years. What risk does that create?