5.2Standard
Investigate an AI response leak across input, retrieval, and policy changes.
Correlate multiple service logs.
Choose two audit practices.
× Incorrect
Use common request ID, principal, time, model, document, and policy versions, with synchronized time, retention, access separation, and tamper detection.
Detailed explanation
IncorrectUse different formats and infer order later
Correlation becomes uncertain.
CorrectManage time synchronization, retention, access, and tamper detection
Evidence is reliable and searchable.
CorrectRecord a common request ID, principal, time, model, document, and policy versions
Processing and changes can be correlated.
IncorrectCopy every full input into audit logs forever
Sensitive exposure expands.
Check official documentation
Compare the following points with the official documentation.
AWS CloudTrail・CloudWatch Logs公式とAIF-C01 Domain 5.2の監査相関を確認する。
Official references
What to confirm
複数サービスのAIイベントを相関し、証跡と機密性を両立できる。
Key points
- Correlation ID
- Time sync
- Tamper detection
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
Audit correlation
Linking events from multiple services by identifiers, timestamps, and shared context.
Time synchronization
Aligning system clocks so event order and duration can be trusted.
Question IDAWS-AIF-289
EnvironmentAWS公式AIF-C01試験ガイドとAWS公式ドキュメントの確認
Last technical review2026-08-20
Report an error or rights issue