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
3 questions in Application Performance Monitoring.
-
Application Performance Monitoring advanced
At 09:07 UTC a CDN route recovers and a queued asset is released. Within seconds the API gateway sees roughly 1.5 million requests per second, about three times its normal peak. Gateway tasks start failing health checks and being replaced, though CPU never saturates and the upstream services look healthy. Canva published this incident for 12 November 2024. Where is the time going, and what do you look at first?
4 min answer canvaapminstrumentation overheadthundering herd -
Application Performance Monitoring advanced
In a multi-tenant platform, aggregate application performance metrics look healthy while specific tenants experience severe slowness. What must performance monitoring do differently?
2 min answer apmmulti-tenancysegmentationoutliers -
Application Performance Monitoring advanced
Review this instrumentation. A checkout service emits about 400 spans per request, every span carries roughly 30 attributes including the full request body, tracing runs at 100% with no sampling, and the team reports that they cannot find anything in the traces. What would you remove, what would you change, and what would you keep even though it looks excessive?
3 min answer tracingapminstrumentationsampling