Welcome to ExamTopics
ExamTopics Logo
- Expert Verified, Online, Free.

Unlimited Access

Get Unlimited Contributor Access to the all ExamTopics Exams!
Take advantage of PDF Files for 1000+ Exams along with community discussions and pass IT Certification Exams Easily.

Exam Professional Cloud DevOps Engineer topic 1 question 8 discussion

Actual exam question from Google's Professional Cloud DevOps Engineer
Question #: 8
Topic #: 1
[All Professional Cloud DevOps Engineer Questions]

You support a high-traffic web application and want to ensure that the home page loads in a timely manner. As a first step, you decide to implement a Service
Level Indicator (SLI) to represent home page request latency with an acceptable page load time set to 100 ms. What is the Google-recommended way of calculating this SLI?

  • A. Bucketize the request latencies into ranges, and then compute the percentile at 100 ms.
  • B. Bucketize the request latencies into ranges, and then compute the median and 90th percentiles.
  • C. Count the number of home page requests that load in under 100 ms, and then divide by the total number of home page requests.
  • D. Count the number of home page request that load in under 100 ms, and then divide by the total number of all web application requests.
Show Suggested Answer Hide Answer
Suggested Answer: C 🗳️
Reference:
https://sre.google/workbook/implementing-slos/

Comments

Chosen Answer:
This is a voting comment (?) , you can switch to a simple comment.
Switch to a voting comment New
Charun
Highly Voted 2 years, 10 months ago
I have submitted C answer
upvoted 17 times
raf2121
2 years, 9 months ago
https://sre.google/workbook/implementing-slos/ In the SRE principles book, it's recommended treating the SLI as the ratio of two numbers: the number of good events divided by the total number of events. For example: Number of successful HTTP requests / total HTTP requests (success rate)
upvoted 8 times
AzureDP900
1 year, 6 months ago
C is right
upvoted 1 times
...
...
...
danchoif2
Highly Voted 2 years, 8 months ago
A, B and D: aren't specific to home page, so they are incorrect. C is correct.
upvoted 9 times
...
Raz0r
Most Recent 4 months, 3 weeks ago
Selected Answer: C
C is the way to go.
upvoted 1 times
...
JonathanSJ
1 year, 4 months ago
Selected Answer: C
Answer C
upvoted 1 times
...
floppino
1 year, 4 months ago
Ans: C 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/
upvoted 1 times
...
GCP72
1 year, 9 months ago
Selected Answer: C
The correct answer is 'C'
upvoted 2 times
...
Alpha121
1 year, 11 months ago
C is the answer
upvoted 1 times
...
alaahakim
2 years, 5 months ago
Ans: C
upvoted 1 times
...
WakandaF
2 years, 10 months ago
B or C?
upvoted 1 times
...
TNT87
2 years, 10 months ago
Ans C https://sre.google/workbook/implementing-slos/
upvoted 6 times
...
francisco_guerra
2 years, 11 months ago
Ans is B After a lot of research i find out this: The SLI for availability indicates whether the service is working. The SLI for availability is defined as follows: The proportion of valid requests served successfully. (good request / total request) The SLI for latency (sometimes called speed) indicates whether the service is fast enough. The proportion of valid requests served faster than a threshold. Latency is commonly measured as a distribution. Given a distribution, you can measure various percentiles. For example, you might measure the number of requests that are slower than the historical 99th percentile. In this case, we consider good events to be events that are faster than this threshold, which was set by examining the historical distribution. You can also set this threshold based on product requirements. You can even set multiple latency SLOs, for example typical latency versus tail latency.
upvoted 4 times
Dark_Lord
2 years, 10 months ago
Still not sure about B
upvoted 1 times
...
francisco_guerra
2 years, 11 months ago
and if this is not enough for you check how google calculate Availability and latency Availability sum(rate(http_requests_total{host="api", status!~"5.."}[7d])) / sum(rate(http_requests_total{host="api"}[7d]) Latency histogram_quantile(0.9, rate(http_request_duration_seconds_bucket[7d])) histogram_quantile(0.99, rate(http_request_duration_seconds_bucket[7d])) https://sre.google/workbook/implementing-slos/ https://cloud.google.com/architecture/adopting-slos/
upvoted 1 times
pddddd
2 years, 3 months ago
The commands shared create a histogram that demonstrates the latency distribution for 90 and 99 % of the requests. Does not define how to measure the SLI.
upvoted 2 times
...
...
Dark_Lord
2 years, 10 months ago
The correct answer is "C", you can confirm it here, https://sre.google/workbook/slo-document/ Latency The proportion of sufficiently fast requests, as measured from the load balancer metrics. “Sufficiently fast” is defined as < 400 ms, or < 850 ms. count of "api" http_requests with a duration less than or equal to "0.4" seconds divided by count of all "api" http_requests
upvoted 3 times
...
...
akg001
2 years, 11 months ago
Answer -C SLI = good events/valid events X 100
upvoted 4 times
...
akg001
2 years, 11 months ago
Answer -C SLI = good events/good events X 100
upvoted 4 times
...
devopsbatch
2 years, 11 months ago
answer C
upvoted 5 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...