4.2Standard
Change model, data, prompt, and intended use.
Approve based on impact.
Choose two practices.
× Incorrect
Record change, scope, evaluation, risk, rollback, and approver, and require reassessment, stakeholder review, and staged rollout for high-impact changes.
Detailed explanation
CorrectRequire reassessment, stakeholder review, and staged rollout for high-impact changes
Important changes receive stronger control.
IncorrectApply production changes with no approval record
Auditability is lost.
CorrectRecord change, impact scope, evaluation, risk, rollback, and approver
Decisions remain traceable.
IncorrectPrompt changes need no approval because they are not code
Behavior and safety can change.
Check official documentation
Compare the following points with the official documentation.
AWS公式AIF-C01 Domain 4.2の変更管理、承認、AIガバナンスを確認する。
Official references
What to confirm
AI挙動に影響する変更を分類し、評価と承認を一貫管理できる。
Key points
- Change management
- Approval
- Impact
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
Change management
A controlled process for proposing, reviewing, releasing, and tracking changes.
Impact assessment
An analysis of affected users, data, controls, quality, and operational risk.
Question IDAWS-AIF-404
EnvironmentAWS公式AIF-C01試験ガイドとAWS公式ドキュメントの確認
Last technical review2026-08-20
Report an error or rights issue