Self-service ML platform architecture in MLOps - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define the main component responsible for model training in a self-service ML platform.

MLOps

class [1]:
    def train(self, data):
        # Training logic here
        pass

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

AModelTrainer

BDataLoader

CModelRegistry

DFeatureStore

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing a component that handles data loading or feature storage instead of training.

The ModelTrainer class is typically responsible for training ML models in a self-service ML platform.

2fill in blank

medium

Complete the code to initialize the feature store client in the platform.

MLOps

feature_store_client = [1]()

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

AModelTrainer

BDataLoader

CFeatureStoreClient

DModelRegistry

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing with model training or data loading components.

The FeatureStoreClient is used to interact with the feature store in a self-service ML platform.

3fill in blank

hard

Fix the error in the code that registers a model in the model registry.

MLOps

model_registry = ModelRegistry()
model_registry.[1](model_name, model_object)

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

Aregister_model

Bload_model

Ctrain_model

Ddelete_model

Attempts:

3 left

💡 Hint

Common Mistakes

Using methods that do not add the model to the registry.

The correct method to add a model to the registry is register_model.

4fill in blank

hard

Fill both blanks to create a dictionary comprehension that maps feature names to their types for features with numeric types.

MLOps

numeric_features = {feature[1]: feature_type[2] for feature, feature_type in features.items() if feature_type in ['int', 'float']}

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

A:

B,

C.

D=

Attempts:

3 left

💡 Hint

Common Mistakes

Using commas or dots instead of colons in key-value pairs.

In dictionary comprehensions, key-value pairs are separated by a colon :.

5fill in blank

hard

Fill all three blanks to filter models with accuracy above 0.9 and create a dictionary with model names and their accuracies.

MLOps

high_accuracy_models = { [1]: [2] for [3] in models.items() if [2] > 0.9 }

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

Amodel_name

Baccuracy

Cmodel_name, accuracy

Dmodel

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect variable names or not unpacking items properly.

The dictionary comprehension uses model_name as key, accuracy as value, and iterates over model_name, accuracy pairs.

Practice

1. What is the main purpose of a self-service ML platform in an organization?

easy

A. To monitor only the hardware usage of ML servers

B. To replace data scientists with automated tools

C. To enable teams to build and deploy ML models independently and faster

D. To store large amounts of raw data without processing

Solution

1. Step 1: Understand the role of self-service ML platforms

   These platforms are designed to help teams work faster and independently by providing tools and interfaces for ML tasks.

2. Step 2: Compare options with this purpose

   Options A, B, and C do not focus on enabling teams to build and deploy models independently.

3. Final Answer:

   To enable teams to build and deploy ML models independently and faster -> Option C

4. Quick Check:

   Self-service ML platform purpose = Enable independent, faster ML work [OK]

Hint: Focus on independence and speed for ML teams [OK]

Common Mistakes:

• Confusing data storage with platform purpose
• Thinking it replaces data scientists
• Assuming it only monitors hardware

2. Which component is essential in a self-service ML platform for managing model versions?

easy

A. Model registry

B. Data ingestion pipeline

C. Experiment tracking UI

D. Security gateway

Solution

1. Step 1: Identify the component for model version management

   The model registry is designed to store and manage different versions of ML models.

2. Step 2: Eliminate other options

   Data ingestion handles data, experiment tracking logs experiments, and security gateway manages access, none manage model versions.

3. Final Answer:

   Model registry -> Option A

4. Quick Check:

   Model version management = Model registry [OK]

Hint: Model versions live in the registry, not data or security parts [OK]

Common Mistakes:

• Confusing experiment tracking with model versioning
• Choosing data pipeline for model management
• Mixing security with model storage

3. Given a self-service ML platform with components: UI, data pipeline, model registry, deployment, and monitoring, which sequence correctly represents the typical workflow?

medium

A. UI -> Data pipeline -> Model registry -> Deployment -> Monitoring

B. Data pipeline -> Model registry -> UI -> Deployment -> Monitoring

C. Data pipeline -> UI -> Model registry -> Deployment -> Monitoring

D. UI -> Model registry -> Data pipeline -> Deployment -> Monitoring

Solution

1. Step 1: Understand the typical ML workflow in a self-service platform

   The user interacts with the UI first to start tasks, then data is processed, models are registered, deployed, and monitored.

2. Step 2: Match the sequence with this logic

   UI -> Data pipeline -> Model registry -> Deployment -> Monitoring starts with UI, then data pipeline, model registry, deployment, and monitoring, which fits the workflow.

3. Final Answer:

   UI -> Data pipeline -> Model registry -> Deployment -> Monitoring -> Option A

4. Quick Check:

   Workflow order = UI first, then data, model, deploy, monitor [OK]

Hint: User starts at UI, then data, model, deploy, monitor [OK]

Common Mistakes:

• Starting workflow with data pipeline instead of UI
• Mixing order of model registry and UI
• Placing data pipeline after deployment

4. A self-service ML platform's deployment component fails to update models after new versions are registered. What is the most likely cause?

medium

A. The data pipeline is processing data too slowly

B. The model registry is not linked to the deployment pipeline

C. The UI does not allow model version selection

D. Monitoring tools are not configured

Solution

1. Step 1: Analyze the failure symptom

   Deployment does not update models after new versions are registered, indicating a disconnect between model registry and deployment.

2. Step 2: Evaluate options for cause

   Slow data pipeline or UI issues won't stop deployment updates; monitoring tools affect tracking, not deployment.

3. Final Answer:

   The model registry is not linked to the deployment pipeline -> Option B

4. Quick Check:

   Deployment update failure = Missing link to model registry [OK]

Hint: Check if deployment connects to model registry for updates [OK]

Common Mistakes:

• Blaming data pipeline speed for deployment issues
• Assuming UI controls deployment updates
• Confusing monitoring with deployment functionality

5. You want to design a self-service ML platform that allows data scientists to run experiments, register models, deploy them, and monitor performance with minimal manual steps. Which architectural feature best supports this goal?

hard

A. Relying on external tools for monitoring without integration

B. Separating data ingestion and model deployment into isolated manual workflows

C. Using a UI that only displays model metrics without deployment controls

D. Integrating experiment tracking with automated model registration and deployment pipelines

Solution

1. Step 1: Identify the goal of minimal manual steps

   This requires automation and integration between experiment tracking, model registration, and deployment.

2. Step 2: Evaluate architectural options

   Integrating experiment tracking with automated model registration and deployment pipelines integrates these components with automation, supporting the goal. Options B, C, and D involve manual or disconnected steps.

3. Final Answer:

   Integrating experiment tracking with automated model registration and deployment pipelines -> Option D

4. Quick Check:

   Automation and integration = minimal manual steps [OK]

Hint: Automation and integration reduce manual work [OK]

Common Mistakes:

• Choosing isolated manual workflows
• Ignoring deployment controls in UI
• Using disconnected monitoring tools