ExamTopics Logo
Mail Us[email protected]
Menu
Google Discussions
exam questions

Exam Professional Cloud DevOps Engineer All Questions

View all questions & answers for the Professional Cloud DevOps Engineer exam
Go to Exam

Exam Professional Cloud DevOps Engineer topic 1 question 40 discussion

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

Your company follows Site Reliability Engineering principles. You are writing a postmortem for an incident, triggered by a software change, that severely affected users. You want to prevent severe incidents from happening in the future. What should you do?

  • A. Identify engineers responsible for the incident and escalate to their senior management.
  • B. Ensure that test cases that catch errors of this type are run successfully before new software releases.
  • C. Follow up with the employees who reviewed the changes and prescribe practices they should follow in the future.
  • D. Design a policy that will require on-call teams to immediately call engineers and management to discuss a plan of action if an incident occurs.
Show Suggested Answer Hide Answer
Suggested Answer: B 🗳️
by devopsbatch at June 2, 2021, 8:33 p.m.

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Submit Cancel
Charun
Highly Voted 3 years, 4 months ago
B is correct
upvoted 26 times
looseboy
3 years, 2 months ago
Agree with B. I find this answer in "Site Reliability Engineering: How Google Runs Production Systems".
upvoted 7 times
...
...
devopsbatch
Highly Voted 3 years, 4 months ago
B make automation better
upvoted 10 times
akg001
3 years, 4 months ago
Agree with you. IMO - B is the correct answer.
upvoted 7 times
...
...
thewalker
Most Recent 5 months ago
Selected Answer: B
B. Ensure that test cases that catch errors of this type are run successfully before new software releases. Here's why: Option A focuses on blaming individuals, which is not helpful in a postmortem. The goal is to learn from the incident and prevent future occurrences, not to assign fault. Option C is a good step, but it's not enough. While following up with reviewers is important, the primary focus should be on improving the testing process to catch errors before they reach production. Option D might be helpful in some cases, but it's not a general solution. Not all incidents require immediate escalation, and relying solely on on-call teams to make that decision can lead to unnecessary escalations.
upvoted 1 times
thewalker
5 months ago
Option B addresses the root cause of the incident by ensuring that similar errors are caught during testing. This will help to prevent future incidents and improve the overall reliability of the system. Here are some additional steps you can take to prevent future incidents: Implement a strong continuous integration and continuous delivery (CI/CD) pipeline. This will help to automate the testing process and ensure that new code is tested thoroughly before it is deployed to production. Use a blameless postmortem process. This will encourage engineers to be open and honest about their mistakes, which will help to identify and fix problems more quickly. Invest in training and education for your engineers. This will help them to understand the importance of reliability and how to write code that is less prone to errors. By taking these steps, you can help to prevent future incidents and improve the overall reliability of your system.
upvoted 1 times
thewalker
5 months ago
Additional Considerations It's important to note that there is no single solution that will prevent all incidents. However, by taking a proactive approach and focusing on improving your testing and development processes, you can significantly reduce the risk of future incidents. Here are some additional resources that you may find helpful: Site Reliability Engineering (SRE) Book: https://landing.google.com/sre/book.html Google Cloud Reliability Engineering: https://cloud.google.com/solutions/reliability-engineering Postmortem Best Practices: https://sre.google/sre-book/postmortems/
upvoted 1 times
...
...
...
habla2019pasta
5 months, 2 weeks ago
Selected Answer: B
B - Blameless postmortem
upvoted 1 times
...
alpha_canary
8 months, 4 weeks ago
Selected Answer: B
The focus should be on improving processes and systems, not blaming individuals.
upvoted 1 times
...
jomonkp
11 months ago
Selected Answer: B
Option B
upvoted 1 times
...
JonathanSJ
1 year, 9 months ago
Selected Answer: B
B. Ensuring that test cases that catch errors of this type are run successfully before new software releases will help to prevent similar incidents from happening in the future.
upvoted 1 times
...
Greg123123
1 year, 10 months ago
It is B. The main point here is "trigged by software change". This make B make sense and right to the point. D is not correct because it doesn't prevent this from happen again...
upvoted 1 times
...
floppino
1 year, 10 months ago
Selected Answer: B
Ans: B 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
2 years, 3 months ago
Selected Answer: B
Answer is B
upvoted 2 times
...
devOpsForFun
2 years, 6 months ago
Selected Answer: D
D is correct. B is too narrow
upvoted 2 times
...
PhilipKoku
2 years, 8 months ago
Selected Answer: B
B - Blameless port-mortens. Focus on the process and not in the people.
upvoted 3 times
...
cyrus86
2 years, 9 months ago
I will go with C here
upvoted 1 times
...
meetplanet
2 years, 10 months ago
I go for D based on the on-call doc
upvoted 1 times
...
Vallal
2 years, 10 months ago
c is the correct answer
upvoted 4 times
...
muk5658
2 years, 11 months ago
I would go with B as they are saying incident is triggered by a software change, if this has been tested thoroughly it would have been avoided.
upvoted 2 times
...
MF2C
3 years, 1 month ago
B is better over D because D is incident management, B is RCA.
upvoted 2 times
...
Load full discussion...
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
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago