What is 'Azure ML's experiment tracking' and why do data scientists use it?
Recording hyperparameters, metrics, and configurations for each training run is exactly what Azure ML experiment tracking does. Each run—often managed through Azure ML's SDK, CLI, or MLflow integration—logs a unique snapshot of the code, environment, dataset version, and hyperparameters, along with scalar and tensor metrics like loss or accuracy. This enables data scientists to compare runs side-by-side in the studio, identify the best performing configuration, and reproduce historical results by replaying the exact logged run. The Run History and metrics tables are purpose-built for this iterative, experimental comparison during model development.
Why this answer
Azure ML's experiment tracking is a feature that automatically records hyperparameters, metrics, and configuration details for each training run. Data scientists use it to compare multiple runs, identify the best-performing model, and reproduce results by revisiting the exact settings and data used. This is essential for iterative experimentation and ensuring reproducibility in machine learning workflows.
Exam trap
The trap here is that candidates confuse experiment tracking (recording training run metadata) with monitoring or auditing of deployed models, leading them to choose options about deployment progress or production compliance logs.
How to eliminate wrong answers
Option A is wrong because it describes monitoring deployment progress of new features, which is a DevOps or MLOps concern, not the purpose of experiment tracking for training runs. Option C is wrong because it refers to resource usage tracking for billing allocation, which is handled by Azure Cost Management and resource tagging, not by experiment tracking. Option D is wrong because it describes a compliance audit log for model predictions in production, which is related to model monitoring and governance, not the recording of training run metadata.