Quiz

2667 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 areas2667 Architecture Fundamentals81 Distributed Systems101 Data Architecture90 Cloud Architecture87 Networking86 API & Integration Architecture78 Reliability & Resilience88 Observability81 Performance & Capacity Engineering90 Security Architecture95 Cost Architecture & FinOps92 Business Architecture93 Architecture Communication91 Enterprise Architecture91 Legacy Modernization92 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

Difficulty Any beginner intermediate advanced

84 questions in Software Architecture.

Quiz

A team's technical debt backlog contains hundreds of items and never shrinks. How should debt be managed?

Engineering says the codebase is full of technical debt. The business hears "we want to stop delivering and tidy up". How do you reframe it?

To hit a launch date, a 60-engineer marketplace organisation of eBay's shape stops all technical debt work for two quarters. Nothing is deleted, no dependency is upgraded, no flake is fixed. Assume the launch succeeds. What degrades, in what order, and what becomes genuinely irreversible?

You need budget for a year of technical debt work. Leadership has repeatedly declined. How do you make the case?

A product team's test suite is slow and flaky, and removing tests causes escapes. What testing strategy resolves this?

A team's test suite is slow, flaky and gives little confidence. What shape should the strategy have, and what determines it?

An end-to-end suite has 200 tests. Each fails spuriously about 1% of the time, independently of the others. Roughly what fraction of runs on correct code go red anyway?

An end-to-end suite takes 40 minutes and fails randomly twice a week. What do you change?

A repository takes 420 merge attempts a day. The merge queue validates one change at a time against the current tip and the suite takes 22 minutes. Developers now wait hours to land anything. Which change raises landed merges per day the most?

A team wants to move from long-lived branches to trunk-based development. What must be in place first?

A trading platform's team wants trunk-based development, but a bad deploy has financial consequences. Are the two compatible?

What has to be true before a team can safely move to trunk-based development?