Which feature detects drift in deployed models?
Why C is the answer
SageMaker Model Monitor
Model Monitor compares live data with a baseline.
In detail
- Model Monitor detects drift in deployed models.
- AWS closed SageMaker Model Monitor to new customers. Existing customers can keep using it.
- Create the baseline from training data.
Use case
An illustrative scenario, not a real incident.
A team enables Model Monitor on an endpoint, and it reports drift against a baseline.
See it in different ways
sequenceDiagram participant E as Endpoint participant S as Captured data in S3 participant M as Model Monitor participant C as CloudWatch E->>S: Capture requests and responses M->>S: Compare with the baseline M->>C: Publish violations C-->>E: Alarm starts retraining
sequenceDiagram participant E as Endpoint participant S as S3 participant M as Model Monitor participant C as CloudWatch E->>S: Data capture M->>S: Compares with the baseline M->>C: Publishes metrics C-->>M: Alarm on drift
flowchart LR S0["Baseline"] --> S1["Captured data"] --> S2["Compare"] --> S3["Report"]
Key point: Model Monitor detects drift.
Why the other options are wrong
- A. SageMaker Debugger
- Debugger inspects training.
- B. SageMaker Clarify alone at training time
- That runs before deployment.
- D. SageMaker Data Wrangler
- Data Wrangler prepares data.