1.3Standard
An asynchronous job times out and is retried.
Prevent duplicate side effects.
Choose two designs.
× Incorrect
Use job IDs or input hashes to deduplicate, check state before side effects, and use capped exponential backoff and a dead-letter path.
Detailed explanation
IncorrectRun unlimited parallel retries after every timeout
Load and side effects grow.
CorrectUse a job ID, input hash, and result location to detect duplicates
Retries converge to one result.
CorrectCheck state before side effects and use capped backoff and dead letters
Infinite work and duplicates are limited.
IncorrectNever store job state and ask the model if it succeeded
State is unknown.
Check official documentation
Compare the following points with the official documentation.
AWS公式AIF-C01 Domain 1.3・3.3の非同期処理、再試行、冪等性を確認する。
Official references
What to confirm
タイムアウト時も二重の推論・登録を発生させず、安全に再試行できる。
Key points
- Idempotency
- Backoff
- Dead letter
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
Idempotency
A property whereby repeating an operation does not create an additional effect.
Job ID
A unique identifier used to track one logical processing request.
Question IDAWS-AIF-477
EnvironmentAWS公式AIF-C01試験ガイドとAWS公式ドキュメントの確認
Last technical review2026-08-20
Report an error or rights issue