Multi-tenancy and isolation in MLOps - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is multi-tenancy in MLOps?

Multi-tenancy means multiple users or teams share the same MLOps platform or resources, but their data and models stay separate and secure.

beginner

Why is isolation important in multi-tenant MLOps environments?

Isolation keeps each tenant's data, models, and compute separate to prevent interference, data leaks, and security risks.

intermediate

Name two common methods to achieve isolation in multi-tenant MLOps platforms.

1. Using containers or virtual machines to separate compute environments. 2. Applying strict access controls and namespaces for data and resources.

intermediate

How does resource quota help in multi-tenancy?

Resource quotas limit how much CPU, memory, or storage each tenant can use, preventing one tenant from using all resources and affecting others.

beginner

What is a namespace in the context of multi-tenant MLOps platforms?

A namespace is a way to group and isolate resources like models, data, and jobs for each tenant, so they don’t mix or interfere.

What does multi-tenancy allow in an MLOps platform?

A All users share the same data and models

B Multiple users share the platform but keep data separate

C Only one user can use the platform at a time

D Users cannot run models simultaneously

Multi-tenancy means multiple users share the platform but their data and models remain isolated.

Which method helps isolate compute environments in multi-tenant MLOps?

A Containers or virtual machines

B Sharing a single server without separation

C Using the same user account for all tenants

D Disabling access controls

Containers or virtual machines create separate environments for each tenant to isolate compute resources.

What is the purpose of resource quotas in multi-tenancy?

A Allow unlimited resource use for all tenants

B Share resources equally without limits

C Limit resource use per tenant to prevent overload

D Disable resource monitoring

Resource quotas limit how much each tenant can use to avoid one tenant affecting others.

Which of the following best describes a namespace?

A A network protocol

B A type of machine learning model

C A shared data storage for all tenants

D A group that isolates tenant resources

Namespaces group and isolate resources for each tenant to prevent interference.

Why is isolation critical in multi-tenant MLOps?

A To prevent data leaks and interference

B To allow all tenants to share data freely

C To reduce platform security

D To slow down model training

Isolation protects tenant data and operations from being accessed or affected by others.

Explain what multi-tenancy means in MLOps and why it is useful.

Think about how many teams can work on the same system safely.

Describe how isolation is achieved in multi-tenant MLOps environments.

Consider both technical tools and policies that keep tenants separate.

Practice

1. What is the main purpose of multi-tenancy in MLOps platforms?

easy

A. To speed up model training by using multiple GPUs

B. To store all data in a single shared database without restrictions

C. To allow multiple users to share the same system safely

D. To run only one user's workload at a time

Solution

1. Step 1: Understand multi-tenancy concept

   Multi-tenancy means many users share one system but remain separate and safe.

2. Step 2: Identify the correct purpose

   The goal is to let users share resources without interfering with each other.

3. Final Answer:

   To allow multiple users to share the same system safely -> Option C

4. Quick Check:

   Multi-tenancy = safe shared use [OK]

Hint: Multi-tenancy means safe sharing, not exclusive use [OK]

Common Mistakes:

• Confusing multi-tenancy with faster hardware use
• Thinking all data is mixed without separation
• Believing only one user runs at a time

2. Which configuration snippet correctly isolates tenant data in a Kubernetes namespace?

easy

A. apiVersion: v1
kind: ConfigMap
metadata:
name: tenant-a-config

B. apiVersion: v1
kind: Namespace
metadata:
name: tenant-a

C. apiVersion: v1
kind: Service
metadata:
name: tenant-a-service

D. apiVersion: v1
kind: Pod
metadata:
name: tenant-a-pod

Solution

1. Step 1: Identify resource for tenant isolation

   Kubernetes namespaces isolate resources per tenant.

2. Step 2: Match correct YAML kind

   Namespace kind with tenant name isolates tenant data correctly.

3. Final Answer:

   apiVersion: v1 kind: Namespace metadata: name: tenant-a -> Option B

4. Quick Check:

   Namespace = tenant isolation [OK]

Hint: Namespaces isolate tenants, not pods or services alone [OK]

Common Mistakes:

• Choosing Pod or Service which do not isolate tenants
• Confusing ConfigMap with isolation resource
• Missing correct YAML syntax for namespaces

3. Given this code snippet for tenant isolation in a shared ML platform, what will be the output?

tenants = {"tenant1": {"models": ["modelA"]}, "tenant2": {"models": ["modelB"]}}

for tenant, data in tenants.items():
    print(f"{tenant} has models: {', '.join(data['models'])}")

medium

A. tenant1 has models: modelA
tenant2 has models: modelB

B. tenant1 has models: modelB
tenant2 has models: modelA

C. tenant1 has models:
tenant2 has models:

D. Error: KeyError

Solution

1. Step 1: Understand dictionary structure

   Each tenant key maps to a dict with a 'models' list.

2. Step 2: Loop and print models per tenant

   Loop prints tenant name and joins model names correctly.

3. Final Answer:

   tenant1 has models: modelA tenant2 has models: modelB -> Option A

4. Quick Check:

   Correct tenant-model mapping printed [OK]

Hint: Check keys and values carefully in dict loops [OK]

Common Mistakes:

• Swapping models between tenants
• Printing empty model lists
• Mistyping keys causing KeyError

4. You have this Kubernetes YAML snippet meant to isolate tenant workloads:

apiVersion: v1
kind: Namespace
metadata:
  name: tenant1
---
apiVersion: v1
kind: Pod
metadata:
  name: tenant1-pod
  namespace: tenant2
spec:
  containers:
  - name: app
    image: ml-app:latest

What is the main issue here?

medium

A. Pod is assigned to a different namespace than tenant's namespace

B. Namespace name is invalid

C. Container image name is incorrect

D. Pod spec is missing container ports

Solution

1. Step 1: Check namespace assignment

   Pod metadata namespace is 'tenant2' but tenant namespace defined is 'tenant1'.

2. Step 2: Identify isolation problem

   Pod runs in wrong namespace, breaking tenant isolation.

3. Final Answer:

   Pod is assigned to a different namespace than tenant's namespace -> Option A

4. Quick Check:

   Namespace mismatch breaks isolation [OK]

Hint: Pod namespace must match tenant namespace exactly [OK]

Common Mistakes:

• Ignoring namespace mismatch
• Assuming image name causes error
• Thinking missing ports cause isolation failure

5. In a multi-tenant MLOps platform, you want to ensure that tenant A's models cannot access tenant B's data. Which combination of strategies best achieves this?

hard

A. Run all tenant workloads on the same node without resource limits

B. Store all tenant data in one database and rely on application code to separate access

C. Allow tenants to share the same service account for simplicity

D. Use separate namespaces for each tenant and enforce RBAC policies limiting access

Solution

1. Step 1: Understand isolation requirements

   Tenant data must be separated and access controlled to prevent leaks.

2. Step 2: Identify best isolation methods

   Namespaces isolate resources; RBAC controls who can access what.

3. Step 3: Evaluate options

   Only Use separate namespaces for each tenant and enforce RBAC policies limiting access uses both namespaces and RBAC for strong isolation.

4. Final Answer:

   Use separate namespaces for each tenant and enforce RBAC policies limiting access -> Option D

5. Quick Check:

   Namespaces + RBAC = strong tenant isolation [OK]

Hint: Combine namespaces and RBAC for secure tenant isolation [OK]

Common Mistakes:

• Relying only on application code for data separation
• Sharing service accounts across tenants
• Ignoring resource limits and node sharing risks