5.1Standard
A prompt needs a customer ID for analysis.
Do not send the real identifier to the model.
Choose two controls.
× Incorrect
Replace identifiers with random tokens and isolate the mapping table, while continuing to control reidentification, logs, retention, and access.
Detailed explanation
IncorrectEmbed the mapping table in every prompt
Separation is lost.
IncorrectTokenization makes all regulatory and access controls unnecessary
A mapping table or combination can reidentify.
CorrectAudit reidentification, logs, output, retention, and access after tokenization
The token is not treated as risk-free.
CorrectReplace the real ID with a random token and store the mapping under a separate access boundary
The model need not receive the direct identifier.
Check official documentation
Compare the following points with the official documentation.
AWS公式AIF-C01 Domain 5.1のデータ保護、トークン化、最小権限を確認する。
Official references
What to confirm
トークン化がアクセス分離であり、完全な匿名化を自動保証しないと説明できる。
Key points
- Tokenization
- Mapping
- Reidentification
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
Tokenization
Replacing a sensitive value with a substitute token while keeping the mapping separately.
Mapping table
A protected table that links replacement tokens back to original values.
Question IDAWS-AIF-291
EnvironmentAWS公式AIF-C01試験ガイドとAWS公式ドキュメントの確認
Last technical review2026-08-20
Report an error or rights issue