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

34 questions in Reliability & Resilience.

Quiz

Two service instances each run at 60% CPU behind a load balancer. Is that redundant?

A service runs across three availability zones at 70% CPU during peak. The team wants to survive losing one zone at peak with no user impact. Roughly what does that require, and what does the same arithmetic say about running across two zones?

An organisation adopts blameless postmortems but engineers still avoid admitting mistakes and incidents are under-reported. What is missing beyond the stated policy?

A team is launching a new service and asks what its SLO should be. How do you help them decide, and why is "99.99%" usually the wrong first answer?

The business asks for "100% uptime" for a new customer portal. Walk me through the conversation that ends in an agreed SLO.

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

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

A service fetches a feature flag value and a database credential from central services on every request. What is wrong?

During a peak event, a platform's configuration service becomes unavailable. What should happen to the serving path, and what design property is being tested?

Explain static stability, and give two examples of designs that violate it.