Parameterized pipeline runs in MLOps - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the main benefit of parameterized pipeline runs?

In MLOps, why do we use parameterized pipeline runs?

A To allow running the same pipeline with different inputs without changing the code

B To make the pipeline run faster by skipping steps

C To automatically fix errors during pipeline execution

D To store pipeline results in a database

💡 Hint

Think about how you can reuse a pipeline for different data or settings.

Parameterized pipelines let you reuse the same pipeline code by passing different values as inputs, making it flexible and efficient.

💻 Command Output

intermediate

Output of running a pipeline with parameters

Given this command to run a pipeline with parameters, what is the expected output snippet?

MLOps

mlflow pipelines run --pipeline-name my_pipeline --param learning_rate=0.01 --param epochs=10

A SyntaxError: invalid syntax near '--param'

B Error: Unknown parameter 'learning_rate'

C Pipeline 'my_pipeline' completed with default parameters

D Starting pipeline 'my_pipeline' with parameters: learning_rate=0.01, epochs=10

💡 Hint

Look for the message confirming the pipeline started with given parameters.

The command runs the pipeline with specified parameters, so the output confirms the parameters used.

❓ Configuration

advanced

Correct YAML snippet for parameterized pipeline

Which YAML snippet correctly defines parameters for a pipeline step?

A

steps:
  - name: train
    parameters:
      learning_rate: 0.01
      epochs: 10

B

steps:
  - name: train
    params:
      learning_rate: 0.01
      epochs: 10

C

steps:
  - train:
      parameters:
        learning_rate: 0.01
        epochs: 10

D

steps:
  - name: train
    parameters: [learning_rate=0.01, epochs=10]

💡 Hint

Look for the correct key name and structure for parameters in YAML.

The key 'parameters' under the step name is the correct way to define parameters as key-value pairs in YAML.

❓ Troubleshoot

advanced

Why does the pipeline fail when passing parameters?

You run a pipeline with parameters but get this error: TypeError: run() got an unexpected keyword argument 'lr'. What is the likely cause?

A The pipeline code has a syntax error unrelated to parameters

B The parameter name 'lr' is not defined in the pipeline code or config

C The pipeline requires parameters to be passed as environment variables

D The pipeline run command does not support parameters

💡 Hint

Check if the parameter name matches what the pipeline expects.

The error means the pipeline code does not expect a parameter named 'lr'. The parameter name must match exactly what the pipeline defines.

🔀 Workflow

expert

Order of steps to run a parameterized pipeline

Arrange the steps in the correct order to run a parameterized pipeline successfully.

A 1,3,2,4

B 2,1,3,4

C 1,2,3,4

D 1,2,4,3

💡 Hint

Think about defining, passing, validating, then running.

First, parameters must be defined in config. Then values are passed when running. Validation happens before execution to catch errors early.

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