SLOs and SLAs

 

Congratulations! You passed!

Grade received 80%

To pass 80% or higher

1.

Question 1

What are some characteristics of SLAs? Select all that apply (2 correct responses).

0 / 1 point

SLAs are the dividing line between happy and unhappy users.

This should not be selected

No, SLOs are a better dividing line for user happiness. You can still be meeting your SLA and have unhappy users.

SLAs do not need a consequence if violated.

SLAs must have a consequence if violated.

SLAs are internal team goals for your service.

SLAs are agreements with your customers about the reliability of your service.

Correct

Yes, SLAs are external promises to customers and must come with consequences.

2.

Question 2

What are some characteristics of SLOs? Select all that apply (2 correct responses)

1 / 1 point

SLOs should be stronger than your SLAs to catch issues before they violate customer expectation.

Correct

That’s right. SLOs should be stronger than your SLAs so you can catch issues before they violate customer expectation. Otherwise, you risk running a very expensive service if you're constantly compensating your customers for missing your SLA.

SLOs are external promises to your customers.

SLOs must have monetary consequences if violated.

SLOs are internal promises to meet customer expectations.

Correct

That’s right. SLOs are internal promises (as opposed to being explicitly shared with customers), and they are directly tied to customer expectations.

3.

Question 3

A startup just suffered a major outage and wants to change its ways. What are some possible ways it can reduce risks to its service? Select all that apply.

1 / 1 point

Doing fewer pushes

Correct

That’s correct. These are some possible practices that can reduce risk to your service.

Lowering their SLO target

Focus on automation efforts

Correct

That’s correct. These are some possible practices that can reduce risk to your service.

Slowing down the rate of change to the system

Correct

That’s correct. These are some possible practices that can reduce risk to your service.

4.

Question 4

In regards to SLOs, what is The Happiness Test?

1 / 1 point

When your service “meets target SLO” that means “happy leadership”. If it misses the target SLO that means “sad leadership”.

When your service “meets target SLO” that means “happy developers”. If it misses the target SLO that means “sad developers”.

When your service “meets target SLO” that means “happy customers”. If it misses the target SLO that means “sad customers”.

When your service “meets target SLO” that means “happy SREs”. If it misses the target SLO that means “sad SREs”.

Correct

Yes, that’s correct. The Happiness Test states that "Services need target SLOs that capture the performance and availability levels that, if barely met, would keep the typical customer happy."

5.

Question 5

True or false, your service should only have one SLO for a specific reliability measurement like latency.

1 / 1 point

True

False

Correct

Great job! There are many edge cases with SLOs that you should be aware of and you might want to set one or more targets to cover these edge cases. For example, it's common to set one latency target for the median user and one for the long tail.