Performance metric tracking in MLOps - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to log a metric named 'accuracy' with value 0.95 using MLflow.

MLOps

mlflow.log_metric('[1]', 0.95)

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

Aloss

Baccuracy

Cprecision

Drecall

Attempts:

3 left

💡 Hint

Common Mistakes

Using a wrong metric name like 'loss' or 'precision'.

The metric name should be 'accuracy' to correctly log the accuracy value.

2fill in blank

medium

Complete the code to start an MLflow run before logging metrics.

MLOps

with mlflow.[1]():
    mlflow.log_metric('accuracy', 0.95)

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

Astart_run

Brun_start

Cbegin_run

Dopen_run

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect method names like 'run_start' or 'begin_run'.

The correct method to start an MLflow run is start_run().

3fill in blank

hard

Fix the error in the code to log the metric 'loss' with value 0.1 inside an MLflow run.

MLOps

with mlflow.start_run():
    mlflow.log_metric('loss', [1])

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

A0.1

B'0.1'

Closs

DNone

Attempts:

3 left

💡 Hint

Common Mistakes

Putting the number in quotes, which makes it a string.

The metric value should be a number, so use 0.1 without quotes.

4fill in blank

hard

Fill both blanks to create a dictionary comprehension that tracks metrics only if their value is greater than 0.5.

MLOps

metrics = {k: v for k, v in all_metrics.items() if v [1] [2]

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

A>

B0.5

C<

D1.0

Attempts:

3 left

💡 Hint

Common Mistakes

Using '<' instead of '>' or wrong threshold values.

The condition should check if the metric value is greater than 0.5 using v > 0.5.

5fill in blank

hard

Fill all three blanks to create a filtered dictionary of metrics where keys are uppercase and values are above 0.7.

MLOps

filtered_metrics = [1]: v for k, v in metrics.items() if v [2] [3]

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

Ak.upper()

B>

C0.7

Dk.lower()

Attempts:

3 left

💡 Hint

Common Mistakes

Using lowercase keys or wrong comparison operators.

The keys are converted to uppercase with k.upper(), and values filtered with v > 0.7.

Practice

1.

What is the main purpose of performance metric tracking in MLOps?

easy

A. To manage user access to the model

B. To store raw training data

C. To measure how well a machine learning model performs

D. To create new machine learning models automatically

Solution

1. Step 1: Understand the role of performance metrics

   Performance metrics are used to evaluate the quality and effectiveness of a machine learning model.

2. Step 2: Identify the main goal of tracking these metrics

   Tracking helps to see how well the model works over time and in different conditions.

3. Final Answer:

   To measure how well a machine learning model performs -> Option C

4. Quick Check:

   Performance metric tracking = measure model quality [OK]

Hint: Metrics track model quality, not data or access [OK]

Common Mistakes:

• Confusing metrics with data storage
• Thinking metrics create models
• Mixing metrics with user management

2.

Which of the following is the correct way to log a metric named accuracy with value 0.95 using a typical MLOps tracking tool?

easy

A. log_metric(name="accuracy", value=0.95)

B. log_metric(accuracy=0.95)

C. log_metric("accuracy", "0.95")

D. log_metric(value=0.95)

Solution

1. Step 1: Identify required parameters for logging

   Logging a metric usually requires a name and a numeric value.

2. Step 2: Check syntax correctness

   log_metric(name="accuracy", value=0.95) uses named parameters with correct types: name as string and value as number.

3. Final Answer:

   log_metric(name="accuracy", value=0.95) -> Option A

4. Quick Check:

   Correct syntax needs name and numeric value [OK]

Hint: Always provide metric name and numeric value explicitly [OK]

Common Mistakes:

• Passing metric name as a keyword argument
• Using string instead of numeric value
• Omitting the metric name

3.

Given the following code snippet for metric logging, what will be the output or effect?

metrics = {}

# Log accuracy at step 1
metrics[1] = 0.85

# Log accuracy at step 2
metrics[2] = 0.90

print(metrics[2])

medium

A. 0.85

B. 0.90

C. KeyError

D. None

Solution

1. Step 1: Understand the dictionary assignments

   metrics[1] is set to 0.85, metrics[2] is set to 0.90.

2. Step 2: Identify the printed value

   print(metrics[2]) outputs the value stored at key 2, which is 0.90.

3. Final Answer:

   0.90 -> Option B

4. Quick Check:

   metrics[2] = 0.90 so print outputs 0.90 [OK]

Hint: Print the value at the requested key in the dictionary [OK]

Common Mistakes:

• Confusing keys 1 and 2
• Expecting error due to missing key
• Assuming default None output

4.

Identify the error in this metric logging code snippet:

def log_metric(name, value):
    print(f"Metric {name}: {value}")

log_metric("loss")

medium

A. Metric name should be numeric

B. Incorrect function definition syntax

C. Using print instead of return

D. Missing value argument when calling log_metric

Solution

1. Step 1: Check function parameters and call

   The function requires two arguments: name and value.

2. Step 2: Identify the call mistake

   The call provides only one argument ("loss"), missing the value argument.

3. Final Answer:

   Missing value argument when calling log_metric -> Option D

4. Quick Check:

   Function call missing required argument [OK]

Hint: Match function call arguments to definition exactly [OK]

Common Mistakes:

• Ignoring missing arguments
• Thinking print must be replaced
• Assuming metric name can be number

5.

You want to track multiple metrics (accuracy, loss) over training steps and compare models. Which approach best supports this in an MLOps system?

1. Log each metric with its name, value, and step number.
2. Store metrics in a structured format like a table or database.
3. Use the stored metrics to generate comparison reports.

Which option describes the best practice?

hard

A. Log metrics with name, value, and step; store structured; generate reports

B. Log metrics without step info and store as plain text files

C. Only log final metric values after training completes

D. Store metrics randomly without names or steps

Solution

1. Step 1: Understand metric logging needs

   Logging with name, value, and step allows tracking progress over time.

2. Step 2: Importance of structured storage and reporting

   Structured storage enables easy querying and comparison; reports help analyze results.

3. Final Answer:

   Log metrics with name, value, and step; store structured; generate reports -> Option A

4. Quick Check:

   Complete tracking needs structured logging and reporting [OK]

Hint: Include step info and use structured storage for comparisons [OK]

Common Mistakes:

• Ignoring step numbers in logs
• Storing metrics unstructured
• Logging only final values