MLA-C01 ML Model Development Practice Question

A team is training a PyTorch model using SageMaker with a custom training script. They want to track hyperparameters and metrics across multiple experiments. Which service should they use?

⚠ Common exam trap

MLA-C01 often tests the distinction between the four SageMaker 'specialty' services (Clarify, Experiments, Model Monitor, Debugger) — candidates confuse Debugger's training-time telemetry with Experiments' run-tracking purpose.

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 Experiments

SageMaker Experiments is purpose-built for tracking ML experiment runs, automatically capturing hyperparameters, metrics, artifacts, and lineage across training jobs. It integrates natively with SageMaker training jobs and custom PyTorch scripts via the SageMaker SDK, letting teams compare runs in the Studio UI. This directly matches the requirement to track hyperparameters and metrics across multiple experiments.

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
SageMaker Clarify detects bias and explains feature attributions; it has no experiment-tracking capability for logging hyperparameters and metrics across runs. It is tempting because it integrates with training pipelines, but it is the correct choice when the requirement is bias detection or SHAP-based explainability, not experiment comparison.
✓
SageMaker Experiments
Why this is correct
SageMaker Experiments captures hyperparameters, metrics, and artefacts across training runs, letting the team compare and track multiple experiments from their custom PyTorch script. It satisfies the requirement to log and organise runs, which raw training jobs alone do not provide.
✗
SageMaker Model Monitor
Why it's wrong here
SageMaker Model Monitor detects data and prediction drift on deployed endpoints; it does not record hyperparameters or training metrics across experiments. It is tempting because it is a SageMaker monitoring service, and it would be correct for alerting on drift in a live endpoint.
✗
SageMaker Debugger
Why it's wrong here
SageMaker Debugger captures tensors and system metrics during training to detect anomalies, but it does not provide a persistent experiment-tracking store for comparing hyperparameters and metrics across runs. It is tempting because it monitors training jobs, yet that is for debugging convergence issues, not cross-experiment comparison.

Go deeper

MLA-C01 ML Model Development Practice Question

Why each option matters

Option-by-option breakdown

Related to this question