Portfolio ↗

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
Difficulty Any beginner intermediate advanced

4 questions in Showback & Chargeback.

  1. Showback & Chargeback intermediate

    A platform team wants engineering teams to reduce their infrastructure spend. Does showback or chargeback work better, and what determines the answer?

    2 min answer posthogshowbackchargebackincentives
  2. Showback & Chargeback intermediate

    An enterprise is deciding between showback and chargeback for cloud costs. What does each achieve, and what goes wrong with chargeback?

    2 min answer showbackchargebackincentivesgovernance
  3. Showback & Chargeback intermediate

    Cloud spend is growing faster than revenue and no individual team feels responsible. How should cost allocation be designed to actually change behaviour?

    2 min answer finopsshowbackchargebackallocation
  4. Showback & Chargeback intermediate

    Review this cost programme - a monthly per-team spend report circulated as a PDF, a quarterly 5% efficiency target for every team, an enforced tagging policy, and one analyst who files optimisation tickets. Tag coverage is 97% and cost per request has not moved in a year. What would you remove, what would you change, and what would you leave alone?

    3 min answer showbackfeedback-latencydesign-reviewefficiency-targets