Following a major outage, an analysis of the outage is conducted. This BEST describes an example of which of the following?
Correct Answer: C
Comprehensive and Detailed Explanation From Exact Extract: Google's SRE approach emphasizes a blameless postmortem culture as a core learning mechanism. After a major outage, SRE teams conduct structured analyses to understand the root causes, contributing factors, and systemic weaknesses. The SRE Book defines this culture explicitly: "Postmortems are written analyses following incidents, designed to capture what happened, why it happened, and how to prevent the issue from recurring." (SRE Book - Chapter: Postmortem Culture). This learning-focused approach reduces blame, increases resilience, and improves future reliability. Option C aligns exactly with this principle. Option A (follow-up culture) is vague and not an SRE term. Option B (major incident culture) refers to incident handling, not learning afterward. Option D (problem culture) is unrelated to SRE's structured post-incident learning. Thus, C is correct. References: Site Reliability Engineering, Chapter: "Postmortem Culture: Learning From Failure." The Site Reliability Workbook, Incident Review processes.
Question 7
If an organization wants to promote changes automatically and reduce dependency errors, what steps should they take?
Correct Answer: B
Comprehensive and Detailed Explanation From Exact Extract: Using verified and signed artifacts is essential for safe automation, ensuring that deployments are consistent and free of dependency or supply chain errors. This is a fundamental principle in Google's release engineering and SRE practices. The Site Reliability Engineering Book, chapter "Release Engineering," states: "Releases should be built once, tested, signed, and stored in a secure repository. Only signed and verified artifacts should be promoted to production to prevent configuration drift and dependency inconsistencies." The SRE Workbook echoes this: "Automated promotions depend on the integrity and immutability of artifacts. Signed artifacts ensure consistency and prevent errors related to mismatched dependencies." Why the other options are incorrect: * A External visibility is irrelevant and may create security risks. * C Error budgets relate to reliability, not artifact promotion. * D SLOs do not define artifact signing; this is handled by release engineering processes. Thus, the correct answer is B. References: Site Reliability Engineering Book, "Release Engineering" SRE Workbook, "Automation and Safe Releases"
Question 8
Which of the following is the BEST description of a customer reliability engineer (CRE)?
Correct Answer: D
Question 9
Which scenario BEST illustrates how stability and agility can be achieved with simplicity?
Correct Answer: B
Comprehensive and Detailed Explanation From Exact Extract: Simplicity is a core SRE design principle. Google states: "Small, frequent, automated changes reduce risk and improve system stability." (SRE Book - Release Engineering). Automating continuous, small deployments creates a simple and repeatable pipeline that increases agility while maintaining reliability. This approach aligns with both DevOps and SRE practices: reducing deployment complexity, lowering blast radius, and supporting rapid iteration. Option B best reflects this philosophy: automated, continuous small deployments provide simplicity, stability, and agility simultaneously. Option A improves process clarity but does not directly affect agility. Option C is beneficial but broader and not specific to simplicity. Option D focuses on control rather than agility. Thus, B is correct. References: Site Reliability Engineering, Chapter: "Release Engineering." The Site Reliability Workbook, CI/CD and Safe Deployment patterns.
Question 10
Which of the following is the MOST accurate description of Kubernetes?
Correct Answer: C
Comprehensive and Detailed Explanation From Exact Extract: Kubernetes is described in SRE-aligned literature as an open-source container orchestration platform that automates deployment, scaling, failover, and lifecycle management of containerized applications. The Site Reliability Workbook references Kubernetes as: "a container management system that automatically handles service discovery, scaling, rollout management, and self-healing." (SRE Workbook - Production Environment chapters). Kubernetes does not replace an OS, nor is it a CI/CD platform; it sits on top of an OS and orchestrates containers across clusters. Option C is the most accurate: it captures container management, cloud deployment context, automated scaling, and failover-key capabilities of Kubernetes. Options A and B incorrectly describe CI/CD platforms. Option D incorrectly labels Kubernetes as an "operating system." Thus, C is correct. References: The Site Reliability Workbook, Kubernetes usage examples. Kubernetes Documentation (Orchestration, Auto-scaling, Self-healing).
