Platform observability and SLAs in MLOps - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Service Level Agreements (SLAs)

Which statement best describes the purpose of an SLA in platform observability?

A An SLA defines the expected uptime and performance targets agreed upon between service provider and user.

B An SLA is a tool used to monitor the internal logs of a platform without user involvement.

C An SLA is a software that automatically fixes bugs in the platform code.

D An SLA is a backup system that stores data in case of platform failure.

💡 Hint

Think about what agreements between users and providers usually include.

SLAs set clear expectations for uptime and performance, helping both parties understand service quality.

💻 Command Output

intermediate

Interpreting Observability Metrics Output

Given the following Prometheus query output for error rate over 5 minutes, what is the error rate percentage?

error_rate{service="ml-model"} 0.02

A 2%

B 0.2%

C 20%

D 0.02%

💡 Hint

Remember to convert decimal to percentage by multiplying by 100.

The value 0.02 means 2% error rate because 0.02 * 100 = 2%.

🔀 Workflow

advanced

Setting Up Alerting for SLA Breach

Which sequence of steps correctly sets up an alert in a monitoring system when the platform's uptime falls below 99.9%?

A 1,3,2,4

B 2,1,3,4

C 1,2,3,4

D 3,1,2,4

💡 Hint

Think about logical order: metric first, then alert, then notification, then test.

You must first define what to monitor, then create alert rules, set notifications, and finally test.

❓ Troubleshoot

advanced

Diagnosing Missing Observability Data

You notice that your observability dashboard shows no data for the last hour. Which is the most likely cause?

A The platform uptime is 100%, so no data is needed.

B The SLA agreement expired and disabled monitoring.

C The notification system is down, so data is not displayed.

D The data collection agent crashed or stopped running.

💡 Hint

Consider what collects and sends data to the dashboard.

If the data collection agent stops, no new data reaches the dashboard, causing missing data.

✅ Best Practice

expert

Choosing Metrics for SLA Compliance Monitoring

Which metric is the best choice to monitor to ensure compliance with a 99.9% uptime SLA for an ML platform?

A Average response time of the ML model predictions.

B Percentage of successful requests over total requests in a time window.

C CPU usage percentage of the ML model server.

D Total number of requests processed per minute.

💡 Hint

Think about what directly reflects availability and success rate.

Percentage of successful requests directly measures uptime and availability, matching SLA goals.

Practice

1. What is the main purpose of platform observability in MLOps?

easy

A. To monitor and understand system performance in real time

B. To set legal contracts with users

C. To deploy machine learning models automatically

D. To store large amounts of data efficiently

Solution

1. Step 1: Understand observability concept

   Observability means seeing how the system behaves and performs live.

2. Step 2: Match purpose with options

   Only To monitor and understand system performance in real time talks about monitoring and understanding performance in real time.

3. Final Answer:

   To monitor and understand system performance in real time -> Option A

4. Quick Check:

   Observability = Real-time performance monitoring [OK]

Hint: Observability = watching system health live [OK]

Common Mistakes:

• Confusing observability with deployment
• Thinking observability sets contracts
• Mixing observability with data storage

2. Which of the following is the correct way to define an SLA uptime of 99.9% in a YAML configuration?

easy

A. sla:
uptime: '99.9%'

B. sla:
uptime: 99.9

C. sla:
uptime: 0.999

D. sla:
uptime: '99,9%'

Solution

1. Step 1: Understand SLA uptime format

   SLA uptime is usually expressed as a percentage string like '99.9%'.

2. Step 2: Check YAML syntax and value correctness

   sla: uptime: '99.9%' uses correct YAML syntax and proper string format with percent sign.

3. Final Answer:

   sla:\n uptime: '99.9%' -> Option A

4. Quick Check:

   Correct SLA uptime format = '99.9%' string [OK]

Hint: Use string with percent sign for SLA uptime [OK]

Common Mistakes:

• Using number without percent sign
• Using decimal instead of percentage
• Using comma instead of dot in percentage

3. Given this monitoring alert rule snippet:

if error_rate > 0.05:
  alert('High error rate')
else:
  alert('Error rate normal')

What will be the alert message if error_rate is 0.03?

medium

A. No alert

B. High error rate

C. Error rate normal

D. Syntax error

Solution

1. Step 1: Evaluate the condition with error_rate = 0.03

   0.03 is less than 0.05, so the condition error_rate > 0.05 is false.

2. Step 2: Determine which alert triggers

   Since condition is false, the else branch runs, triggering alert('Error rate normal').

3. Final Answer:

   Error rate normal -> Option C

4. Quick Check:

   0.03 < 0.05 triggers else alert [OK]

Hint: Check if error_rate exceeds threshold [OK]

Common Mistakes:

• Confusing greater than with less than
• Assuming no alert triggers
• Thinking code has syntax error

4. You have this SLA configuration:

sla:
  uptime: '99.95%'
  response_time_ms: 200

But your monitoring shows frequent alerts for response time exceeding 200ms. What is the most likely cause?

medium

A. The uptime percentage is incorrect

B. The SLA response_time_ms is set too low for actual system performance

C. The SLA syntax is invalid YAML

D. The monitoring tool is not running

Solution

1. Step 1: Analyze SLA and alert mismatch

   The SLA sets response_time_ms to 200ms, but alerts show it often exceeds this.

2. Step 2: Identify cause of frequent alerts

   This means the system often responds slower than 200ms, so SLA is too strict or system needs improvement.

3. Final Answer:

   The SLA response_time_ms is set too low for actual system performance -> Option B

4. Quick Check:

   Strict SLA causes frequent alerts [OK]

Hint: Check if SLA limits match real system speed [OK]

Common Mistakes:

• Blaming uptime for response time alerts
• Assuming YAML syntax error without checking
• Ignoring monitoring tool status

5. You want to combine observability metrics and SLA checks to alert only when uptime drops below 99.9% and error rate exceeds 1%. Which pseudo-code correctly implements this?

hard

A. if uptime >= 99.9 and error_rate >= 0.01:
alert('SLA breach')

B. if uptime > 99.9 or error_rate < 0.01:
alert('SLA breach')

C. if uptime <= 99.9 and error_rate <= 0.01:
alert('SLA breach')

D. if uptime < 99.9 and error_rate > 0.01:
alert('SLA breach')

Solution

1. Step 1: Understand SLA breach conditions

   SLA breach means uptime is less than 99.9% AND error rate is greater than 1% (0.01).

2. Step 2: Match condition logic with options

   if uptime < 99.9 and error_rate > 0.01: alert('SLA breach') uses < for uptime and > for error rate combined with AND, matching the requirement exactly.

3. Final Answer:

   if uptime < 99.9 and error_rate > 0.01:\n alert('SLA breach') -> Option D

4. Quick Check:

   Use AND with correct inequalities for SLA breach [OK]

Hint: Use AND with uptime < 99.9 and error_rate > 0.01 [OK]

Common Mistakes:

• Using OR instead of AND
• Reversing inequality signs
• Alerting on normal conditions