3.3Standard
Ground truth arrives weeks after predictions.
Detect issues before labels arrive.
Choose two practices.
× Incorrect
Separate confirmed metrics after labels arrive from leading signals, and monitor label delay, missingness, and confirmation rules.
Detailed explanation
IncorrectAssume performance is normal while labels are missing
It is simply unmeasured.
CorrectMonitor label delay, missingness, and confirmation rules and separate provisional metrics
Uncertainty is explicit.
IncorrectFeed provisional predictions back as confirmed labels immediately
Errors can amplify.
CorrectRecompute accuracy and errors when labels arrive and correlate them with drift signals
Later performance is confirmed.
Check official documentation
Compare the following points with the official documentation.
AWS公式AIF-C01 Domain 3.3のモデル監視、ラベル遅延、ドリフトを確認する。
Official references
What to confirm
ラベルが遅れる環境で、暫定監視と確定評価を区別できる。
Key points
- Delayed label
- Leading signal
- Confirmed metric
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
Delayed label
A target value that becomes available only after the prediction is made.
Leading indicator
An earlier signal that may reveal change before outcome labels arrive.
Question IDAWS-AIF-425
EnvironmentAWS公式AIF-C01試験ガイドとAWS公式ドキュメントの確認
Last technical review2026-08-20
Report an error or rights issue