Public and internal data are combined for training.
Make permission and change history traceable.
Which management practice is most appropriate?
Record provider, acquisition date, license, consent scope, transformations, and version so the path into a model can be traced.
Detailed explanation
Use and changes are traceable.
Use and changes are traceable.
Evidence of source and permission is missing.
Evidence of source and permission is missing.
Public data still has use conditions.
Public data still has use conditions.
Improper use may already be difficult to undo.
Improper use may already be difficult to undo.
Try it yourself
An example you can run in a temporary verification environment.
AWS公式AIF-C01 Domain 5.3のデータ出所、ライセンス、ガバナンスを確認する。Expected result
データの出所と利用根拠を、モデル版と結び付けて説明できる。Key points
- Data provenance
- Permission
- Versioning
Notes
- Environment: AWS公式AIF-C01試験ガイドとAWS公式ドキュメントの確認
- Command output formatting can vary slightly by distribution or tool version.
- Run the example in a temporary directory or process when possible.
Foundation review
Read the scope first
Check whether the command acts on the current shell, a new process, an existing process, or a file.
Verify the observable result
Use the supplied command and compare the output with the expected result.