Table of Contents
Developing a Google SRE Culture Week 1 Quiz Answers
DevOps and SRE Quiz Answers
Q1. Which philosophy closes the gap between development and operations?
Q2. How do DevOps and SRE relate to each other?
- DevOps is a way to implement SRE.
- SRE is a way to implement DevOps.
- SRE and DevOps originated together.
- DevOps developed in response to SRE practice.
Q3. Which is a key pillar of DevOps philosophy?
- Share ownership.
- Accept failure as normal.
- Reduce the cost of failure.
- Implement blameless postmortems.
Q4. Which is an SRE practice that promotes sharing ownership in IT?
- Design thinking
- Error budgets
- Blameless postmortems
Module 3 Quiz Answers
Q1. What is one value SRE provides to an IT team?
- The business is able to focus primarily on its users.
- Team members gain time to focus on the more manual tasks.
- Developers are able to spend more time focusing on system reliability.
- Developers are enabled to work at a higher velocity while maintaining reliability.
Q2. What are Site Reliability Engineers comfortable with?
- 100% reliability
- System-wide updates
- Unknown outage reasons
Q3. What is a reasonable degree of target reliability for an SLO?
Q4. What can happen when team members don’t feel psychologically safe?
- Innovation increases.
- Moments of learning are lost.
- More people express dissatisfaction.
- Fewer people are punished for mistakes.
Q5. What is your team’s clear and compelling goal that it strives to achieve?
Developing a Google SRE Culture Week 2 Quiz Answers
Module 4: Quiz Answers
Q1. What is a benefit of continuous integration and continuous delivery (CI/CD)?
- It is less disruptive for customers.
- It decreases the need for automation.
- It allows large changes to be rolled out slower.
- It allows for testing of only the production change.
Q2. What would be the best way to practice canarying?
- Roll out a feature change to 90% of users.
- Test the code change in a different environment than production.
- Deploy a small feature change to users that are a representative subset of your typical customers.
- Deploy a significant code change to any type of user.
Q3. Why is toil a problem?
- It is unbounded.
- It is unavoidable.
- It is low-risk and low-stress.
- It becomes toxic in large quantities.
Q4. Which is the third phase of design thinking?
Q5. What should you present change to your team members as?
- A threat
- A requirement
- An inevitability
- An opportunity
Module 5 Quiz Answers
Q1. SLIs need to provide a clear definition of what?
- User happiness
- Service downtime
- Good and bad events
- Total user interactions
Q2. What does monitoring allow for?
- SLI measurement
- Improved security
- Visibility into a system
- Reporting on outage causes
Q3. What does Google use OKRs as?
- Feedback loops
Q4. Which bias is the tendency to find information, input, or data that supports your preconceived notions?
- Affinity bias
- Labeling bias
- Confirmation bias
- Selective attention bias
Module 6 Quiz Answers
Q1. What practice does Google recommend that you establish before forming your first SRE team?
- Toil automation
- Blameless postmortem culture
- Continuous integration/continuous delivery
Q2. Which type of IT role does Google recommend as a possible new SRE hire?
- Sales engineer
- Systems analyst
- Systems architect
- Systems administrator
Q3. Scope is generally unbounded for which type of SRE implementation?
- Kitchen Sink
Q4. Which Google team can support you in jumpstarting your SRE implementation?
- Google Cloud SRE team
- Google Engineering Services team
- Google Cloud Customer Experience team
- Google Cloud Professional Services team
Developing a Google SRE Culture Week 3 Quiz Answers
Final Assessment Quiz Answers
Q1. Generally, whose experience with a production service determines its availability?
- The SRE’s
- The customer’s
- The developer’s
- The operator’s
Q2. Which is the term that describes breaking down the silos and closing gaps between development and operations teams?
- Site Reliability Engineering
Q3. Which DevOps pillar led to Google SRE practices, such as SLOs and error budgets, that promote shared
ownership between developers and SREs?
- Accept failure as normal
- Implement gradual change
- Reduce organizational silos
- Leverage tooling and automation
Q4. Your developers have felt inundated with too many manual and repetitive tasks that are tied to the production service. What is this called?
- Discomfort discharge
Q5. What does a blameless postmortem not help with?
- Avoiding multiplying complexity
- Reducing the likelihood of stressful outages
- Decreasing engineering costs incurred after launch
- Ensuring that all the root causes are properly understood by the team
Q6. What can you build with your team by acknowledging your own fallibility as a leader?
- Unified vision
- Psychological safety
- Data-driven decision making
- Service-level indicators (SLIs)
Q7. What is a service-level objective (SLO)?
- A precise numerical target for system reliability.
- The amount of unreliability you are willing to tolerate.
- An indicator of how well your service is doing at any moment in time.
- Code that is built, integrated, and tested within the development environment.
Q8. What often accompanies toil automation that leaders should be prepared for?
- Shared vision
- Blameless culture
- Resistance to change
- Linear scaling of work with complexity
Q9. Your team members are unsure what goals they are trying to achieve within the team. What part of your team vision should you work to clarify?
- The values
- The mission
- The strategy
- Service-oriented meetings
Q10. SREs believe that change is best when what?
- Fast and big
- Frequent and global
- Small and frequent
- Small and dispersed
Q11. What is continuous delivery?
- Minimizing time between build and deployment.
- Deploying to production frequently, or at the rate the business chooses.
- Building, integrating, and testing code within the development environment.
- Deploying a change in service to a group of users who don’t know they are receiving the change.
Q12. What are the five steps in design thinking methodology?
- Empathize, Define, Ideate, Prototype, Test
- Empathize, Define, Design, Prototype, Test
- Empathize, Discuss, Ideate, Prototype, Test
- Define, Ideate, Prototype, Test, Resolve
Q13. Why should toil be limited to a bounded part of the SRE role?
- It helps IT teams decide what to automate.
- It prevents SREs from doing only sysadmin work.
- It frees SREs to completely focus on reliability work.
- It allows SREs to focus on project work without worrying about the team’s SLOs.
Q14. You’ve decided to adopt SRE practices and culture in your company. As change begins to happen, you notice that Naveen, one of your operations managers is avoiding new protocols and continuing with his normal work routine. In which group of people would you categorize Naveen?
Q15. What is one benefit of measuring toil?
- It helps SREs choose SLIs.
- It triggers a reduction effort.
- It reveals error budget burn.
- It allows design thinking.
Q16. What does Google recommend you do with the four golden signals?
- Create SLIs
- Translate data
- Monitor the system
- Automate features
Q17. What do OKRs primarily help an organization do?
- Set goals
- Share feedback
- Overcome biases
Q18. Which phase of the SRE journey includes automating toil?
- Regulate Workload
- Reliability Measurement
- SLOs with Consequences
- Make Tomorrow Better than Today
Q19. SREs are regularly on-call and required to solve problems fast. What is a primary skill SREs need for this?
- Monitoring systems
- System architecting
- Operations and software engineering
Q20. Which type of SRE team implementation does Google recommend for an organization’s first SRE team?
- Kitchen Sink
Get all course Quiz Answers of Preparing for Google Cloud Certification: Cloud DevOps Engineer Professional Certificate
Logging, Monitoring and Observability in Google Cloud Quiz Answers
Getting Started with Google Kubernetes Engine Quiz Answers