In MLOps, why do we use parameterized pipeline runs?
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.
Given this command to run a pipeline with parameters, what is the expected output snippet?
mlflow pipelines run --pipeline-name my_pipeline --param learning_rate=0.01 --param epochs=10
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.
Which YAML snippet correctly defines parameters for a pipeline step?
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.
You run a pipeline with parameters but get this error: TypeError: run() got an unexpected keyword argument 'lr'. What is the likely cause?
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.
Arrange the steps in the correct order to run a parameterized pipeline successfully.
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.