MLA-C01 Practice Question: A team wants to automatically retrain a model…

A team wants to automatically retrain a model when new labeled data arrives. Which SageMaker feature can orchestrate this workflow?

⚠ Common exam trap

Candidates often confuse monitoring services (Model Monitor, Debugger) with orchestration services, or assume Autopilot's automation includes workflow orchestration, when in fact only Pipelines provides the explicit DAG-based orchestration needed to chain retraining steps on new data events.

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 Pipelines

SageMaker Pipelines is a purpose-built CI/CD service for machine learning that allows you to define, orchestrate, and automate end-to-end ML workflows, including retraining models when new labeled data arrives. You can create a pipeline that triggers on new data events (e.g., via an S3 event notification or a Lambda function) and automatically executes steps such as data processing, training, evaluation, and model registration. This makes it the correct choice for orchestrating an automated retraining workflow.

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 Pipelines
Why this is correct
SageMaker Pipelines orchestrates the retraining workflow by chaining processing, training and evaluation steps into a directed acyclic graph, triggered automatically when new labelled data lands in Amazon S3 via EventBridge. This satisfies the stem's requirement for automatic, event-driven retraining rather than manual intervention.
✗
SageMaker Model Monitor
Why it's wrong here
Model Monitor compares production inference data against a baseline to detect drift and data quality issues, emitting alerts rather than retraining. It is tempting because drift detection often precedes retraining, but it does not orchestrate the workflow; SageMaker Pipelines handles that with an EventBridge trigger.
✗
SageMaker Debugger
Why it's wrong here
Debugger captures training tensors and profiles resource usage to diagnose convergence and bottleneck issues during a job; it neither detects new labelled data nor launches retraining. It is tempting because it operates across training runs, but orchestration of retraining belongs to SageMaker Pipelines, not a debugging hook.
✗
SageMaker Autopilot
Why it's wrong here
Autopilot automates algorithm selection, feature engineering and hyperparameter tuning for a single training job; it does not watch data arrivals or trigger pipelines. It is tempting because it automates model building, but event-driven retraining orchestration requires SageMaker Pipelines with a trigger such as EventBridge.

Quick reference

AWS S3 Storage Class Comparison

Storage Class	Min Duration	Retrieval	Use Case
S3 Standard	None	Immediate	Frequently accessed data
S3 Standard-IA	30 days	Immediate	Infrequent access, rapid retrieval
S3 One Zone-IA	30 days	Immediate	Non-critical infrequent data
S3 Intelligent-Tiering	None	Immediate–hours	Unknown or changing access patterns
S3 Glacier Instant	90 days	Milliseconds	Archive with instant retrieval
S3 Glacier Flexible	90 days	Minutes–hours	Archive, flexible retrieval
S3 Glacier Deep Archive	180 days	Hours	Long-term compliance archive

Go deeper

MLA-C01 Practice Question: A team wants to automatically retrain a model…

Why each option matters

Option-by-option breakdown

AWS S3 Storage Class Comparison

Related to this question