quiz · 4 min Cost, Latency & Reliability Check According to the lessons, where does budget enforcement live?The model stops itself when its internal token counter reaches the limitThe provider API enforces the budget and returns a quota errorThe budget is counted across all calls including cache hitsThe agent wrapper enforces the budget in code, stopping the run when exhaustedIn the Budgeted wrapper from the interactive lesson, what is the cache key?The exact input promptThe call counter value at the time of the requestA hash of the model's previous outputThe step number in the outer agent loopIn the Budgeted wrapper, which check happens first on every call?The budget check -- reject if calls >= budget before touching the cacheThe cache check -- return cached result if the prompt was seen beforeThe model call -- then cache the result and increment the counterA jitter delay -- then the cache check, then the budget checkWhy does Lesson 40 say retrying a write is unsafe without idempotency?Reads are also non-idempotent and must use unique IDs to be safeRetries are safe by default because the retry cap bounds total callsA timeout that triggers a retry can execute the action twice without idempotencyIdempotency is only required when switching to a fallback model, not for retriesWhat is the purpose of adding jitter to exponential backoff?Jitter increases the effective retry cap so the agent can attempt more callsJitter prevents concurrent agents from retrying in lockstepJitter satisfies the idempotency requirement for retried writesJitter resets the circuit breaker after a burst of failuresSubmit Mark complete ← Timeouts, Retries & Fallback Tracing the Loop →