Quick Answer
The correct answer is SageMaker Debugger and built-in early stopping in XGBoost. SageMaker Debugger works by monitoring training metrics in real time, using built-in rules like LossNotDecreasing or VanishingGradient to detect when the model stops improving, then automatically triggering the StopTraining API to halt the job. XGBoost’s native early stopping, controlled by the `early_stopping_rounds` parameter, stops training when the validation metric fails to improve for a set number of rounds, making it a lightweight, algorithm-level solution. On the MLS-C01 exam, this question tests your ability to distinguish between SageMaker-native monitoring tools and algorithm-specific parameters—a common trap is confusing SageMaker’s automatic model tuning (hyperparameter optimization) with early stopping, which is a separate mechanism. Remember the mnemonic “Debugger detects, XGBoost stops”: Debugger watches all metrics, while XGBoost’s parameter handles its own rounds.
This MLS-C01 practice question tests your understanding of modeling. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A data scientist is training a model using SageMaker and wants to automatically stop training when the model stops improving. Which TWO options can be used?
AWS Step Functions
Why wrong: Orchestration, not automatic stopping.
Built-in early stopping in XGBoost
Native early stopping support.
SageMaker Debugger
Can monitor and stop training.
CloudWatch Alarms
Why wrong: For infrastructure monitoring.
SageMaker Model Monitor
Why wrong: For production data quality.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Built-in early stopping in XGBoost
Built-in early stopping in XGBoost (Option B) is correct because XGBoost natively supports an `early_stopping_rounds` parameter that halts training when the validation metric stops improving for a specified number of rounds. SageMaker Debugger (Option C) is correct because it can monitor training metrics in real time and trigger a stop action via a built-in or custom rule (e.g., `VanishingGradient` or `LossNotDecreasing`) when the model stops improving, integrating with SageMaker's `StopTraining` API.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
AWS Step Functions
Why it's wrong here
Orchestration, not automatic stopping.
Built-in early stopping in XGBoost
Why this is correct
Native early stopping support.
Related concept
Read the scenario before looking for a memorised answer.
SageMaker Debugger
Why this is correct
Can monitor and stop training.
Related concept
Read the scenario before looking for a memorised answer.
CloudWatch Alarms
Why it's wrong here
For infrastructure monitoring.
SageMaker Model Monitor
Why it's wrong here
For production data quality.
Common exam traps
The trap here is that candidates may confuse SageMaker Model Monitor (post-deployment monitoring) with SageMaker Debugger (training-time monitoring), or assume CloudWatch Alarms can directly implement early stopping logic when they are only for threshold-based alerts on emitted metrics.
Detailed technical explanation
Under the hood, XGBoost's early stopping evaluates the evaluation metric on a validation set after each boosting round and stops if no improvement is seen for `early_stopping_rounds` consecutive rounds, using a tolerance (e.g., `maximize_evaluation_metrics`). SageMaker Debugger hooks into the training process via the SageMaker SDK, capturing tensors and scalars at each step, and its built-in rules (e.g., `LossNotDecreasing`) compare the current loss to a moving baseline; if the loss fails to decrease over a configurable number of steps, it issues a `STOP` signal through the `TrainingJob` API. A real-world scenario: training a deep learning model on a large dataset where overfitting causes validation loss to plateau — Debugger can stop the job early, saving compute costs, while XGBoost's early stopping prevents unnecessary rounds in gradient boosting.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Modeling — study guide chapter
Learn the concepts, then practise the questions
Modeling practice questions
Targeted practice on this topic area only
All MLS-C01 questions
1,755 questions across all exam domains
AWS Certified Machine Learning Specialty MLS-C01 study guide
Full concept coverage aligned to exam objectives
MLS-C01 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise MLS-C01 questions linked to Data Engineering.
Practise MLS-C01 questions linked to Machine Learning Implementation and Operations.
Practise MLS-C01 questions linked to Modeling.
Practise MLS-C01 questions linked to Exploratory Data Analysis.
Practise MLS-C01 questions linked to MLS-C01 fundamentals.
Practise MLS-C01 questions linked to MLS-C01 scenario.
Practise MLS-C01 questions linked to MLS-C01 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Modeling — This question tests Modeling — Read the scenario before looking for a memorised answer..
The correct answer is: Built-in early stopping in XGBoost — Built-in early stopping in XGBoost (Option B) is correct because XGBoost natively supports an `early_stopping_rounds` parameter that halts training when the validation metric stops improving for a specified number of rounds. SageMaker Debugger (Option C) is correct because it can monitor training metrics in real time and trigger a stop action via a built-in or custom rule (e.g., `VanishingGradient` or `LossNotDecreasing`) when the model stops improving, integrating with SageMaker's `StopTraining` API.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 24, 2026
This MLS-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 MLS-C01 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.