5.2Standard
Map AI use to several regulations and contracts.
Turn abstract requirements into technical and operational checks.
Choose two practices.
× Incorrect
Map each requirement to controls and evidence, then record owners, frequency, exceptions, audit results, and remediation deadlines.
Detailed explanation
IncorrectAssume a certification replaces every application review
Certification does not replace specific design and operation checks.
IncorrectNever update the map after a law or service changes
Implementation and requirements drift apart.
CorrectRecord owner, frequency, exception approval, audit result, and remediation deadline
Policy becomes an ongoing operation.
CorrectMap data, access, retention, audit, and notification controls to each requirement
Gaps and duplicate controls become visible.
Check official documentation
Compare the following points with the official documentation.
AWS公式AIF-C01 Domain 5.2のコンプライアンス、責任共有、監査を確認する。
Official references
What to confirm
抽象的なAI要件を管理策・証跡・担当へ対応付けられる。
Key points
- Controls
- Evidence
- Owner
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
Control mapping
Linking a legal or contractual requirement to the controls and evidence that satisfy it.
Control owner
The person or team accountable for operating and maintaining a control.
Question IDAWS-AIF-225
EnvironmentAWS公式AIF-C01試験ガイドとAWS公式ドキュメントの確認
Last technical review2026-08-20
Report an error or rights issue