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.