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

88 questions in Reliability & Resilience.

Quiz

How would you test that your service degrades correctly when a dependency's latency rises tenfold?

Review this resilience programme. Chaos experiments run weekly in staging at 03:00, they inject only instance termination, results are recorded in a spreadsheet, and there is a kill switch that has never been used. What would you change, and what would you keep?

A collaborative workspace product must define RTO and RPO. The product team says "we can never lose a user's work". What does that requirement actually mean, and what does it cost?

A financial-operations platform sets one RTO and RPO for the entire business. What goes wrong, and how should they be derived instead?

A stakeholder asks for zero RPO across the estate. What does that cost and what would you propose instead?

A team documents an RPO of 24 hours because backups run nightly at 02:00 and take about 40 minutes. The last restore was attempted at the time the system was built. What is the honest recovery point objective?

In April 2022 a maintenance script at Atlassian used the wrong identifiers and deleted sites belonging to about 775 customers. Restoration took up to about two weeks for some of them, even though backups existed and were working. What property of the recovery design accounts for that gap?

A brokerage sets a single availability target of 99.9% for its whole platform. Why is that wrong, and what should replace it?

A live-streaming platform defines an SLO of "99.9% of API requests succeed". During a major event, the SLO is met while viewers report the product is unusable. What is wrong with the SLO?

A service exhausts its error budget in week two of a 28-day window. What actually happens next?

Leadership asks for "five nines" across the platform. Engineering says it is impossible. Design the response.

A marketplace's failover mechanism requires calling a control plane to provision replacement capacity. Why is this a design flaw, and what is the alternative?