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

45 questions in Cost & FinOps.

Quiz

A year into chargeback every product team's reported infrastructure cost is down between 15% and 25%. Company cloud spend is up 8%. Tag coverage is 100% and no commitment expired. Where is the money going, and what would you look at first?

A training pipeline runs on 400 interruptible GPU instances checkpointing every 30 minutes. Regional demand spikes and reclamation goes from a handful of instances an hour to most of the fleet inside ten minutes. What happens minute by minute, and what stops it?

The Hugging Face Hub held over 30 PB of models and datasets in Git LFS repositories where every new checkpoint version was stored in full. Sequence the move to chunk-level deduplicated storage under live traffic, and say where the saving actually comes from.

A company evaluating whether to move a workload off public cloud computes a lower monthly infrastructure bill for owned hardware. Which costs does that comparison typically omit?

A platform team spends about 11% of its engineering capacity staying portable - an internal interface over the managed queue, nightly exports of vendor-held data, and an annual paper exit. Finance asks what that buys. What has the team actually purchased, and when is paying for it irrational?

A database vendor removes its free tier to control cost. How should a platform team model the true cost of serving many tiny tenants, and which architectural choices change the economics?

An AI inference platform's margin depends on GPU utilisation. Which levers actually change unit economics, and in what order?