5.1Standard
Encrypt training data, logs, and backups.
Separate administrators by purpose.
Choose two designs.
× Incorrect
Separate KMS keys by purpose, environment, or account, and audit usage, rotation, deletion waiting periods, and cross-account grants.
Detailed explanation
IncorrectShare one administrator key across every environment
Mistakes and compromise spread.
CorrectSeparate keys and key policies by purpose, environment, or account
One key compromise has a smaller scope.
CorrectAudit key use, rotation, deletion waiting periods, and cross-account grants
The key lifecycle is controlled.
IncorrectDeleting a key removes all retention obligations
Deletion and retention requirements differ.
Check official documentation
Compare the following points with the official documentation.
AWS KMS公式とAIF-C01 Domain 5.1の暗号化、キーポリシー、鍵管理を確認する。
Official references
What to confirm
AIデータの暗号鍵を用途別に管理し、鍵操作を監査できる。
Key points
- KMS
- Key separation
- Rotation
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
KMS key policy
A resource policy defining who may use or administer a KMS key.
Key separation
Using different keys for distinct environments, purposes, or trust boundaries.
Question IDAWS-AIF-365
EnvironmentAWS公式AIF-C01試験ガイドとAWS公式ドキュメントの確認
Last technical review2026-08-20
Report an error or rights issue