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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Google Professional Cloud DevOps Engineer Exam - Topic 10 Question 31 Discussion

You support a large service with a well-defined Service Level Objective (SLO). The development team deploys new releases of the service multiple times a week. If a major incident causes the service to miss its SLO, you want the development team to shift its focus from working on features to improving service reliability. What should you do before a major incident occurs?
B) Negotiate with the product team to always prioritize service reliability over releasing new features.
A) Develop an appropriate error budget policy in cooperation with all service stakeholders.
C) Negotiate with the development team to reduce the release frequency to no more than once a week.
D) Add a plugin to your Jenkins pipeline that prevents new releases whenever your service is out of SLO.

Google Professional Cloud DevOps Engineer Exam - Topic 10 Question 31 Discussion

Actual exam question for Google's Professional Cloud DevOps Engineer exam
Question #: 31
Topic #: 10
[All Professional Cloud DevOps Engineer Questions]

You support a large service with a well-defined Service Level Objective (SLO). The development team deploys new releases of the service multiple times a week. If a major incident causes the service to miss its SLO, you want the development team to shift its focus from working on features to improving service reliability. What should you do before a major incident occurs?

Show Suggested Answer Hide Answer
Suggested Answer: B

by Judy at May 04, 2022, 03:59 PM

Limited Time Offer

25%

Off

Get Premium Professional Cloud DevOps Engineer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Raylene
7 months ago
B is a bit too rigid; we need balance, not just reliability.
upvoted 0 times
...
Lavera
7 months ago
Wait, can we really enforce that in Jenkins? Sounds tricky.
upvoted 0 times
...
Ashton
8 months ago
But what about all the new features we need?
upvoted 0 times
...
Corinne
8 months ago
Totally agree, prioritizing reliability is a must.
upvoted 0 times
...
Rozella
8 months ago
A solid error budget policy is key!
upvoted 0 times
...
Timothy
8 months ago
Adding a Jenkins plugin sounds like a good idea, but I wonder if it might slow down our development process too much.
upvoted 0 times
...
Laurel
8 months ago
Reducing release frequency seems too drastic. I think we should focus on improving reliability without limiting our deployment cadence.
upvoted 0 times
...
Malcolm
8 months ago
I'm not entirely sure, but I feel like negotiating with the product team might lead to conflicts. We need to balance features and reliability.
upvoted 0 times
...
Buddy
8 months ago
I remember discussing error budgets in class, and I think developing a policy with stakeholders is crucial. It sets clear expectations.
upvoted 0 times
...
Aja
8 months ago
Okay, I think I've got it. The question is asking about how the IAA can describe its work, and since the external assessment was recent and the quality assurance program is favorable, option B seems to be the most accurate statement.
upvoted 0 times
...
Launa
8 months ago
This is straightforward - the security requirement means we need to use a Lookup relationship, not Master Detail. Lookup gives the access control we need.
upvoted 0 times
...

Save Cancel