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

38 questions in Architecture Fundamentals.

Quiz

A search company must decide where the rules deciding which documents are eligible to appear for a query should live - the crawler, the indexer, the query serving layer, or a dedicated component. Which choice best reflects cohesion?

A B2B marketplace splits into supplier-onboarding, catalogue, pricing and fulfilment services. Eighteen months later every meaningful feature requires all four teams. What does Conway's Law say happened, and what are the two available fixes?

What happens if an edge platform's configuration system is built by three teams - one owning the config language, one owning global propagation, one owning the edge runtime - and each team ships on its own schedule with its own API? Predict the architectural consequence.

You design service boundaries along domain lines. They cut across three existing teams. What happens and what do you do?

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?

A frequently written table needs a column renamed and its type changed. The service runs many instances and cannot be stopped. How do you do it and remain able to roll back at every step?

A services marketplace launches in one city with one category. Three years later it runs dozens of categories across many cities with different pricing and compliance rules. What should have been built on day one, and what should deliberately not have been?

"Interview. You are the architect for a grocery marketplace where item availability changes constantly. Name three fitness functions you would put in CI to protect the architecture, and explain what each one would have caught." What makes a strong answer?

Architecture decisions in your organisation are either ignored or bottlenecked in a review board. Design something better.