5.2Basic
Model, data, business, and security owners differ.
Prevent responsibility gaps.
Choose two practices.
× Incorrect
Document owners, approvers, operators, data managers, risk contacts, and escalation for high-impact decisions.
Detailed explanation
CorrectDefine approval, stop, restart, and escalation for high-impact use
Important decisions are controlled.
CorrectDocument owner, approver, operator, data manager, and risk or legal contact
Decision paths are clear.
IncorrectMany roles mean nobody needs final accountability
Responsibility becomes unclear.
IncorrectThe provider alone owns all impact management
Users have duties too.
Check official documentation
Compare the following points with the official documentation.
AWS公式AIF-C01 Domain 4のガバナンス、責任分界、変更管理を確認する。
Official references
What to confirm
役割を分担しながら最終責任と高影響判断の経路を明確にできる。
Key points
- Accountability
- Approval
- Escalation
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
Responsibility matrix
A mapping of activities to accountable, responsible, consulted, and informed roles.
Accountable owner
The role answerable for a system, decision, or control outcome.
Question IDAWS-AIF-486
EnvironmentAWS公式AIF-C01試験ガイドとAWS公式ドキュメントの確認
Last technical review2026-08-20
Report an error or rights issue