Quiz
2988 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 areas2988
Architecture Fundamentals91
Distributed Systems111
Data Architecture100
Cloud Architecture97
Networking96
API & Integration Architecture97
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
2 questions in UI Monorepo Strategy.
-
UI Monorepo Strategy advanced
Eleven frontend repositories consume a design system published to a private registry. The median application is four minor versions behind and a token change takes seven weeks to reach every application. The team wants one monorepo. Give the sequence under live weekly releases, where state can diverge, the point of no return, and how long it really takes.
3 min answer monorepodesign-systemsingle-version-policybuild-cache -
UI Monorepo Strategy advanced Multiple choice
Many frontend applications share components, tooling and types. Monorepo or separate repositories?
1 min answer monorepotoolingcoordinationversioning