Topic 1 Question 29
You support a high-traffic web application with a microservice architecture. The home page of the application displays multiple widgets containing content such as the current weather, stock prices, and news headlines. The main serving thread makes a call to a dedicated microservice for each widget and then lays out the homepage for the user. The microservices occasionally fail; when that happens, the serving thread serves the homepage with some missing content. Users of the application are unhappy if this degraded mode occurs too frequently, but they would rather have some content served instead of no content at all. You want to set a Service Level Objective (SLO) to ensure that the user experience does not degrade too much. What Service Level Indicator (SLI) should you use to measure this?
A quality SLI: the ratio of non-degraded responses to total responses.
An availability SLI: the ratio of healthy microservices to the total number of microservices.
A freshness SLI: the proportion of widgets that have been updated within the last 10 minutes.
A latency SLI: the ratio of microservice calls that complete in under 100 ms to the total number of microservice calls.
ユーザの投票
コメント(17)
Ans: A Quality as an SLI Quality is a helpful SLI for complex services that are designed to fail gracefully by degrading when dependencies are slow or unavailable. The SLI for quality is defined as follows:
The proportion of valid requests served without degradation of service.
👍 33francisco_guerra2021/06/22Ans: B
👍 9Charun2021/06/28- 正解だと思う選択肢: A
https://cloud.google.com/architecture/adopting-slos?hl=en#sli-quality
Quality is a helpful SLI for complex services that are designed to fail gracefully by degrading when dependencies are slow or unavailable. The SLI for quality is defined as follows:
The proportion of valid requests served without degradation of service. For example, a web page might load its main content from one datastore and load ancillary, optional assets from 100 other services and datastores. If one optional service is out of service or too slow, the page can still be rendered without the ancillary elements. By measuring the number of requests that are served a degraded response (that is, a response missing at least one backend service's response), you can report the ratio of requests that were bad. You might even track how many responses to the user were missing a response from a single backend, or were missing responses from multiple backends.
👍 6not_thanos2021/12/17
シャッフルモード