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 2 Question 71 Discussion

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

Your organization wants to implement Site Reliability Engineering (SRE) culture and principles. Recently, a service that you support had a limited outage. A manager on another team asks you to provide a formal explanation of what happened so they can action remediations. What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: A

The correct answer is D. Grant the logging.logWriter and monitoring.metricWriter roles to the Compute Engine service accounts.

According to the Google Cloud documentation, the Compute Engine service account is a Google-managed service account that is automatically created when you enable the Compute Engine API1. This service account is used by default to run your Compute Engine instances and access other Google Cloud services on your behalf1. To ensure that monitoring metrics and logs for the instances are visible in Cloud Logging and Cloud Monitoring, you need to grant the following IAM roles to the Compute Engine service account23:

The logging.logWriter role allows the service account to write log entries to Cloud Logging4.

The monitoring.metricWriter role allows the service account to write custom metrics to Cloud Monitoring5.

These roles grant the minimum permissions that are needed for logging and monitoring, following the principle of least privilege. The other roles are either unnecessary or too broad for this purpose. For example, the logging.editor role grants permissions to create and update logs, log sinks, and log exclusions, which are not required for writing log entries6. The logging.admin role grants permissions to delete logs, log sinks, and log exclusions, which are not required for writing log entries and may pose a security risk if misused. The monitoring.editor role grants permissions to create and update alerting policies, uptime checks, notification channels, dashboards, and groups, which are not required for writing custom metrics.


Service accounts, Service accounts. Setting up Stackdriver Logging for Compute Engine, Setting up Stackdriver Logging for Compute Engine. Setting up Stackdriver Monitoring for Compute Engine, Setting up Stackdriver Monitoring for Compute Engine. Predefined roles, Predefined roles. Predefined roles, Predefined roles. Predefined roles, Predefined roles. [Predefined roles], Predefined roles. [Predefined roles], Predefined roles.

by Pansy at Jun 29, 2024, 06:10 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
Michael
5 months ago
A is too limited, we need to share lessons with the whole team!
upvoted 0 times
...
Ashley
5 months ago
Wait, why not just share it with the manager? Seems odd.
upvoted 0 times
...
Walker
5 months ago
Definitely going with D, everyone should see it!
upvoted 0 times
...
Nan
6 months ago
I think C is too detailed for a simple outage.
upvoted 0 times
...
Dorothy
6 months ago
Option B seems best, transparency is key!
upvoted 0 times
...
Thaddeus
6 months ago
I practiced a similar question, and I think sharing on the document portal is crucial for accountability. But I wonder if we should also have a follow-up meeting to discuss it further.
upvoted 0 times
...
Emerson
6 months ago
I’m a bit confused about whether to include the list of people responsible. It seems like it could lead to blame rather than focusing on solutions.
upvoted 0 times
...
Germaine
6 months ago
I think option B makes the most sense. We need to share lessons learned with everyone, not just one manager. It helps build a culture of learning.
upvoted 0 times
...
Wilda
7 months ago
I remember we discussed the importance of transparency in postmortems. Sharing it on the document portal seems like the right approach, but I'm not sure if it should be public or just for the team.
upvoted 0 times
...
Edwin
7 months ago
I think the SRE principles of blameless postmortems and continuous improvement are really important here. I'll focus on capturing the learnings and action items, and then consider the best way to share that information.
upvoted 0 times
...
Leonie
7 months ago
Hmm, I'm a bit unsure about the right way to handle this. Should I share the postmortem more broadly or keep it limited to the manager who asked?
upvoted 0 times
...
Louvenia
7 months ago
This seems like a straightforward postmortem process, but I'll need to think through the best approach to balance transparency and accountability.
upvoted 0 times
...
Georgeanna
7 months ago
Okay, I've got this. The key is to develop a thorough postmortem that identifies the root causes, resolution, and lessons learned. Then I just need to decide whether to share it privately or more publicly.
upvoted 0 times
...
Terrilyn
7 months ago
Ah, this is a tricky one. I remember learning about the different domains, but I'm drawing a blank right now. Maybe I can eliminate a few of the options and see if that helps me narrow it down.
upvoted 0 times
...
Malcom
7 months ago
This looks straightforward enough. I'll try option C and see if that gives me the expected result of 'sku0000000008675309'.
upvoted 0 times
...
Delsie
12 months ago
I'm all about that transparency life, so I'm going with option B. The more we share, the more we can learn and improve as a team. Plus, it'll make the manager feel extra special.
upvoted 0 times
Lilli
10 months ago
Absolutely, sharing information helps everyone learn and grow together.
upvoted 0 times
...
Son
10 months ago
That's a great idea! Transparency is key in SRE culture.
upvoted 0 times
...
Yoko
11 months ago
Option B: Provide a detailed incident report to the manager, including root cause analysis and steps taken for resolution.
upvoted 0 times
...
...
Emilio
12 months ago
Well, well, well... looks like we've got a real 'Postmortem Picasso' on our hands! I wonder if they'll let us include the blooper reel too?
upvoted 0 times
Meghan
11 months ago
Collaborate with the team to implement preventive measures to avoid similar incidents in the future.
upvoted 0 times
...
Dominic
11 months ago
Include the necessary technical details and root cause analysis in the report.
upvoted 0 times
...
Trinidad
11 months ago
Acknowledge the request and agree to provide a detailed postmortem report.
upvoted 0 times
...
...
Eva
12 months ago
Option A sounds like the safest bet. I don't want to publicly call out individuals or share sensitive information. Sharing the postmortem with the manager is more prudent.
upvoted 0 times
Willis
11 months ago
Option A is definitely the way to go in this situation.
upvoted 0 times
...
Kris
11 months ago
It's important to focus on the facts and learnings from the outage.
upvoted 0 times
...
Cristina
12 months ago
I agree, sharing the postmortem with the manager is the best approach.
upvoted 0 times
...
...
Barbra
1 year ago
I'm leaning towards option D. Putting the details out there, including the responsible parties, will show accountability and ensure proper follow-through on the action items.
upvoted 0 times
...
Stefany
1 year ago
Hmm, I think option B is the way to go. Sharing the postmortem on the engineering portal will promote transparency and help the whole team learn from this incident.
upvoted 0 times
Jesusa
11 months ago
Let's make sure to document everything in the postmortem report.
upvoted 0 times
...
Vesta
11 months ago
It's important for everyone to learn from this incident.
upvoted 0 times
...
Hana
12 months ago
We should definitely promote transparency within the team.
upvoted 0 times
...
Gabriele
12 months ago
I agree, sharing the postmortem on the engineering portal is a good idea.
upvoted 0 times
...
...
Delisa
1 year ago
I disagree. I think we should go with option A and share the postmortem with the manager only. It's more efficient and keeps the information contained within the relevant team.
upvoted 0 times
...
Janna
1 year ago
I agree with Kimberlie. It's important for everyone in the engineering organization to have visibility into what happened and the actions being taken to prevent it in the future.
upvoted 0 times
...
Kimberlie
1 year ago
I think we should choose option B. Sharing the postmortem on the engineering organization's document portal will promote transparency and accountability.
upvoted 0 times
...
Asuncion
1 year ago
I prefer option D. Including the list of people responsible and action items for each person will ensure accountability and ownership of the issues.
upvoted 0 times
...
Phyliss
1 year ago
I agree with Muriel. It's important for everyone in the organization to learn from incidents and work together to prevent future outages.
upvoted 0 times
...
Muriel
1 year ago
I think we should choose option B. Sharing it on the engineering organization's document portal will promote transparency and accountability.
upvoted 0 times
...

Save Cancel