3.4Standard
A generative API is throttled after a traffic spike.
Limit user impact and avoid a retry storm.
Choose two appropriate practices.
× Incorrect
Use exponential backoff with jitter and define capped retries and a wait, alternate model, or human fallback.
Detailed explanation
CorrectOffer a wait, smaller model, or simple response when limits are reached
A bounded fallback is safer than infinite retries.
CorrectUse exponential backoff and jitter
Retries are spread out rather than synchronized.
IncorrectRetry every client immediately
The load and throttling worsen.
IncorrectRecord failures as successes
Availability and quality would be misreported.
Check official documentation
Compare the following points with the official documentation.
AWS公式AIF-C01 Domain 3.4とAmazon Bedrockのスロットリング・再試行設計を確認する。
Official references
What to confirm
再試行集中を避け、安全に利用者へ代替手段を示せる。
Key points
- Backoff
- Jitter
- Fallback
Notes
- Environment: AWS公式AIF-C01試験ガイドとAWS公式ドキュメントの確認
- Compare the definition with the AIF-C01 objective and the service documentation before applying it.
- Keep the concept separate from a particular answer choice or implementation step.
Foundation review
Exponential backoff
Increasing the wait between retries to reduce pressure during a failure or throttle.
Jitter
A random delay component that prevents many clients from retrying at the same instant.
Question IDAWS-AIF-124
EnvironmentAWS公式AIF-C01試験ガイドとAWS公式ドキュメントの確認
Last technical review2026-08-20
Report an error or rights issue