Quiz

2868 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 areas2868 Architecture Fundamentals91 Distributed Systems101 Data Architecture90 Cloud Architecture87 Networking86 API & Integration Architecture87 Reliability & Resilience99 Observability92 Performance & Capacity Engineering90 Security Architecture95 Cost Architecture & FinOps92 Business Architecture93 Architecture Communication102 Enterprise Architecture100 Legacy Modernization92 AI-Era Architecture96 Software Architecture & Engineering93 Architecture Patterns94 Architecture Decision-Making101 The Architect's Meta-Skills102 Delivery & Release Engineering103 Platform Engineering & Developer Experience92 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

Difficulty Any beginner intermediate advanced

92 questions in Platform Engineering.

Quiz

A product team commits to 99.95% availability. Their service depends on your platform's ingress, config service and secret manager. What do you tell them?

Application teams say the platform is unreliable. The platform team's dashboard shows 99.95% on every component. How do you resolve this?

Should an internal platform have SLOs, and what should they cover?

Why should a platform publish SLOs to internal consumers, and what should they cover?

A team of six owns nineteen services and is missing every deadline. They ask for more engineers. Is that the right answer?

How should platform work be organised as an organisation grows, and what structure prevents the platform becoming a bottleneck?

Six platform engineers support forty product teams. Each team raises roughly 1.5 requests a week and each request costs about 90 minutes of an engineer's time once the context switch is counted. Roughly how much of the team's capacity is interrupt work and what does that number rule in or out?

A platform team cannot tell which of its capabilities are used, by whom, or whether they are working. What telemetry does a platform need about itself?

On 11 December 2024 OpenAI rolled a new telemetry service across its Kubernetes fleet. Staging was clean; the change reached every cluster in under thirty minutes; all services degraded for roughly four hours. What is the failure chain, and which of its links is the one to design against?

What should a platform team measure about its own platform, and what is most often missing?

A platform serves internal teams with very different scale and criticality. Should they share infrastructure?