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

PeopleCert Exam DevOps-SRE Topic 8 Question 40 Discussion

Actual exam question for PeopleCert's DevOps-SRE exam
Question #: 40
Topic #: 8
[All DevOps-SRE Questions]

Which of the following BEST describes the most important rationale for NOT seeking an SLO of 100% availability?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Ocie
15 days ago
A 100% availability target? Good luck with that! I'd like to see the engineer who can code a service that never, ever goes down. Maybe they can also make a car that never needs gas and a toaster that never burns the bread.
upvoted 0 times
...
Bette
18 days ago
Wait, user satisfaction is affected by 'a tow percent'? I'm not sure what that means, but it doesn't sound very convincing. I'll stick with A.
upvoted 0 times
...
Hyman
22 days ago
I like C. Leaving room for improvement is crucial. If you hit 100% right away, where do you go from there? You need some wiggle room to keep getting better.
upvoted 0 times
...
Avery
23 days ago
Option B makes sense to me. If you set the bar so high, you're almost guaranteed to fail. That's not a great way to run a service. Realistic targets are key.
upvoted 0 times
...
Katie
1 months ago
A 100% availability target is simply not realistic. As the question states, the complexity and scale of modern services make that an unachievable goal. I'll go with A on this one.
upvoted 0 times
...
Delbert
2 months ago
B) The likely results is failure where such targets are defined.
upvoted 0 times
...
Tamar
2 months ago
C) There is no room for improvements if targets are so high.
upvoted 0 times
...
Annabelle
2 months ago
A) It is not realistic for the complexity and scale of services.
upvoted 0 times
...

Save Cancel