Parameterized pipeline runs in MLOps - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to pass a parameter named 'learning_rate' with value 0.01 to the pipeline run.

MLOps

pipeline_run = pipeline.run(parameters={"learning_rate": [1])

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

A0.1

B0.01

C1

D"0.01"

Attempts:

3 left

💡 Hint

Common Mistakes

Passing the learning rate as a string instead of a float.

Using an incorrect value like 0.1.

The parameter 'learning_rate' should be passed as a float 0.01, not as a string or other value.

2fill in blank

medium

Complete the code to retrieve the parameter 'batch_size' from the pipeline run's parameters dictionary.

MLOps

batch_size = pipeline_run.parameters.get([1], 32)

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

A"batch_size"

B"batch"

Cbatch_size

D"size"

Attempts:

3 left

💡 Hint

Common Mistakes

Using a wrong key string like 'batch' or 'size'.

Using the variable name without quotes.

The key to retrieve the batch size parameter is the string 'batch_size'.

3fill in blank

hard

Fix the error in the code to correctly pass multiple parameters to the pipeline run.

MLOps

pipeline_run = pipeline.run(parameters=[1])

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

A"epochs=10, lr=0.001"

B["epochs", 10, "lr", 0.001]

C("epochs", 10, "lr", 0.001)

D{"epochs": 10, "lr": 0.001}

Attempts:

3 left

💡 Hint

Common Mistakes

Passing parameters as a list or tuple instead of a dictionary.

Passing parameters as a string.

Parameters must be passed as a dictionary with keys and values, not as a list, tuple, or string.

4fill in blank

hard

Fill both blanks to create a dictionary comprehension that filters parameters with values greater than 0.5.

MLOps

filtered_params = {k: v for k, v in pipeline_run.parameters.items() if v [1] [2]

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

A>

B0.5

C<

D1

Attempts:

3 left

💡 Hint

Common Mistakes

Using less than operator instead of greater than.

Using wrong threshold values.

The condition filters parameters where the value is greater than 0.5 using > and 0.5.

5fill in blank

hard

Fill all three blanks to create a dictionary of parameters where keys are uppercase and values are strings.

MLOps

param_strs = [1]: str([2]) for [3], v in pipeline_run.parameters.items()

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

Ak.upper()

Bv

Ck

Dv.upper()

Attempts:

3 left

💡 Hint

Common Mistakes

Using v.upper() which is invalid if value is not string.

Swapping key and value variables.

The keys are converted to uppercase with k.upper(), values converted to strings with str(v), and the loop uses k, v.

Practice

1. What is the main benefit of using parameterized pipeline runs in MLOps?

easy

A. They generate reports after pipeline completion.

B. They automatically fix errors in the pipeline code.

C. They speed up the pipeline execution by parallel processing.

D. They allow customizing pipeline inputs without changing the pipeline code.

Solution

1. Step 1: Understand pipeline parameterization

   Parameterized runs let you pass different inputs to the same pipeline code, making it flexible.

2. Step 2: Identify the main benefit

   This avoids changing the pipeline code for each run, saving time and reducing errors.

3. Final Answer:

   They allow customizing pipeline inputs without changing the pipeline code. -> Option D

4. Quick Check:

   Parameterization = Customize inputs without code change [OK]

Hint: Remember: parameters change inputs, not code [OK]

Common Mistakes:

• Thinking parameters fix code errors
• Confusing parameterization with parallelism
• Assuming parameters generate reports

2. Which of the following is the correct way to pass parameters when triggering a pipeline run using a CLI command?

easy

A. pipeline run -param learning_rate 0.01

B. pipeline run --param learning_rate=0.01

C. pipeline run --parameters learning_rate:0.01

D. pipeline run --param learning_rate:0.01

Solution

1. Step 1: Review common CLI parameter syntax

   Most CLI tools use double dashes and equal signs to pass key-value parameters, like --param key=value.

2. Step 2: Match the correct syntax

   pipeline run --param learning_rate=0.01 uses --param learning_rate=0.01, which is the standard and correct format.

3. Final Answer:

   pipeline run --param learning_rate=0.01 -> Option B

4. Quick Check:

   CLI param syntax = --param key=value [OK]

Hint: Use --param key=value format for CLI parameters [OK]

Common Mistakes:

• Using colon instead of equal sign
• Missing double dashes before param
• Separating key and value with space

3. Given this pipeline run command:
pipeline run --param batch_size=32 --param epochs=10
What will be the values of batch_size and epochs inside the pipeline?

medium

A. batch_size=32, epochs=10

B. batch_size=32, epochs=default

C. batch_size=10, epochs=32

D. batch_size=default, epochs=10

Solution

1. Step 1: Identify parameter assignments in the command

   The command passes batch_size=32 and epochs=10 explicitly.

2. Step 2: Understand parameter values inside the pipeline

   These values override any defaults, so inside the pipeline batch_size=32 and epochs=10.

3. Final Answer:

   batch_size=32, epochs=10 -> Option A

4. Quick Check:

   Passed params = used values inside pipeline [OK]

Hint: Parameters passed override defaults inside pipeline [OK]

Common Mistakes:

• Swapping parameter values
• Assuming defaults when parameters are passed
• Confusing parameter names

4. You run a pipeline with this command:
pipeline run --param learning_rate=0.01 --param epochs
But the pipeline fails to start. What is the most likely cause?

medium

A. Parameters must be passed in a config file, not CLI.

B. Incorrect parameter name learning_rate.

C. Missing value for the parameter epochs.

D. Pipeline does not support parameters.

Solution

1. Step 1: Analyze the command parameters

   The parameter epochs is passed without a value, which is invalid syntax.

2. Step 2: Understand pipeline parameter requirements

   Each parameter must have a value; missing values cause errors and prevent pipeline start.

3. Final Answer:

   Missing value for the parameter epochs. -> Option C

4. Quick Check:

   All params need values [OK]

Hint: Always provide values for all parameters [OK]

Common Mistakes:

• Passing parameters without values
• Assuming pipeline ignores missing values
• Confusing parameter names

5. You want to run the same pipeline with different datasets without changing the pipeline code. Which approach best uses parameterized pipeline runs to achieve this?

hard

A. Pass the dataset path as a parameter when triggering each pipeline run.

B. Create a separate pipeline for each dataset.

C. Hardcode dataset paths inside the pipeline code.

D. Manually edit the pipeline code before each run.

Solution

1. Step 1: Understand the goal

   You want to reuse the same pipeline code but run it on different datasets.

2. Step 2: Use parameterized runs for dataset paths

   Passing dataset paths as parameters lets you run the pipeline multiple times with different inputs without code changes.

3. Step 3: Evaluate other options

   Creating separate pipelines or editing code manually is inefficient and error-prone.

4. Final Answer:

   Pass the dataset path as a parameter when triggering each pipeline run. -> Option A

5. Quick Check:

   Parameterize inputs for reuse [OK]

Hint: Use parameters to swap datasets, not code edits [OK]

Common Mistakes:

• Creating multiple pipelines unnecessarily
• Hardcoding values inside pipeline code
• Editing code before every run