1.3Standard
Several teams register candidate models.
Only evaluated models may enter production.
Choose two operational practices.
× Incorrect
Attach data, code, evaluation, risk, approver, and purpose to each version, then use approval gates, staged rollout, rollback, and retirement controls.
Detailed explanation
IncorrectDiscard evaluation and approval history
Production use can no longer be explained.
CorrectAttach data, code, evaluations, risks, approver, and purpose to each model version
The model's origin and state are traceable.
IncorrectDeploy every registered model automatically
Unreviewed or out-of-scope models can be released.
CorrectDefine approval gates, staged deployment, rollback, and retirement for expired models
Production lifecycle decisions are controlled.
Check official documentation
Compare the following points with the official documentation.
AWS公式AIF-C01 Domain 1.3のモデルレジストリ、承認、デプロイを確認する。
Official references
What to confirm
モデルをファイルではなく承認状態を持つ運用資産として管理できる。
Key points
- Model version
- Approval gate
- 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
Model registry
A catalog that tracks model versions, evaluations, approvals, and deployment status.
Approval gate
A required review that must pass before a candidate moves to the next stage.
Question IDAWS-AIF-295
EnvironmentAWS公式AIF-C01試験ガイドとAWS公式ドキュメントの確認
Last technical review2026-08-20
Report an error or rights issue