Cost Control and Budgets
Feeds categories D2 and D3 (cost tracking, budget enforcement).
Starting state from the fast track: a personal key with traffic history, a hello-world budget in warn mode, and teams with budgets drawing down. Scenarios 6.3 and 6.4 build directly on that state rather than starting from scratch.
Grade each scenario Pass (2 points), Pass with gaps (1), or Fail (0) against the grading rubric, and carry the subtotal into the summary scorecard.
Scoresheet document
For your convenience, this page can be downloaded as PDF or printed directly. Site navigation is omitted, the scoring table keeps its rows intact with the header repeated on every page, and the Grade and Notes columns leave room for handwriting.
| ID | Scenario | Guide | Grade | Notes |
|---|---|---|---|---|
| 6.1 | Pick the right cost control for two contrasting workloads (a production app and an evaluation key) using the decision guide. Verify: the chosen controls match the guide's situation table. | Choose the right cost control | ||
| 6.2 | Run a usage review: by-key breakdown, sorted by cost, over a chosen period. Verify: the top consumers match expectations, and one row can be drilled into its keys and models. | Catch spend drift before the invoice does | ||
| 6.3 | Create a team budget with a deliberate scope (pooled or per-member) and enforcement mode (warn or block). Verify: the budget appears with the intended scope, and two identities draw down as the scope dictates. (Carried over from fast-track W1.3; grade from that evidence.) | Keep each team's spend inside an agreed ceiling | ||
| 6.4 | Exhaust a small test budget and read the burn along the way. Verify: the meter shows used, remaining, and days left; a hard-enforced budget blocks at the cap. (Head start from fast-track D1.6: convert the warn-mode budget to a hard cap and exhaust it.) | See budget exhaustion coming | ||
| 6.5 | Raise the exhausted budget's ceiling in place. Verify: blocked requests resume immediately, and the change appears in the audit trail. | Raise a spend ceiling without interrupting delivery | ||
| 6.6 | Export a spend statement grouped by team for a closed period. Verify: the download carries USD amounts joinable to cost-centre records. | Bill AI spend back to the teams that incur it | ||
| 6.7 | Attribute cost with caller-set tags. Verify: spend reports group by the supplied tags, and an untagged or mislabeled request is refused where policy requires the tag. | Know what every app and project actually costs | ||
| 6.8 | Set a rate limit and exceed it deliberately. Verify: requests over the limit are rejected with a 429, and the firing limit is identifiable in the traffic view. | Stop runaway workloads | ||
| 6.9 | (optional) Simulate a leaked key: revoke it mid-traffic. Verify: the next request on the credential is rejected, and the revocation is recorded in the audit trail. | Contain a leaked key | ||
| Subtotal | /18 |