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
5 questions in DORA Metrics.
-
DORA Metrics intermediate
A team measures deployment frequency, lead time, change failure rate and recovery time. How should these be used, and how are they misused?
2 min answer verceldorametricsdelivery -
DORA Metrics intermediate
An organisation adopts delivery metrics and teams begin optimising the numbers rather than the outcomes. What went wrong, and how should the metrics be used?
2 min answer dorametricsgoodhartoutcomes -
DORA Metrics intermediate
An organisation adopts the four DORA metrics and delivery does not improve. What are the metrics for, and how are they commonly misused?
2 min answer dorametricsdeliverygoodhart -
DORA Metrics advanced
Deployment frequency is monthly and change failure rate is 30%. Which do you attack first and why?
2 min answer dorabatch-sizedeploymentstability -
DORA Metrics intermediate
Etsy released StatsD in 2011 alongside a blog post titled "Measure Anything, Measure Everything". The client sends UDP packets and does not care whether anything is listening. What problem forced that design, and what does it have to do with deploying many times a day?
2 min answer etsystatsdinstrumentationudp