Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Google Professional Cloud DevOps Engineer Exam - Topic 12 Question 50 Discussion

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?
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.
A) Buckelize Ihe 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.
D) Count the number of home page requests that load in under 100 ms. and then divide by the total number of all web application requests.

Google Professional Cloud DevOps Engineer Exam - Topic 12 Question 50 Discussion

Actual exam question for Google's Professional Cloud DevOps Engineer exam
Question #: 50
Topic #: 12
[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?

Show Suggested Answer Hide Answer
Suggested Answer: C

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)


Contribute your Thoughts:

0/2000 characters
Jenise
7 months ago
Bucketing latencies is good, but I prefer the median approach.
upvoted 0 times
...
Mitsue
7 months ago
Totally agree with C! It's straightforward and clear.
upvoted 0 times
...
Herman
7 months ago
Wait, are we really counting all requests for D? Seems off.
upvoted 0 times
...
Dominic
8 months ago
I think B makes more sense for a detailed analysis.
upvoted 0 times
...
Jackie
8 months ago
Option C is the way to go! Simple and effective.
upvoted 0 times
...
Thaddeus
8 months ago
Counting requests under 100 ms sounds right, but I wonder if we should only focus on the home page or all requests.
upvoted 0 times
...
Sue
8 months ago
I feel like the median and percentiles are important, but I can't recall if they relate to the SLI calculation directly.
upvoted 0 times
...
Emmanuel
8 months ago
I remember practicing a similar question where we had to calculate SLIs, and I think bucketizing latencies was involved.
upvoted 0 times
...
Ruth
8 months ago
I think we should count the requests that load under 100 ms, but I'm not sure if it's option C or D.
upvoted 0 times
...
Ariel
8 months ago
Easy peasy, the answer is A - a Subscription. That's the top-level Azure resource that all your other services and resources have to be associated with. I'm feeling pretty confident about this one.
upvoted 0 times
...
Carol
8 months ago
This looks like a straightforward data extension setup question. I think the key is to identify the primary key and make sure the data extension is sendable.
upvoted 0 times
...
Kayleigh
8 months ago
This looks like a pretty straightforward question. I think the key is to create a new domain that only contains the NetWare servers I manage, and then use that domain in the Management Console. Option C seems to be the best approach.
upvoted 0 times
...

Save Cancel