1.3Standard
Continuously update model code and data definitions.
Deploy only changes that meet quality conditions.
Choose two pipeline practices.
× Incorrect
Track code, data, model versions, and evaluation results, then require quality, safety, bias, and approval gates before staged deployment.
Detailed explanation
IncorrectDeploy directly whenever data changes
No quality gate exists.
IncorrectDelete failed evaluation results
Auditability is lost.
CorrectRequire fixed tests, bias and safety checks, and approval before staged rollout
Regressions and risk are gated.
CorrectRecord code, data, model versions, and evaluation results as artifacts
Changes are reproducible and traceable.
Check official documentation
Compare the following points with the official documentation.
AWS公式AIF-C01 Domain 1.3のMLOps、自動化、承認を確認する。
Official references
What to confirm
モデル変更へ再現性と品質ゲートを組み込める。
Key points
- CI/CD
- Quality gate
- Staged rollout
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
Model CI/CD
A pipeline that repeatedly validates and delivers models with their related assets.
Quality gate
A required quality or safety check that a change must pass before proceeding.
Question IDAWS-AIF-318
EnvironmentAWS公式AIF-C01試験ガイドとAWS公式ドキュメントの確認
Last technical review2026-08-20
Report an error or rights issue