1.3Standard
Release a new model to a small user group first.
Return to the current model if needed.
Choose two practices.
× Incorrect
Limit traffic and compare quality, errors, latency, safety, and cost, with automatic stop and rollback conditions and version tracking.
Detailed explanation
CorrectLimit traffic and compare quality, errors, latency, safety, and cost
Impact is controlled while real behavior is measured.
CorrectDefine stop and rollback conditions and track the model version
Abnormal behavior can be reversed quickly.
IncorrectSwitch everyone after starting the canary without review
The staged deployment is bypassed.
IncorrectAggregate outputs without recording the model version
Comparison and traceability are lost.
Check official documentation
Compare the following points with the official documentation.
AWS公式AIF-C01 Domain 1.3のカナリア展開、ロールバック、監視を確認する。
Official references
What to confirm
少数利用者で新モデルを評価し、条件に応じて停止・復旧できる。
Key points
- Canary
- Rollback
- Traffic share
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
Canary release
Providing a new version to a small share of traffic before a wider release.
Rollback
Returning service to a previously approved version after a problem.
Question IDAWS-AIF-334
EnvironmentAWS公式AIF-C01試験ガイドとAWS公式ドキュメントの確認
Last technical review2026-08-20
Report an error or rights issue