Quiz
2627 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 areas2627
Architecture Fundamentals81
Distributed Systems101
Data Architecture90
Cloud Architecture77
Networking86
API & Integration Architecture78
Reliability & Resilience88
Observability81
Performance & Capacity Engineering90
Security Architecture85
Cost Architecture & FinOps82
Business Architecture93
Architecture Communication91
Enterprise Architecture91
Legacy Modernization82
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
84 questions in Software Architecture.
-
Bounded Contexts advanced
A payments platform has one Payment entity used by checkout, settlement, refunds, reconciliation and reporting, and it has grown to eighty fields. What is the problem and what is the fix?
2 min answer razorpaybounded-contextdddmodel -
Bounded Contexts intermediate
Review this context map. Eleven bounded contexts, and nine of the relationships between them are shared kernel: a common library of domain types that every team imports and any team may change. The teams report that releases have to be coordinated. What would you change, what would you keep, and how would you argue it?
2 min answer domain driven designbounded contextsshared kernelcoupling -
Bounded Contexts advanced
Two teams disagree about whether "reservation" and "booking" are one concept or two. What evidence settles it?
2 min answer bounded-contextslanguageevidenceboundaries -
CI/CD advanced
A developer platform's CI system faces a burst of builds after a major release. How should queues, workers, caching and prioritisation prevent collapse?
2 min answer ci-cdqueuesprioritisationcaching -
CI/CD advanced
A team has a fully automated pipeline and still releases monthly. What is actually blocking them?
2 min answer ci-cdbatch-sizebranchingfeature-flags -
CI/CD beginner
A team's CI pipeline takes 40 minutes. Everyone agrees that is annoying but tolerable, because engineers do other work while they wait. Why does the 40 minutes change what engineers do rather than only how long they wait?
2 min answer ci cdfeedback loopbatch sizeflaky tests -
CI/CD intermediate
Your monorepo runs 320 pipelines a day. Median wait before a runner picks up a job is 11 minutes; the pipeline itself takes 14. Finance asks whether doubling the runner pool is worth $9k a month. Work out the number that answers them.
2 min answer ciqueueingdeveloper experiencecost -
Clean Architecture intermediate Multiple choice
A service calls a payment provider over HTTP. The provider occasionally returns 503 and occasionally times out. In a domain / application / adapter layering, which layer should own the retry and backoff policy?
3 min answer clean architecturehexagonalretrieslayering -
Clean Architecture intermediate
A team adopts a layered architecture with strict dependency rules and finds every small change touches many files. Is the architecture wrong, or the application of it?
2 min answer clean-architecturelayersindirectionpragmatism -
Clean Architecture intermediate
Review this design. Every repository method opens its own transaction and commits before returning. One use case calls four repositories and then publishes an event. Support reports occasional orders with a payment row and no shipment row. What would you change and what would you leave alone?
3 min answer clean architectureunit of worktransactionsoutbox -
Clean Architecture advanced
When is clean architecture over-engineering, and what is the signal that you have its costs without its benefits?
2 min answer clean-architectureanaemic-domainover-engineeringcost -
Code Review intermediate
A 40-engineer platform organisation requires two approvals on every pull request. Median time from ready-for-review to merge is 26 hours. A staff engineer proposes one approval plus mandatory post-merge review for low-risk changes. What is gained, what is paid, and when does the bill arrive?
2 min answer code reviewlead timechange failure ratecodeowners