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

1018 questions.

Quiz

What must be designed for internationalisation on day one, and what can genuinely wait?

A monolith is moved to Kubernetes and the team discovers pod restarts drop in-flight requests and kill long-running jobs. What is actually happening, and what must be configured?

A team of five running four services wants to adopt Kubernetes. Do you support it?

An enterprise SaaS company grows from one cloud account to hundreds across many teams. What structure prevents this from becoming ungovernable, and what is the wrong way to impose it?

A layered architecture is described as outdated. When is it still the right choice, and what is its real limitation?

A team applies a strict layered architecture and finds every change touches nine files. Is layering wrong, or is the application wrong?

Your company runs two data centres and wants automatic database failover between them. What is missing?

A replacement for a 16-year-old claims system passed every acceptance test and went live. Six weeks later the reinsurance return it produced was rejected by finance, and nothing in the test pack was wrong. An interviewer asks how you would have found that gap during the assessment. What do you say?

A team inherits a system nobody fully understands and is asked whether to rewrite it. What should be established before answering?

Before modernising, a team must assess a legacy system. What should the assessment measure, and what is usually skipped?

On Salesforce's Force.com platform, a customer's custom objects and fields are rows of metadata in shared tables rather than a schema of their own (Weissman and Bobrowski described the design at SIGMOD in 2009). What does that remove from the legacy problem, and what does it not remove?

A modern service must read from a legacy system that offers only nightly batch files and a synchronous interface that cannot handle concurrent load. What integration approach fits?