MLflow Model Registry in MLOps - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

MLflow Model Registry: Model Stages

Which MLflow Model Registry stage is used to indicate a model that is ready for production deployment?

A Archived

B None

C Staging

D Production

💡 Hint

Think about the stage that means the model is stable and actively used.

The Production stage is used to mark models that are ready and approved for deployment in production environments.

💻 Command Output

intermediate

MLflow CLI: Listing Registered Models

What is the output of the following MLflow CLI command?

mlflow registered-models list

A Shows the current active model version only

B Lists all registered models with their latest versions and stages

C Displays the MLflow server status

D Raises an error: command not found

💡 Hint

Think about what 'list' usually does in command line tools.

The command mlflow registered-models list lists all registered models along with their latest versions and stages.

🔀 Workflow

advanced

MLflow Model Registry: Transitioning Model Stages

Which sequence of MLflow Python API calls correctly transitions a model version from Staging to Production?

MLOps

from mlflow.tracking import MlflowClient
client = MlflowClient()

# Assume model_name and version are defined

# Which code snippet correctly transitions the stage?

A client.transition_model_version_stage(name=model_name, version=version, stage='Production')

B client.update_model_version(name=model_name, version=version, stage='Production')

C client.transition_stage(model_name, version, 'Production')

D client.set_model_stage(model_name, version, 'Production')

💡 Hint

Look for the method name that includes 'transition' and 'stage'.

The correct method to change a model version's stage is transition_model_version_stage with parameters for name, version, and stage.

❓ Troubleshoot

advanced

MLflow Model Registry: Error Handling

You try to register a new model version but get this error: RESOURCE_ALREADY_EXISTS: Model version already exists. What is the most likely cause?

A The model artifact path is invalid

B The MLflow server is down and cannot register new models

C You are trying to register a model version with a version number that already exists for that model

D You forgot to specify the model name when registering

💡 Hint

Think about what 'already exists' means in this context.

The error means you tried to create a model version with a version number that is already taken for that model. Version numbers must be unique per model.

✅ Best Practice

expert

MLflow Model Registry: Managing Model Versions in CI/CD

In a CI/CD pipeline, what is the best practice for automatically promoting a model version to Production after successful testing?

A Use MLflow API in the pipeline script to transition the model version stage after tests pass

B Manually promote the model version in the MLflow UI after deployment

C Delete previous production versions before promoting a new one

D Skip stage transitions and deploy the model directly from the artifact store

💡 Hint

Automation is key in CI/CD pipelines.

Automating stage transitions using the MLflow API in the pipeline script ensures consistent and reliable promotion of models after tests pass.

Practice

1. What is the primary purpose of the MLflow Model Registry?

easy

A. To train machine learning models automatically

B. To visualize data for machine learning

C. To organize, track, and manage machine learning models and their versions

D. To store raw datasets for training

Solution

1. Step 1: Understand the role of MLflow Model Registry

   The Model Registry is designed to keep track of models, their versions, and lifecycle stages.

2. Step 2: Compare with other options

   Training models, visualizing data, and storing raw data are not functions of the Model Registry.

3. Final Answer:

   To organize, track, and manage machine learning models and their versions -> Option C

4. Quick Check:

   Model Registry purpose = Organize and track models [OK]

Hint: Model Registry = model tracking and version control [OK]

Common Mistakes:

• Confusing Model Registry with training or data storage
• Thinking it handles data visualization
• Assuming it automatically trains models

2. Which of the following is the correct command to register a model named my_model with MLflow Model Registry using the Python API?

easy

A. mlflow.create_model(name='my_model')

B. mlflow.register_model(model_uri='runs:/1234/my_model', name='my_model')

C. mlflow.add_model_version('my_model')

D. mlflow.model.register('my_model')

Solution

1. Step 1: Recall the MLflow Python API for registering models

   The correct function is mlflow.register_model() with parameters model_uri and name.

2. Step 2: Check the options for syntax correctness

   Only mlflow.register_model(model_uri='runs:/1234/my_model', name='my_model') uses the correct function and parameters. Others are invalid or do not exist.

3. Final Answer:

   mlflow.register_model(model_uri='runs:/1234/my_model', name='my_model') -> Option B

4. Quick Check:

   Register model = mlflow.register_model() [OK]

Hint: Use mlflow.register_model() with model_uri and name [OK]

Common Mistakes:

• Using non-existent functions like create_model or add_model_version
• Incorrect function names or missing parameters
• Confusing model registration with model creation

3. Given the following Python code snippet using MLflow Model Registry, what will be the output?

from mlflow import MlflowClient
client = MlflowClient()
model_versions = client.get_latest_versions(name='my_model', stages=['Production'])
print(len(model_versions))

medium

A. Zero, because the method returns an empty list always

B. The total number of all model versions regardless of stage

C. An error because get_latest_versions requires no parameters

D. The number of model versions currently in the Production stage

Solution

1. Step 1: Understand the method get_latest_versions

   This method returns the latest versions of a model filtered by the specified stages.

2. Step 2: Analyze the code behavior

   The code filters for versions in the 'Production' stage and prints how many such versions exist.

3. Final Answer:

   The number of model versions currently in the Production stage -> Option D

4. Quick Check:

   get_latest_versions with stages filters versions [OK]

Hint: get_latest_versions(name, stages) filters by stage [OK]

Common Mistakes:

• Assuming it returns all versions without filtering
• Thinking the method takes no parameters
• Believing it always returns zero

4. You try to transition a model version to the 'Staging' stage using this code:

client.transition_model_version_stage(name='my_model', version='2', stage='Staging')

But you get a TypeError. What is the likely cause?

medium

A. The version parameter should be an integer, not a string

B. The stage name 'Staging' is invalid

C. The method name is incorrect; it should be change_stage

D. The client object is not initialized

Solution

1. Step 1: Check the method signature for transition_model_version_stage

   The version parameter must be an integer representing the model version number.

2. Step 2: Identify the error cause

   Passing version='2' as a string causes a TypeError; it should be version=2 as an integer.

3. Final Answer:

   The version parameter should be an integer, not a string -> Option A

4. Quick Check:

   Version parameter type = int [OK]

Hint: Pass version as int, not string, to avoid TypeError [OK]

Common Mistakes:

• Passing version as string instead of integer
• Using wrong method name
• Assuming stage names are invalid
• Not initializing the client object

5. You want to automate deployment by moving the latest model version from 'Staging' to 'Production' only if its accuracy metric is above 0.9. Which MLflow Model Registry workflow correctly implements this logic?

hard

A. Retrieve latest 'Staging' version, check accuracy metric, then transition to 'Production' if > 0.9

B. Transition all versions to 'Production' without checking metrics

C. Delete all 'Staging' versions and register a new model in 'Production'

D. Manually download the model and deploy without using Model Registry stages

Solution

1. Step 1: Identify the correct workflow for conditional deployment

   You must get the latest model version in 'Staging' and check its accuracy metric before promoting.

2. Step 2: Understand why other options are incorrect

   Transitioning all versions blindly ignores quality checks; deleting and manual deployment bypasses registry benefits.

3. Final Answer:

   Retrieve latest 'Staging' version, check accuracy metric, then transition to 'Production' if > 0.9 -> Option A

4. Quick Check:

   Conditional stage transition based on metric = correct workflow [OK]

Hint: Check metric before stage transition to automate deployment [OK]

Common Mistakes:

• Skipping metric check before promotion
• Promoting all versions blindly
• Deleting versions unnecessarily
• Ignoring Model Registry stages