MicrosoftManage the machine learning model lifecycle and operations

ML Pipelines & Data Drift — AI-300 Practice Question

A representative Microsoft Machine Learning Operations Engineer Associate (AI-300) exam question on ML Pipelines & Data Drift. Work through it below, then read why each option is right or wrong.

This question is part of the free Microsoft Machine Learning Operations Engineer Associate practice test.

Short answer

The correct answer is C. Create an Azure ML pipeline that runs data drift detection as the first step, then conditionally execute the retraining step only if drift metrics exceed the threshold using pipeline step conditions.

Azure ML pipelines support conditional step execution, allowing data drift detection to gate retraining—this is the most cost-efficient and native approach. C uses built-in pipeline orchestration to avoid unnecessary compute. B relies on external alerting and manual intervention, which is slower and less integrated. D still incurs hourly compute costs even when retraining is skipped. A uses GitHub Actions for polling rather than event-driven automation, introducing latency and external dependencies. The pipeline-native approach in C aligns with the ML pipelines concept documented in the official guide.

The Question

Your organization has deployed a churn prediction model that must be retrained weekly with fresh customer data. The retraining job currently runs on a fixed schedule, but recent data drift detection indicates that model performance degrades significantly between retraining cycles. You need to implement a solution that automatically triggers retraining only when data drift exceeds a defined threshold, while minimizing unnecessary compute costs. What is the best approach?

AUse GitHub Actions to poll the model registry every 6 hours, compare current model metrics against baseline, and trigger a retraining workflow if metrics fall below acceptable thresholds
BDeploy a separate Azure Monitor alert that triggers an Azure Logic App whenever Application Insights detects performance degradation, which then manually invokes a retraining run
CCreate an Azure ML pipeline that runs data drift detection as the first step, then conditionally execute the retraining step only if drift metrics exceed the threshold using pipeline step conditionsCorrect
DSchedule the retraining pipeline to run every hour and add a Python script that skips model retraining if drift is below threshold, reducing unnecessary training iterations

Why C is correct

Azure ML pipelines support conditional step execution, allowing data drift detection to gate retraining—this is the most cost-efficient and native approach. C uses built-in pipeline orchestration to avoid unnecessary compute. B relies on external alerting and manual intervention, which is slower and less integrated. D still incurs hourly compute costs even when retraining is skipped. A uses GitHub Actions for polling rather than event-driven automation, introducing latency and external dependencies. The pipeline-native approach in C aligns with the ML pipelines concept documented in the official guide.

Why the other options are wrong

Option A: Use GitHub Actions to poll the model registry every 6 hours, compare current model metrics against baseline, and trigger a retraining workflow if metrics fall below acceptable thresholds

Option A does not satisfy the requirement in the scenario. Review the explanation above: the correct choice (C) is the only one that fully meets every constraint stated in the question.

Option B: Deploy a separate Azure Monitor alert that triggers an Azure Logic App whenever Application Insights detects performance degradation, which then manually invokes a retraining run

Option B does not satisfy the requirement in the scenario. Review the explanation above: the correct choice (C) is the only one that fully meets every constraint stated in the question.

Option D: Schedule the retraining pipeline to run every hour and add a Python script that skips model retraining if drift is below threshold, reducing unnecessary training iterations

Option D does not satisfy the requirement in the scenario. Review the explanation above: the correct choice (C) is the only one that fully meets every constraint stated in the question.

Key idea: ML Pipelines & Data Drift

Azure ML pipelines support conditional step execution, allowing data drift detection to gate retraining—this is the most cost-efficient and native approach. C uses built-in pipeline orchestration to avoid unnecessary compute. B relies on external alerting and manual intervention, which is slower and less integrated. D still incurs hourly compute costs even when retraining is skipped. A uses GitHub Actions for polling rather than event-driven automation, introducing latency and external dependencies. The pipeline-native approach in C aligns with the ML pipelines concept documented in the official guide. On the AI-300 exam, questions in the "Manage the machine learning model lifecycle and operations" domain test whether you can map a scenario's constraints to the right choice. Read the requirement carefully, eliminate options that violate any single constraint, and pick the one that satisfies all of them with the least operational overhead.

Ready to see how you'd score?

Take the free practice quiz and find out which Microsoft Machine Learning Operations Engineer Associate domains you need to focus on. No signup required.

Practice 5 similar questions

Same cert, same or adjacent domain. Use these after reviewing the explanation.

Related Microsoft Machine Learning Operations Engineer Associate Practice Questions

Official sources used

Verify program and exam details at the source before scheduling.