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 5 Question 90 Discussion

Your team is writing a postmortem after an incident on your external facing application Your team wants to improve the postmortem policy to include triggers that indicate whether an incident requires a postmortem Based on Site Reliability Engineenng (SRE) practices, what triggers should be defined in the postmortem policy?Choose 2 answers
A) An external stakeholder asks for a postmortem and C) An internal stakeholder requests a postmortem
B) Data is lost due to an incident
D) The monitoring system detects that one of the instances for your application has failed
E) The CD pipeline detects an issue and rolls back a problematic release.

Google Professional Cloud DevOps Engineer Exam - Topic 5 Question 90 Discussion

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

Your team is writing a postmortem after an incident on your external facing application Your team wants to improve the postmortem policy to include triggers that indicate whether an incident requires a postmortem Based on Site Reliability Engineenng (SRE) practices, what triggers should be defined in the postmortem policy?

Choose 2 answers

Show Suggested Answer Hide Answer
Suggested Answer: A, C

The best options for defining triggers that indicate whether an incident requires a postmortem based on Site Reliability Engineering (SRE) practices are an external stakeholder asks for a postmortem and data is lost due to an incident. An external stakeholder is someone who is affected by or has an interest in the service, such as a customer or a partner. If an external stakeholder asks for a postmortem, it means that they are concerned about the impact or root cause of the incident, and they expect an explanation and remediation from the service provider. Therefore, this should trigger a postmortem to address their concerns and improve their satisfaction. Data loss is a serious consequence of an incident that can affect the integrity and reliability of the service. If data is lost due to an incident, it means that there was a failure in the backup or recovery mechanisms, or that there was a corruption or deletion of data. Therefore, this should trigger a postmortem to investigate the cause and impact of the data loss, and to prevent it from happening again.


by Zack at Apr 05, 2025, 11:27 AM

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
Mariko
7 months ago
D seems a bit too minor for a postmortem, don’t you think?
upvoted 0 times
...
Edwin
7 months ago
I think C is just as important as A.
upvoted 0 times
...
My
7 months ago
Definitely A and B! Those are crucial triggers.
upvoted 0 times
...
Nickole
7 months ago
B is a must, but I’m not sold on A being necessary.
upvoted 0 times
...
Denise
7 months ago
Surprised that E isn't a top choice! That’s a big deal!
upvoted 0 times
...
Johanna
8 months ago
The monitoring system detecting a failure seems like a clear trigger too. I practiced a question where we had to identify incident severity based on monitoring alerts.
upvoted 0 times
...
Ashlyn
8 months ago
I’m a bit confused about whether internal requests are as significant as external ones. I feel like both should matter, but I can't recall the specifics.
upvoted 0 times
...
Danica
8 months ago
I think data loss definitely warrants a postmortem, it’s a critical incident. I’ve seen similar questions where data integrity was a key focus.
upvoted 0 times
...
Danica
8 months ago
I remember discussing how external stakeholder requests can be a strong trigger for a postmortem, but I'm not sure if that's the only factor we should consider.
upvoted 0 times
...
Oliva
9 months ago
I feel pretty confident about this question. The SRE practices emphasize learning from incidents, so the triggers should capture the kinds of issues that warrant a deeper dive through a postmortem. Data loss and pipeline rollbacks seem like clear choices.
upvoted 0 times
...
Pamella
9 months ago
This is a good one. I'd say the key is to focus on triggers that indicate a significant incident or disruption to the external-facing application. Things like external stakeholder requests and internal stakeholder requests seem like they'd be good to include.
upvoted 0 times
...
Valentin
9 months ago
Okay, I think I've got this. Based on SRE, we'll want to include triggers like data loss, failed instances, and issues detected by the CD pipeline. Those seem like the kinds of high-impact incidents that would require a deeper analysis through a postmortem.
upvoted 0 times
...
Yolando
9 months ago
Hmm, I'm a bit unsure about this one. I know we want to include triggers based on SRE practices, but I'm not totally clear on what those would be. Maybe I should review some SRE principles before answering.
upvoted 0 times
...
Jenifer
9 months ago
This seems like a straightforward question about defining triggers for a postmortem policy. I think the key is to focus on SRE practices and what kinds of incidents would warrant a postmortem.
upvoted 0 times
...
Hortencia
1 year ago
Ha, I bet the answer is D and E. Gotta love those SRE practices - if the monitoring system and the CD pipeline catch something, you know it's serious business.
upvoted 0 times
Daron
1 year ago
A: True, A and C could definitely help improve our postmortem policy.
upvoted 0 times
...
Alease
1 year ago
B: I think A and C are also important triggers to consider.
upvoted 0 times
...
Yun
1 year ago
A: Definitely agree, D and E are key triggers for a postmortem.
upvoted 0 times
...
...
Latrice
1 year ago
Wait, is this a trick question? I feel like the obvious answers are B and C - data loss and an internal stakeholder request. Who cares what the external stakeholders think, am I right?
upvoted 0 times
...
Chaya
1 year ago
Hmm, I think the triggers should be more about the impact of the incident, not just who requests it. I'd say B and D are the way to go - data loss and failed instances seem like clear reasons to do a postmortem.
upvoted 0 times
Annamae
1 year ago
B: Absolutely, it will help us learn from our mistakes and prevent similar incidents in the future.
upvoted 0 times
...
Bambi
1 year ago
A: We should make sure to include those in our postmortem policy moving forward.
upvoted 0 times
...
Kathrine
1 year ago
B: Yeah, those triggers can help us understand the impact of the incident and improve our processes.
upvoted 0 times
...
Dyan
1 year ago
A: I agree, data loss and failed instances are definitely important triggers for a postmortem.
upvoted 0 times
...
...
Sheridan
1 year ago
I believe E should also be included as a trigger. Rolling back a release due to an issue is a significant event that requires analysis.
upvoted 0 times
...
Novella
1 year ago
I agree with you, Danilo. Data loss and instance failure are critical incidents that should trigger a postmortem.
upvoted 0 times
...
Danilo
1 year ago
I think B and D should be defined as triggers in the postmortem policy.
upvoted 0 times
...

Save Cancel