Skip to main content
Your progress
0 of 4 lessons complete0%
T4 / M4.2 / Engineer TIER / ~10 min

Showback vs chargeback: module quiz

M4.2 module quiz

Ten questions. 80% to pass (8 of 10). Open book, unlimited retakes.

Answers are collapsed under each question. Answer first, then check.


Q1

Showback and chargeback differ in that chargeback:

A. Is more accurate per team
B. Covers more resource types
C. Is real-time rather than daily and batched
D. Moves actual budget between organisational units

Show answer

Correct: D. Showback informs; chargeback bills. That difference in consequence is why chargeback demands a level of allocation precision showback does not.

Q2

Most orgs should start with:

A. Showback, because it produces most of the behaviour change at a fraction of the friction
B. Chargeback, for real accountability
C. Both simultaneously, from day one
D. Neither; wait until the tagging is fixed properly before doing either of them

Show answer

Correct: A. If visibility alone changes behaviour, the friction of chargeback buys nothing. Testing that first is cheaper than discovering it after building the machinery.

Q3

Chargeback becomes an anti-pattern when:

A. Any team disputes an allocation at all, even just once in a single quarter
B. More than three cost categories exist
C. Shared services are split unevenly
D. The allocation rules are complex enough that maintaining them is its own cost centre

Show answer

Correct: D. The straightforward test: if the effort to defend an allocation exceeds the behaviour change it produces, the model is too complex.

Q4

The “internal billing engineer” anti-pattern describes:

A. Hiring a dedicated billing engineer to maintain all of the allocation rules
B. FinOps becoming a referee for allocation disputes rather than an optimization function
C. Automating the chargeback process
D. Charging back engineering time too

Show answer

Correct: B. The role drifts from finding savings to adjudicating splits, and the org loses the function it actually hired for.

Q5

Allocation, as distinct from showback and chargeback, is:

A. The same thing as chargeback, just under a slightly different label
B. A cloud provider feature
C. The underlying assignment of cost to a dimension, which both depend on
D. A reporting cadence

Show answer

Correct: C. Getting allocation right is the shared prerequisite. Arguing about showback versus chargeback before allocation works is arguing about presentation of a number nobody trusts.

Q6

Stable allocation periods matter because:

A. The cloud providers require stable reporting periods for their own exports
B. Re-allocating history makes past reports change, which destroys trust in all of them
C. They simplify the tagging policy
D. They improve query performance

Show answer

Correct: B. A number that moves after the fact cannot be reconciled against anything, and the first time a team notices it, every prior report becomes suspect.

Q7

The “fairness” pitfall in chargeback design is:

A. Pursuing perfect fairness at a complexity cost that exceeds the benefit
B. Splitting the shared costs equally across every single owning team
C. Charging back non-prod spend
D. Excluding shared services

Show answer

Correct: A. Perfect fairness is unreachable and each increment toward it costs disproportionately. Good-enough and stable beats precise and contested.

Q8

Dispute resolution should be designed:

A. Case by case, as they arise
B. By escalation to finance
C. In advance, with a stated process and an owner
D. By re-running the allocation from scratch

Show answer

Correct: C. Designing it after the first dispute means designing it under pressure, with a specific team’s interests in the room.

Q9

Showback is sufficient when:

A. Spend is below a set threshold
B. Teams can act on the information and are accountable without a budget transfer
C. There is only one single team involved across the entire cloud estate
D. The organisation is pre-revenue

Show answer

Correct: B. The three tests are about whether visibility produces accountability, not about spend size.

Q10

Recovering from chargeback complexity means:

A. Simplifying back toward showback
B. Adding more allocation rules
C. Automating the existing rules
D. Moving to a different tool

Show answer

Correct: A. Which is a legitimate outcome rather than a failure. An org that tried chargeback and reverted has learned something specific about itself.


What’s next

Back to Showback vs chargeback.

Start with the bill.

Foundations takes about five hours. The first lesson is nine minutes.

Open curriculum. No login. No paywall. 290 lessons across 7 courses, three publicly verifiable credentials. Read it on the train, take the exam on a Saturday, list the credential on your résumé Monday.

5h median time to finish Foundations
0 logins, paywalls, or marketing forms
open curriculum, public credential verifier
Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console· Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console·