5.2Standard
A provider reports possible data exposure in an external model.
Decide quickly whether your users are affected.
Choose two first responses.
× Incorrect
Match provider scope, period, version, data, and configuration to your records and coordinate containment, notice, deletion, and prevention.
Detailed explanation
IncorrectDelete logs before the cause is known to save storage
Evidence and audit information are lost.
CorrectIf needed, stop the feature and coordinate user notice, legal, security, deletion, and prevention
Impact and omissions are contained.
CorrectCheck provider scope, period, version, recommended actions, and evidence against your usage
Affected use is identified.
IncorrectAssume no impact from the provider statement alone
Your settings and data use may differ.
Check official documentation
Compare the following points with the official documentation.
AWS公式AIF-C01 Domain 5の第三者リスク、インシデント、通知を確認する。
Official references
What to confirm
外部ベンダーの通知を自社の利用実態へ照合して初動を決められる。
Key points
- Third-party risk
- Impact matching
- Coordination
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
Third-party risk
Risk introduced by an external provider, component, or service dependency.
Impact correlation
Comparing an external event with local assets, versions, and observed effects.
Question IDAWS-AIF-540
EnvironmentAWS公式AIF-C01試験ガイドとAWS公式ドキュメントの確認
Last technical review2026-08-20
Report an error or rights issue