5.1Standard
A new AI feature is in requirements planning.
Build protection in early.
Choose two practices.
× Incorrect
Specify purpose, minimization, private defaults, retention, access, deletion, and rights and include threat, reidentification, transfer, and reuse tests in design review.
Detailed explanation
CorrectInclude threat, reidentification, cross-border, and reuse tests in design review
Risks are early.
IncorrectAsk privacy reviewers only after implementation
Late fixes are costly.
CorrectSpecify purpose, minimization, private default, retention, access, deletion, and rights as requirements
Protection is built in.
IncorrectDecide collection and retention later for convenience
Overcollection becomes normal.
Check official documentation
Compare the following points with the official documentation.
AWS公式AIF-C01 Domain 5.1のプライバシー、最小化、設計レビューを確認する。
Official references
What to confirm
プライバシーを実装後の修正ではなく、要件・設計・試験へ組み込める。
Key points
- Privacy by design
- Minimization
- Private default
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
Privacy by design
Building privacy controls into architecture and process from the beginning.
Default private
A default state that limits access and disclosure unless explicitly authorized.
Question IDAWS-AIF-529
EnvironmentAWS公式AIF-C01試験ガイドとAWS公式ドキュメントの確認
Last technical review2026-08-20
Report an error or rights issue