MLA-C01 Practice Question: ML Solution Monitoring, Maintenance, and Security
A company has deployed a machine learning model on Amazon SageMaker and wants to automatically detect when the distribution of input features deviates significantly from the training data distribution. Which SageMaker feature should they use?
⚠ Common exam trap
Candidates often confuse 'Data Quality Monitoring' with 'Model Quality Monitoring', mistakenly thinking that monitoring prediction accuracy covers input distribution drift, whereas Data Quality Monitoring is explicitly for input features and Model Quality Monitoring is for output predictions.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
SageMaker Model Monitor – Data Quality Monitoring
SageMaker Model Monitor – Data Quality Monitoring is the correct choice because it is specifically designed to detect deviations in the distribution of input features compared to the training data distribution. It continuously monitors incoming inference requests and compares statistical properties (e.g., mean, variance, or histogram) against a baseline computed from the training dataset, alerting when drift is detected.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
SageMaker Clarify
Why it's wrong here
Clarify detects bias in data and models and generates feature attribution explanations; it does not continuously monitor deployed inference inputs for distribution shift. It tempts because it analyses feature behaviour. Ongoing detection of input feature deviation from training data is performed by Data Quality Monitoring in SageMaker Model Monitor.
- ✗
SageMaker Edge Manager
Why it's wrong here
Edge Manager packages and deploys models to edge devices and monitors them there; it does not compare live inference input features against the training distribution. It tempts because it is a SageMaker monitoring-adjacent service. Detecting input feature drift requires Data Quality Monitoring within SageMaker Model Monitor.
- ✗
SageMaker Model Monitor – Model Quality Monitoring
Why it's wrong here
Model Quality Monitoring compares predictions against ground-truth labels to detect accuracy, precision and drift in model outputs, not the distribution of input features. It tempts because it is a Model Monitor capability addressing drift. Input feature distribution deviation is detected by Data Quality Monitoring, which baselines incoming feature statistics.
- ✓
SageMaker Model Monitor – Data Quality Monitoring
Why this is correct
SageMaker Model Monitor's data quality monitoring compares live inference traffic against a baseline computed from the training dataset, raising CloudWatch alerts when feature distributions drift beyond configured thresholds. This directly satisfies the requirement to detect input feature deviation from the training distribution automatically, without custom code.
Go deeper
Related to this question
About these practice questions
One of 665 original MLA-C01 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This MLA-C01 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the MLA-C01 exam.