Portfolio ↗

Quiz

2948 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 areas2948 Architecture Fundamentals91 Distributed Systems101 Data Architecture90 Cloud Architecture87 Networking96 API & Integration Architecture87 Reliability & Resilience99 Observability92 Performance & Capacity Engineering100 Security Architecture105 Cost Architecture & FinOps102 Business Architecture103 Architecture Communication102 Enterprise Architecture100 Legacy Modernization102 AI-Era Architecture106 Software Architecture & Engineering93 Architecture Patterns94 Architecture Decision-Making101 The Architect's Meta-Skills102 Delivery & Release Engineering103 Platform Engineering & Developer Experience102 Testing & Quality Architecture102 Data Platform Architecture98 Streaming & Real-Time Data103 Data Governance & Semantics91 Frontend & Experience Architecture101 Edge, Mobile & IoT98 Regulatory & Data Protection Architecture99 Assurance, Audit & Model Risk98
Difficulty Any beginner intermediate advanced

4 questions in Component Contracts.

  1. Component Contracts intermediate

    A design system releases 4.3.0. The changelog says no breaking changes. Eleven of forty consuming applications report broken layouts. Review the versioning policy - what is wrong with it?

    3 min answer design-systemscomponent-contractssemverimplicit-coupling
  2. Component Contracts advanced

    A platform team's design system ships connected components - an avatar that fetches the user from its id, a price tag that calls the pricing service from a sku, and a notification bell that opens its own WebSocket. Forty applications consume it. The package is 180 KB compressed and the bell is in the shared header on every page. Review this. What would you remove, what would you keep, and what would you leave alone even though it looks wrong?

    2 min answer design-systemcomponent-contractscouplingwaterfall
  3. Component Contracts intermediate

    A team asks for a new prop on a shared component. When do you say no, and what do you offer instead?

    2 min answer design-systemapi-surfacecompositioncontracts
  4. Component Contracts intermediate

    What makes a shared component's interface stable enough that consumers can upgrade without breakage?

    1 min answer component-apicontractsversioningcomposition