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
4 questions in Cohesion.
-
Cohesion advanced Multiple choice
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?
2 min answer cohesionsearchbaiduboundaries -
Cohesion intermediate
A subscription-billing platform has an "invoice service" that generates invoices, sends dunning emails, computes tax, syncs to accounting systems and renders PDFs. Is that cohesive? How would you decide?
1 min answer cohesionchargebeebillingboundaries -
Cohesion intermediate Multiple choice
Every meaningful feature in a platform requires changes to at least nine services and three teams. Which architectural property has failed and what is the diagnostic?
2 min answer cohesionboundariesconways-lawspotify -
Cohesion beginner
Review this. An internal library called platform-common holds an HTTP client, a feature-flag reader, a money type, a retry helper and tenant-context propagation. 140 services depend on it. A one-line bugfix to the money type produces version 4.12.0, and until each service upgrades it is running a version missing the fix. The last upgrade wave took eleven weeks. What would you split, and what would you leave alone?
3 min answer cohesionshared-librariesversioningrelease-cadence