Quiz

2741 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 areas2741 Architecture Fundamentals81 Distributed Systems101 Data Architecture90 Cloud Architecture87 Networking86 API & Integration Architecture78 Reliability & Resilience99 Observability92 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 Architecture102 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

2741 questions.

Quiz

A cost-sensitive platform must choose between a highly available architecture and a cheaper one with a wider failure domain. How should the decision be made?

A team is asked to reduce infrastructure cost by 30%. How do you make the reliability trade-off explicit rather than accidental, and what should be cut first?

One architecture has excellent performance and mediocre reliability; another is reliable at substantially higher cost. How should the trade-off be evaluated?

What would it cost to move a service from 99.9% to 99.99% availability, and how would you decide whether it is worth it?

A communications API platform finds that adding a new messaging channel requires coordinated changes in the gateway, the billing service, the webhook dispatcher and the console UI, across four teams. What would you change about the coupling, and what should you deliberately leave alone?

A company split its monolith into 14 services. Deployments now require a coordinated release plan across teams and one user action traverses six synchronous hops. What went wrong and what would you do?

A social product is launched on top of an existing platform's identity, graph and infrastructure, and reaches 100 million users in five days. Which components are safe to borrow, which must be isolated, and what does this say about coupling?

At Meesho-scale marketplace growth, catalogue, pricing, order and logistics teams all read and write one shared product table, each deploying schema changes independently. Which kind of coupling is this, and why does it get worse rather than plateau?

A consumer fintech team proposes CQRS because their read and write workloads are very different. What evidence should be required before accepting the added synchronisation, projection and operational complexity?

A marketplace team proposes CQRS because search and browse read patterns differ sharply from the transactional write model. What evidence should be required before accepting the extra synchronisation and projection complexity?

A search index built by a projection has been serving wrong results for three weeks because of a bug in the projection logic. Walk through recovery.