Developing a Google SRE Culture Quiz

🧠 Quiz: Developing a Google SRE Culture (All Weeks)

In many IT organizations, incentives are not aligned between developers, who strive for agility, and operators, who focus on stability. Site reliability engineering, or SRE, is how Google aligns incentives between development and operations and does mission-critical production support. Adoption of SRE cultural and technical practices can help improve collaboration between the business and IT. This course introduces key practices of Google SRE and the important role IT and business leaders play in the success of SRE organizational adoption. Course will be foundo on https://www.skills.google/course_templates/95

Q1. Which philosophy closes the gap between development and operations?

SRE

DevOps

Agile

Waterfall

Q2. How do DevOps and SRE relate?

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 SRE practice promotes sharing ownership in IT?

Monitoring

Design thinking

Error budgets

Blameless postmortems

Q5. One value SRE provides to an IT team:

The business is able to focus primarily on its users.

Team members focus on manual tasks.

Developers spend more time on reliability.

Developers enabled to work at higher velocity while maintaining reliability.

Q6. What are Site Reliability Engineers comfortable with?

Failure

100% reliability

System-wide updates

Unknown outage reasons

Q7. Reasonable target reliability for an SLO?

0%

50%

99.9%

100%

Q8. 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.

Q9. What should your team strive to achieve?

Mission

Vision

Strategy

Purpose

Q10. What is a benefit of CI/CD?

It is less disruptive for customers.

It decreases the need for automation.

It allows large changes rolled out slower.

It allows testing only on production change.

Q11. Best way to practice canarying?

Roll out to 90% users.

Test in non-prod environment.

Deploy to a representative subset of users.

Deploy a big change to any users.

Q12. Why is toil a problem?

It is unbounded.

It is unavoidable.

It is low-risk.

It becomes toxic in large quantities.

Q13. Third phase of design thinking?

Ideate

Define

Empathize

Prototype

Q14. How should you present change to your team?

A threat

A requirement

An inevitability

An opportunity

Q15. SLIs need clear definition of what?

User happiness

Service downtime

Good and bad events

Total interactions

Q16. What does Google use OKRs as?

KPIs

SLIs

SLOs

Feedback loops

Q17. Which bias finds info to support preconce notions?

Affinity bias

Labeling bias

Confirmation bias

Selective attention bias

Q18. What practice does Google recommend before forming first SRE team?

Monitoring

Toil automation

Blameless postmortem culture

CI/CD

Q19. Which team can support jumpstarting your SRE implementation?

Google Cloud SRE team

Google Engineering Services team

Google Cloud Customer Experience team

Google Cloud Professional Services team

Q20. Whose experience determines production availability?

The SRE’s

The customer’s

The developer’s

The operator’s

Q21. What describes breaking down silos between dev & ops?

Agile

DevOps

Monitoring

Site Reliability Engineering

Q22. Whose experience ultimately determines production availability?

The SRE’s

The customer’s

The developer’s

The operator’s

Q23. What does error budgeting enable teams to do?

Eliminate all outages

Focus only on reliability

Stop feature development

Balance innovation and reliability

Q24. What is the primary purpose of a blameless postmortem?

Learn from failure

Assign responsibility

Document outages

Reduce on-call load

Q25. What is toil?

Creative engineering work

Strategic planning

Manual, repetitive operational work

Incident response leadership

Q26. What is the main benefit of automation in SRE?

More manual control

Reduction of toil

Increased outages

Reduced testing

Q27. What should SLOs be based on?

Internal team goals

Management expectations

User experience

Infrastructure limits

Q28. What happens when error budgets are exhausted?

Feature releases slow or stop

Reliability targets increase

More outages are allowed

Automation stops

Q29. Which practice helps teams learn without fear of punishment?

Root cause analysis

Incident escalation

Performance reviews

Blameless postmortems

Q30. What culture is essential for a successful SRE team?

Competitive culture

Psychological safety

Hierarchical control

Strict supervision

Tags: #DevelopingAGoogleSRECulture, #GoogleSRE, #CourseraQuizAnswers, #SRECultureQuiz, #SiteReliabilityEngineering, #DevOpsAndSRE, #SREErrorBudget, #SRESLOSLI, #BlamelessPostmortem, #SREToilAutomation, #CourseraSRE, #GoogleSRECourse, #SREFinalAssessment, #DevOpsQuizAnswers #DevOpsandSREQuiz