Congratulations! You passed!
1.
What are some characteristics of SLIs? Select all that apply (2 correct responses).
That’s correct! SLIs are quantitative measurements or metrics of a user experience and are best expressed as a proportion of all valid events that were good. For example, an SLI could be the proportion of HTTP requests that were served successfully.
That’s correct! SLIs are quantitative measurements or metrics of a user experience and are best expressed as a proportion of all valid events that were good. For example, an SLI could be the proportion of HTTP requests that were served successfully.
2.
Which of these is an example of an SLI?
Yes, that’s correct. Remember that SLIs are a measure of all good events divided by all valid events, while SLOs have reliability targets measured by SLIs.
3.
One commonly used signifier of success or failure is the status code of an HTTP or RPC response. How can this be problematic?
This is somewhat plausible. I mean, who can really say whether a "418 I'm a teapot" response is good or bad? But most services will only return a small subset of the available status codes, and at least for HTTP they are already grouped into different classes of success or failure.
4.
Which of these scenarios would a quality SLI be appropriate for? Select all that apply (2 correct responses).
Correct! Though the user is getting a response, as the subset of data searched gets smaller there's a larger chance that the result they were looking for is in the unsearched remainder. Not serving a user the result they want is bad for their experience, but we can only estimate the impact of this based on the size of the unsearched set.
That's right! The user is still getting a response, but they are not seeing up-to-date data, which may degrade the quality of their experience when using the service.
Nenhum comentário:
Postar um comentário