5.1Basic
An inference service uses an external model API secret.
Limit impact if it leaks.
Choose two practices.
× Incorrect
Store secrets in a managed service, grant only the required role, rotate and revoke old values, and monitor retrieval failures.
Detailed explanation
IncorrectHard-code the secret in source for easy deployment
Leak response becomes difficult.
IncorrectKeep old values active forever after rotation
Compromise impact remains.
CorrectRotate regularly, disable old values, limit readers, and monitor failures
The secret lifecycle is controlled.
CorrectStore the secret in a managed service and retrieve it only when needed
Secrets stay out of source and logs.
Check official documentation
Compare the following points with the official documentation.
AWS公式AIF-C01 Domain 5.1のSecrets Manager、IAM、秘密ローテーションを確認する。
Official references
What to confirm
推論サービスの秘密を安全に保管・取得・更新・失効できる。
Key points
- Secret management
- Rotation
- Revocation
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
Secret rotation
Replacing a credential on a schedule or after exposure while updating its consumers.
Minimal secret access
Granting only the application and operations that need to read a particular secret.
Question IDAWS-AIF-349
EnvironmentAWS公式AIF-C01試験ガイドとAWS公式ドキュメントの確認
Last technical review2026-08-20
Report an error or rights issue