Exam Professional Cloud DevOps Engineer topic 1 question 29 discussion

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. https://cloud.google.com/architecture/adopting-slos

Ans: B

Option A

A. A quality SLI: the ratio of non-degraded responses to total responses. Explanation: An SLI (Service Level Indicator) is a metric that is used to measure the performance of a service against a specific SLO (Service Level Objective). To measure the user experience of the web application, which is the main concern in this scenario, the most appropriate SLI would be a quality SLI: the ratio of non-degraded responses to total responses. This will give you a clear indication of how often users are experiencing a degraded mode of the web application, and it will allow you to set a specific SLO for the percentage of non-degraded responses that you want to achieve. An availability SLI (Option B) would measure the availability of the microservices, not the user experience of the web application. A freshness SLI (Option C) would measure the freshness of the content, not the user experience of the web application. A latency SLI (Option D) would measure the speed of the microservices, not the user experience of the web application.

Ans: A Exam passed and taken on 19/12/2022, 50/50 from this dump without buying the full access and looking for 'devops' word here: https://www.examtopics.com/discussions/google/1/

Confusion between ET and user answers. How should I know which answer is correct? Anyone can address this?

Answer A is looks correct for me

I think D is the correct

based on the comments of "to ensure that the user experience does not degrade too much" , A is OK. The SLI for quality is defined as follows: The proportion of valid requests served without degradation of service. https://cloud.google.com/architecture/adopting-slos#sli-quality

Submitted A

I think B.

A - Quality SLI: Number of correct pages / Total number of pages served.

https://cloud.google.com/architecture/adopting-slos#sli-quality

Answer A - Quality as an SLI suits well for degrading dependencies

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.

Ans : B

Ans is A https://sre.google/workbook/implementing-slos/ Request-driven: Quality If the service degrades gracefully when overloaded or when backends are unavailable, you need to measure the proportion of responses that were served in an undegraded state. For example, if the User Data store is unavailable, the game is still playable but uses generic imagery.