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
5 questions in Branching Models.
-
Branching Models intermediate
A design platform in the mould of Canva moves 90 engineers off long-lived feature branches onto trunk-based development with a merge queue. Six weeks later the mean branch still lives four days and the trunk is no healthier. Review this change. What did they actually need to change?
2 min answer canvatrunk-based-developmentcode-reviewbranch-lifetime -
Branching Models intermediate Multiple choice
A platform with many teams and frequent releases must choose a branching model. What decides it?
1 min answer branchingtrunk-basedrelease-branchesprerequisites -
Branching Models intermediate Multiple choice
A product ships versioned software that customers install and run themselves. Three major versions are under support and security fixes must reach all of them. Which branching model fits?
2 min answer branchingrelease-branchestrunk-basedsupported-versions -
Branching Models beginner
A team keeps `main` for the current release and `develop` for the next one, and every hotfix is cherry-picked into both. Last quarter two fixes that shipped in `main` were missing from the next release, and a customer re-reported a bug that had been closed six weeks earlier. What failed, and which design decision allowed it?
3 min answer branchingcherry-pickpatch-idrelease-branch -
Branching Models intermediate
Sixty engineers work on branches that live five days on average before merging. Estimate what that lifetime costs per year, and say which assumption dominates the error.
3 min answer branchingtrunk-basedmerge-conflictsrework