Replace the foundation model used by an application.
Limit customer impact and be able to return to the previous model.
Choose two release practices.
Use canary traffic, version the model and configuration, and maintain a rollback path before full rollout.
Detailed explanation
Problems may appear with other times or input distributions.
Quality, safety, and latency can be observed before broad rollout.
Impact and root cause cannot be isolated.
The change is reproducible and recoverable.
Check official documentation
Compare the following points with the official documentation.
AWS公式AIF-C01 Domain 3.1・3.3のモデル評価、変更管理、監視を確認する。
Official references
What to confirm
モデル変更の影響を限定し、比較とロールバックを行う方法を説明できる。
Key points
- Canary
- Versioning
- Rollback
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 deployment
Sending a limited share of traffic to a new version before expanding its exposure.
Rollback
Returning traffic or configuration to a previously stable version after a problem.