Model metadata and lineage in MLOps - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to log model metadata using MLflow.

MLOps

import mlflow
mlflow.[1]("learning_rate", 0.01)

Drag options to blanks, or click blank then click option'

Amodels

Bset_tag

Clog_param

Dstart_run

Attempts:

3 left

💡 Hint

Common Mistakes

Using start_run instead of log_param.

Trying to log parameters with models module.

The log_param function records a parameter like learning rate in MLflow metadata.

2fill in blank

medium

Complete the code to start an MLflow run for tracking.

MLOps

with mlflow.[1]():
    mlflow.log_metric("accuracy", 0.95)

Drag options to blanks, or click blank then click option'

Aexperiment

Blog_metric

Crun

Dstart_run

Attempts:

3 left

💡 Hint

Common Mistakes

Using log_metric as a context manager.

Using experiment which is not a context manager.

The start_run function starts a new MLflow run context to track metrics and parameters.

3fill in blank

hard

Fix the error in the code to register a model in MLflow Model Registry.

MLOps

mlflow.[1]("runs:/12345/model", "MyModel")

Drag options to blanks, or click blank then click option'

Aregister_model

Blog_model

Cmodels

Dstart_run

Attempts:

3 left

💡 Hint

Common Mistakes

Using log_model which does not exist.

Using start_run which is unrelated.

The register_model function registers a model in the MLflow Model Registry using the model URI and name.

4fill in blank

hard

Fill both blanks to create a dictionary capturing model metadata and lineage.

MLOps

metadata = {"model_name": [1], "source_run_id": [2]

Drag options to blanks, or click blank then click option'

A"MyModel"

B"12345"

C"run_67890"

D"ModelV1"

Attempts:

3 left

💡 Hint

Common Mistakes

Using numeric values instead of strings.

Mixing up model name and run ID.

The model_name is a string like "MyModel" and source_run_id is the run identifier string.

5fill in blank

hard

Fill all three blanks to log model metadata with tags and parameters.

MLOps

mlflow.start_run()
mlflow.set_tag("[1]", "v1.0")
mlflow.log_param("[2]", 100)
mlflow.log_metric("[3]", 0.98)

Drag options to blanks, or click blank then click option'

Aversion

Bnum_trees

Caccuracy

Dstage

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing tags with parameters or metrics.

Using incorrect keys that MLflow does not recognize.

Tags like version describe model version, parameters like num_trees describe model settings, and metrics like accuracy show performance.

Practice

1. What is the main purpose of model metadata in MLOps?

easy

A. To clean the input data before training

B. To execute the model training automatically

C. To deploy the model to production

D. To store important details about the model's creation and performance

Solution

1. Step 1: Understand what model metadata contains

   Model metadata includes details like training parameters, performance metrics, and environment info.

2. Step 2: Identify the purpose of metadata

   This information helps track how the model was created and how well it performs.

3. Final Answer:

   To store important details about the model's creation and performance -> Option D

4. Quick Check:

   Model metadata = model details storage [OK]

Hint: Metadata stores model info, not execution or deployment [OK]

Common Mistakes:

• Confusing metadata with deployment steps
• Thinking metadata runs the model
• Mixing metadata with data cleaning

2. Which of the following is the correct way to represent model lineage?

easy

A. A graph showing connections between data, code, and model versions

B. A list of model hyperparameters only

C. A single file containing the trained model weights

D. A script that trains the model

Solution

1. Step 1: Define model lineage

   Model lineage tracks the history and relationships between data, code, and model versions.

2. Step 2: Identify correct representation

   A graph or map showing these connections is the correct way to represent lineage.

3. Final Answer:

   A graph showing connections between data, code, and model versions -> Option A

4. Quick Check:

   Lineage = connection graph [OK]

Hint: Lineage means tracking history and connections [OK]

Common Mistakes:

• Thinking lineage is just model parameters
• Confusing lineage with model files
• Assuming lineage is a training script

3. Given the following metadata record:

{"model_version": "v1.2", "accuracy": 0.92, "training_data": "dataset_v3", "code_commit": "abc123"}

What does the code_commit field represent?

medium

A. The version of the training dataset used

B. The unique identifier of the code version used to train the model

C. The accuracy score of the model

D. The deployment environment name

Solution

1. Step 1: Analyze the metadata fields

   The field code_commit usually stores the code version identifier, like a git commit hash.

2. Step 2: Match field meaning to options

   It identifies the exact code used to train the model, ensuring reproducibility.

3. Final Answer:

   The unique identifier of the code version used to train the model -> Option B

4. Quick Check:

   code_commit = code version ID [OK]

Hint: Code commit means code version ID, not data or accuracy [OK]

Common Mistakes:

• Confusing code_commit with dataset version
• Thinking it stores accuracy
• Assuming it is deployment info

4. You notice that the model lineage graph is missing links between data versions and model versions. What is the most likely cause?

medium

A. The training code commit hash is missing

B. The model accuracy was too low

C. The metadata did not record the data version used during training

D. The deployment script failed to run

Solution

1. Step 1: Understand lineage graph links

   Links between data versions and model versions require metadata recording the data version used.

2. Step 2: Identify missing metadata impact

   If data version info is missing, lineage cannot connect data to model versions.

3. Final Answer:

   The metadata did not record the data version used during training -> Option C

4. Quick Check:

   Missing data version metadata breaks lineage links [OK]

Hint: Missing data version metadata breaks lineage connections [OK]

Common Mistakes:

• Blaming model accuracy for lineage issues
• Confusing deployment errors with lineage
• Assuming code commit missing causes data link loss

5. You want to ensure full reproducibility of your ML model training. Which combination of metadata and lineage tracking is best?

hard

A. Record model hyperparameters, training data version, code commit hash, and link them in a lineage graph

B. Only save the final trained model file

C. Track deployment environment and ignore training data versions

D. Store training logs without linking to code or data versions

Solution

1. Step 1: Identify key elements for reproducibility

   Reproducibility requires knowing hyperparameters, data version, and exact code used.

2. Step 2: Understand lineage role

   Linking these elements in a lineage graph shows their relationships and history.

3. Step 3: Evaluate options

   Only Record model hyperparameters, training data version, code commit hash, and link them in a lineage graph includes all necessary metadata and lineage tracking for full reproducibility.

4. Final Answer:

   Record model hyperparameters, training data version, code commit hash, and link them in a lineage graph -> Option A

5. Quick Check:

   Full reproducibility = metadata + lineage graph [OK]

Hint: Combine metadata and lineage graph for full reproducibility [OK]

Common Mistakes:

• Saving only model files without metadata
• Ignoring data version tracking
• Not linking metadata in lineage