A dashboard shows settled charges while concurrent requests create new liabilities. Define what the cap promises, reconcile the exposure and decide how the product behaves when money is reserved.
Updated Nov 2026 · Original practice questions with worked answers and teaching rubrics. Our editorial policy explains the sources, review process and limits.
Fictional model-API account. All amounts are USD before tax within one billing period. Settled, completed-but-unsettled and in-flight usage are disjoint. Each stated maximum is enforceable for this exercise; no real provider policy is implied.
| Customer cap | 1000 |
|---|---|
| Settled charges | 930 |
| Completed usage awaiting settlement | 30 |
| In-flight requests | 8 |
| Maximum reserved charge per in-flight request | 5 |
| New requests arriving together | 20 |
| Maximum charge per new request | 5 |
| Follow-up | Three original in-flight requests finish at 3 USD each. Reconcile the account and decide what can start next. |
Your task. Reconstruct exposure, explain a possible overshoot and specify admission, settlement, timeout and customer-facing behavior for a hard cap.
A dashboard shows settled charges while concurrent requests create new liabilities. Define what the cap promises, reconcile the exposure and decide how the product behaves when money is reserved.
This reference answer is in Premium. Free signup opens other answers.
9 answers per topic instead of 5, and your progress kept · no cardor unlock all 420 remaining answersNo comments yet. How would you have answered?