Courseiva
Model Development →mediumMultiple Choice

Databricks-ML-Pro Model Development Practice Question

Exhibit

MLflow.log_metric('rmse', 0.5)
MLflow.log_metric('rmse', 0.45)
MLflow.log_metric('rmse', 0.4)

Refer to the exhibit. What happens to these logged metrics in MLflow when the training run completes?

⚠ Common exam trap

Candidates frequently assume MLflow overwrites previous metric values when updated, not realizing that MLflow natively supports time-series logging for every call of log_metric during a run.

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

✓

MLflow keeps all values, enabling the visualization of metrics over time.

MLflow is designed to track metrics over time, which is crucial for monitoring model convergence during training. By logging the same metric key multiple times, MLflow stores each value as a point in a time series. This allows developers to visualize the training progress and identify when the model stops improving, which is critical for implementing early stopping and optimizing training efficiency in deep learning.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    MLflow overwrites the previous value with the latest value.

    Why it's wrong here

    MLflow preserves all logged values for a given metric key. Overwriting would destroy the training history, preventing the analysis of convergence. Maintaining the series of values is essential for visualizing training progress and debugging model performance throughout the entire training process in a professional ML experiment lifecycle.

  • ✓

    MLflow keeps all values, enabling the visualization of metrics over time.

    Why this is correct

    Storing multiple values for a single metric key creates a sequence that MLflow can plot. This is vital for analyzing the model's convergence behavior, allowing data scientists to identify potential issues like overfitting or high variance early, and helping to fine-tune the training process effectively during the experiment cycle.

  • ✗

    The run will throw an error because the metric key is not unique.

    Why it's wrong here

    Metric keys are not required to be unique within a single run. MLflow expects multiple logs for the same key to track training progress. Throwing an error would disrupt the training workflow, which is the opposite of the purpose of a professional tracking tool designed for iterative development processes.

  • ✗

    MLflow averages the values and stores the mean.

    Why it's wrong here

    Averaging the values would hide the training trajectory, making it impossible to see if the model is learning correctly or fluctuating. Storing the full sequence is necessary for transparency and proper evaluation, as it allows users to see the actual progress of the metric as the model is optimized.

About these practice questions

One of 300 original Databricks-ML-Pro practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written and reviewed by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

Last reviewed September 2026 · checked against the official Databricks exam blueprint

This Databricks-ML-Pro practice question is part of Courseiva's free Databricks 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 Databricks-ML-Pro exam.