5.2Standard
Models, data, prompts, and use cases change.
Match approval to risk.
Choose two practices.
× Incorrect
Classify impact across users, data, safety, fairness, and legal factors, then document tests, approvals, and rollback for each class.
Detailed explanation
IncorrectPrompts are text, so all prompt changes are automatically approved
Behavior and risk change.
CorrectAssess user, data, safety, fairness, and legal impact to choose an approval level
High-impact changes receive control.
IncorrectCreate an approval record only after success
There is no preventive control.
CorrectDocument criteria, tests, approvers, and rollback for minor and high-impact changes
Decisions are consistent.
Check official documentation
Compare the following points with the official documentation.
AWS公式AIF-C01 Domain 4の変更管理、リスク分類、承認を確認する。
Official references
What to confirm
変更の種類と影響に応じた承認・検証・復旧を設計できる。
Key points
- Change management
- Risk classification
- Approval
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
Risk classification
Grouping changes by potential effect, likelihood, and required control strength.
Approval level
The role or review depth required before a change is released.
Question IDAWS-AIF-490
EnvironmentAWS公式AIF-C01試験ガイドとAWS公式ドキュメントの確認
Last technical review2026-08-20
Report an error or rights issue