Pipeline versioning and reproducibility in MLOps - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to save the pipeline version using MLflow.

MLOps

mlflow.set_experiment('my_experiment')
with mlflow.start_run():
    mlflow.log_param('pipeline_version', [1])

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

A'v1.0.0'

B1.0

Cversion

Dpipeline

Attempts:

3 left

💡 Hint

Common Mistakes

Using a number instead of a string for version.

Pipeline version should be a string like 'v1.0.0' to track reproducible runs.

2fill in blank

medium

Complete the code to load a specific pipeline version from the registry.

MLOps

from mlflow import pyfunc
model = pyfunc.load_model('models:/my_pipeline/[1]')

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

Aproduction

Bv1

C1

Dlatest

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'latest' which may not be stable.

Loading the 'production' stage ensures you get the stable pipeline version.

3fill in blank

hard

Fix the error in the code to ensure pipeline reproducibility by pinning dependencies.

MLOps

import subprocess
def save_requirements():
    with open('requirements.txt', 'w') as f:
        f.write([1])

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

Aos.system('pip freeze > requirements.txt')

Bpip freeze > requirements.txt

Csubprocess.check_output(['pip', 'freeze'], text=True)

Df.write('pip freeze')

Attempts:

3 left

💡 Hint

Common Mistakes

Writing the string 'pip freeze' instead of the command output.

Using subprocess.check_output captures the output of 'pip freeze' as a string and writes it to the file correctly.

4fill in blank

hard

Fill both blanks to create a reproducible pipeline run with a fixed random seed.

MLOps

import random
import numpy as np
random.[1](42)
np.random.[2](42)

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

Aseed

Brandom

Crandint

Dchoice

Attempts:

3 left

💡 Hint

Common Mistakes

Using methods that generate random numbers instead of setting the seed.

Setting the seed for both random and numpy.random ensures reproducible randomness.

5fill in blank

hard

Fill all three blanks to log pipeline metadata with MLflow for reproducibility.

MLOps

mlflow.log_param('[1]', 'v1.0.0')
mlflow.log_param('[2]', 'my_experiment')
mlflow.log_param('[3]', '2024-06-01')

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

Apipeline_version

Brun_id

Cstart_date

Dexperiment_name

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up parameter names or using incorrect keys.

Logging 'pipeline_version', 'experiment_name', and 'start_date' helps track pipeline runs clearly.

Practice

1. What is the main purpose of pipeline versioning in MLOps?

easy

A. To increase the size of the dataset used

B. To speed up the training process of machine learning models

C. To track changes in workflows and configurations over time

D. To automatically fix bugs in the code

Solution

1. Step 1: Understand pipeline versioning

   Pipeline versioning means keeping track of changes made to the steps and settings in your workflow.

2. Step 2: Identify the main goal

   This helps teams know what changed and when, making it easier to reproduce or fix issues.

3. Final Answer:

   To track changes in workflows and configurations over time -> Option C

4. Quick Check:

   Pipeline versioning = track changes [OK]

Hint: Versioning means tracking changes over time [OK]

Common Mistakes:

• Confusing versioning with speeding up training
• Thinking versioning fixes bugs automatically
• Believing versioning increases dataset size

2. Which of the following is the correct way to fix a random seed in Python for reproducibility in a pipeline?

easy

A. random.seed(42)

B. random.fix_seed(42)

C. seed.random(42)

D. fix.seed(42)

Solution

1. Step 1: Recall Python random seed syntax

   In Python, the random module uses random.seed(value) to fix the seed.

2. Step 2: Check each option

   Only random.seed(42) matches the correct syntax; others are invalid function calls.

3. Final Answer:

   random.seed(42) -> Option A

4. Quick Check:

   Fix seed in Python = random.seed() [OK]

Hint: Use random.seed(value) to fix seed in Python [OK]

Common Mistakes:

• Using incorrect function names like fix_seed or seed.random
• Confusing method order or syntax
• Missing the random module prefix

3. Given this snippet in a pipeline script:

import random
random.seed(10)
print(random.randint(1, 100))
random.seed(10)
print(random.randint(1, 100))

What will be the output?

medium

A. 67 followed by 67

B. 67 followed by a different number

C. Two different random numbers

D. Error due to repeated seed

Solution

1. Step 1: Understand seed effect on random numbers

   Setting the seed to the same value resets the random number generator to the same state.

2. Step 2: Analyze the code output

   Both calls to random.randint(1, 100) after setting seed(10) will produce the same number, 67.

3. Final Answer:

   67 followed by 67 -> Option A

4. Quick Check:

   Same seed = same random output [OK]

Hint: Same seed resets random sequence, repeat outputs [OK]

Common Mistakes:

• Assuming different outputs after resetting seed
• Thinking repeated seed causes error
• Ignoring seed effect on randomness

4. You run a pipeline but get different results each time, even though you fixed the random seed. What is the most likely cause?

medium

A. The random seed was set correctly

B. The pipeline uses non-deterministic operations or external data changes

C. The pipeline versioning is enabled

D. The code has syntax errors

Solution

1. Step 1: Understand reproducibility factors

   Fixing the random seed controls randomness but does not cover external changes or non-deterministic steps.

2. Step 2: Identify cause of varying results

   If results differ despite fixed seed, likely external data or operations like parallelism cause variation.

3. Final Answer:

   The pipeline uses non-deterministic operations or external data changes -> Option B

4. Quick Check:

   Non-determinism breaks reproducibility [OK]

Hint: Check external data and non-deterministic steps [OK]

Common Mistakes:

• Assuming seed fixes all randomness
• Confusing versioning with reproducibility
• Blaming syntax errors for result changes

5. You want to ensure your ML pipeline is fully reproducible across different machines. Which combination is best to achieve this?

hard

A. Only fix random seeds and ignore environment differences

B. Run pipeline without versioning but log outputs manually

C. Use different random seeds each run and update pipeline versions

D. Fix random seeds, use containerized environments, and version pipeline code

Solution

1. Step 1: Identify reproducibility requirements

   Reproducibility needs fixed seeds, consistent environments, and tracking code changes.

2. Step 2: Evaluate options for best practice

   Fix random seeds, use containerized environments, and version pipeline code combines fixing seeds, containerization for environment consistency, and versioning for tracking changes.

3. Final Answer:

   Fix random seeds, use containerized environments, and version pipeline code -> Option D

4. Quick Check:

   Seeds + containers + versioning = reproducibility [OK]

Hint: Combine seeds, containers, and versioning for full reproducibility [OK]

Common Mistakes:

• Ignoring environment differences
• Changing seeds each run
• Skipping pipeline versioning