Quiz

2707 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 areas2707 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 Architecture96 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 Architecture98 Streaming & Real-Time Data93 Data Governance & Semantics91 Frontend & Experience Architecture91 Edge, Mobile & IoT88 Regulatory & Data Protection Architecture90 Assurance, Audit & Model Risk98

Difficulty Any beginner intermediate advanced

2707 questions.

Quiz

One availability zone becomes unavailable. Walk through what happens to a typical three-tier application and what you would have changed.

Three copies of a service run in three availability zones behind one load balancer. A regional event takes all three out inside the same minute although no data centre lost power or cooling. Which property of availability zones explains why the physical separation did not help?

What is cell-based architecture, what does it actually buy, and how do you decide cell size and routing?

A grocery platform integrates with retail partners whose inventory data varies in freshness, completeness and reliability. How should the integration be designed so one partner's bad data does not degrade the whole platform?

An enterprise integration platform connects to many customer identity systems with different reliability and behaviour. How should directory sync, SSO and webhook processing be isolated?

Partner integrations take four months from contract signature to production traffic. Engineering says the work is three days. Where does the time go and how do you cut it?

You must make a breaking change to an API used by 5000 partner organisations. What is your plan?

A bug in a streaming job produced wrong results for three weeks. How should the backfill be designed so it does not cause a second incident?

A bug is found in a stream processor that has been running for a month. How should the correction be handled?

A logic bug means six months of a derived table are wrong. You must reprocess without disrupting live consumers. How?

A logic bug means the last 10 days of a derived table are wrong. An engineer proposes resetting the running consumer group's offsets back 10 days and letting the job reprocess. What does that actually do?