5.1Standard
Public and internal data are combined for training.
Make permission and change history traceable.
Which management practice is most appropriate?
× Incorrect
Record provider, acquisition date, license, consent scope, transformations, and version so the path into a model can be traced.
Detailed explanation
IncorrectCheck permissions only after training the model
Improper use may already be difficult to undo.
IncorrectDo not record the source of public data
Public data still has use conditions.
IncorrectRecord only the data file name
Evidence of source and permission is missing.
CorrectRecord provider, acquisition date, license, consent scope, transformations, and version
Use and changes are traceable.
Check official documentation
Compare the following points with the official documentation.
AWS公式AIF-C01 Domain 5のデータ出所、ライセンス、ガバナンスを確認する。
Official references
What to confirm
データの出所と利用根拠を、モデル版と結び付けて説明できる。
Key points
- Data provenance
- Permission
- Versioning
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
Data provenance
Information describing a dataset's origin, custody, transformation, and use.
Consent scope
The purpose, data, recipients, and period covered by consent.
Question IDAWS-AIF-531
EnvironmentAWS公式AIF-C01試験ガイドとAWS公式ドキュメントの確認
Last technical review2026-08-20
Report an error or rights issue