3.3Standard
Responses are cached to reduce inference cost.
Prevent cross-tenant leakage.
Choose two designs.
× Incorrect
Include tenant, authorization, model, prompt, and data versions in cache keys and manage TTL, invalidation, privacy, encryption, hit rate, and staleness.
Detailed explanation
CorrectInclude tenant, permission, model, prompt, and data versions in the cache key
Results are less likely to mix.
Results are less likely to mix.
CorrectUse TTL, invalidation, privacy controls, encryption, and stale-result monitoring
Cost and leakage are controlled.
Cost and leakage are controlled.
IncorrectThe same text question has one answer for every user
Context and permissions differ.
Context and permissions differ.
IncorrectNever expire or delete a cached result
Old or personal data remains.
Old or personal data remains.
Try it yourself
An example you can run in a temporary verification environment.
AWS公式AIF-C01 Domain 3.3・5.1のキャッシュ、データ分離、保持を確認する。Expected result
コスト削減のキャッシュが権限混同や古い回答を生まないよう設計できる。Key points
- Cache key
- TTL
- Invalidation
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.
Question IDAWS-AIF-462
EnvironmentAWS公式AIF-C01試験ガイドとAWS公式ドキュメントの確認
Last technical review2026-08-20
Report an error or rights issue