AI-900 Practice Question: Describe fundamental principles of machine learning on Azure
What is 'Azure ML's experiment tracking' and why do data scientists use it?
⚠ Common exam trap
Many exam-takers 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.
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
✓
Recording hyperparameters, metrics, and configurations for each training run for comparison and reproduction
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.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Monitoring the progress of Azure ML service new feature deployments
Why it's wrong here
Monitoring the progress of Azure ML service new feature deployments is a platform operations concern, not a machine learning development activity. In Azure, service feature rollouts are tracked via Azure Service Health, DevOps release pipelines, or deployment dashboards that indicate whether a new service update has rolled out to a region. Experiment tracking, in contrast, captures the parameters, metrics, code, and environment of individual ML training runs—not the deployment status of Azure's own product updates. So this option confuses Azure's internal release observability with a data scientist's run-level reproducibility workflow.
- ✓
Recording hyperparameters, metrics, and configurations for each training run for comparison and reproduction
Why this is correct
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.
- ✗
Tracking which Azure ML resources are used by which team members for billing allocation
Why it's wrong here
Tracking which Azure ML resources are used by which team members for billing allocation belongs to Azure Cost Management, not to experiment tracking. You would use tags, cost analysis, and assigned budgets to attribute compute charges to a team or project, and this has nothing to do with the scientific details of a training run. Experiment tracking records metrics like loss, accuracy, and training time—not monetary costs or per-user resource consumption. Therefore, this option mistakes a financial governance practice for a model-development observability tool.
- ✗
A compliance audit log of all model predictions made in production
Why it's wrong here
A compliance audit log of all model predictions made in production is a governance and monitoring concern that applies after deployment, not during the training phase. In Azure ML, you would enable data collection and model data drift monitoring for deployed endpoints to log inference requests and responses for audit or compliance review. Experiment tracking, by contrast, operates at development time and captures training runs—including hyperparameters, metrics, and code snapshots—before a model ever serves predictions. Thus, this option conflates post-deployment inference logging with pre-deployment experiment tracking.
Go deeper
Related to this question
Learn chapter
Machine Learning Core Concepts
Key term
Feature
A feature is a distinct unit of functionality that delivers value to the user, often managed and tracked throughout the software development lifecycle.
Key term
Model
In IT and AI, a model is a trained mathematical representation that learns patterns from data to make predictions or decisions.
About these practice questions
Courseiva writes every AI-900 question from scratch — 985 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AI-900 practice question is part of Courseiva's free Microsoft 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 AI-900 exam.