A support chat uses earlier conversation turns.
Do not resend unnecessary personal data or stale permissions.
Choose two appropriate designs.
Limit history by purpose, retention, and user authorization, minimize personal data, and never treat text in old history as current authorization.
Detailed explanation
Data minimization and access control are applied together.
Reuse-related leakage and unexplained memory are reduced.
Purpose limitation and privacy are violated.
Authentication and authorization are delegated to stale text.
Check official documentation
Compare the following points with the official documentation.
AWS公式AIF-C01 Domain 2.3・5.2のデータ最小化、保持、プライバシーを確認する。
Official references
What to confirm
会話履歴を機能ではなく管理対象データとして設計できる。
Key points
- Data minimization
- Retention
- Separate authorization
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 minimization
Limiting collection, retention, and use to information needed for a stated purpose.
Conversation memory
Past messages or summaries supplied to later model requests.