The Site Reliability Engineering (SRE) Foundation v1.2 (DevOps-SRE)

Comprehensive and Detailed Explanation From Exact Extract:

A Business Continuity Plan (BCP) is a critical component of organizational resilience. While not unique to SRE, SRE strongly intersects with continuity planning because reliable systems must continue functioning during disruptions. According to Google’s SRE principles, reliability extends beyond typical outages and includes “ensuring services continue to operate even under exceptional conditions.” (SRE Book – Chapter: Addressing Risks). A business continuity plan specifically outlines how essential operations are maintained during major disruptions such as natural disasters, data center outages, or large-scale system failures.

Option A—“The way the organization maintains operations during a disaster”—matches the formal definition of BCP.

Option B refers to disaster recovery (DR), which is separate; DR focuses on restoring systems, not maintaining ongoing operations.

Option C refers to configuration management activities, not continuity.

Option D refers to risk management, which informs BCP but does not define it.

Therefore, A is the correct answer because it directly reflects the purpose of continuity planning as supported by reliability-focused guidance.

Comprehensive and Detailed Explanation From Exact Extract:

In a safety culture, SRE emphasizes psychological safety so engineers can work effectively in production without fear of blame. However, safety never removes accountability. Engineers must take responsibility for their actions, decisions, and assumptions, particularly during incidents.

The Site Reliability Engineering Book, Chapter “Postmortem Culture,” states:

“Blamelessness does not eliminate accountability. Individuals must still explain the context, assumptions, and reasoning behind their decisions so that the organization can learn.”

Google stresses that:

Engineers must feel safe to act and report issues

Engineers must remain responsible and accountable

Accountability enables learning, not punishment

Why other options are incorrect:

A Sharing incidents on social media violates confidentiality

C Blameless postmortems are required, not skipped

D Avoiding on-call is contrary to SRE responsibilities

Thus, B is correct.

Comprehensive and Detailed Explanation From Exact Extract:

SRE and DevOps release engineering define a canary release as rolling out new features to a small subset of users to validate reliability and performance before full release. The SRE Book states: “Canarying is the practice of releasing changes to a small percentage of users or servers first to detect issues before global rollout.” This minimizes risk by catching regressions early without impacting the entire user base.

Option B fits this definition exactly.

Option A (rolling wave) is a deployment pattern but not canarying.

Option C resembles phased rollout but not specifically canary release.

Option D describes testing, not production canary deployment.

Thus, B is correct.

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.

Comprehensive and Detailed Explanation From Exact Extract:

When a team exceeds its error budget, SRE practice requires applying error budget policies that restrict feature releases and shift focus toward reliability improvement. The idea is to prevent further degradation of user experience and ensure the service meets the agreed reliability targets.

The Site Reliability Engineering Book, Chapter “Service Level Objectives,” states:

“If the service exceeds its error budget, all new feature launches or risky changes are halted until reliability returns to acceptable levels. Engineering work should be directed toward addressing the causes of the budget overrun.”

This aligns with option A, which describes a reliability-focused response during sprint planning. Limiting sprint planning to post-mortem action items and reliability improvements is a direct application of error budget policies.

Additional guidance from the SRE Workbook:

“Error budget burn should directly influence decision-making. When the budget is exhausted, the team must focus on remediation work rather than new features.”

Why the other options are incorrect:

B Reviewing the error budget’s realism can be done periodically, but it is not the immediate consequence of a breach.

C Extending the error budget invalidates its purpose and is discouraged.

D Ignoring the error budget contradicts the entire SRE model and Google’s official guidance.

Therefore, A is the only correct answer.

Comprehensive and Detailed Explanation From Exact Extract:

The statement “Toil is not important work” is NOT an SRE principle. This is incorrect based on the official Google SRE documentation. In the Site Reliability Engineering Book, toil is treated as a critical concept, because identifying and reducing toil directly enables reliability improvements and more engineering-focused work. The SRE book emphasizes that toil must be taken seriously and systematically reduced, but never dismissed.

From the SRE Book, Chapter “Eliminating Toil”:

“Toil is the kind of work tied to running a production service that tends to be manual, repetitive, automatable, tactical, with no enduring value, and that scales linearly as a service grows.”

The SRE book further emphasizes:

“SRE teams should measure toil, track it, and make constant efforts to reduce it.”

This demonstrates that toil is significant and should not be ignored. Therefore, any suggestion that “toil is not important work” contradicts the documentation.

The other answer choices are actual SRE principles:

Operations is a software problem — From SRE Book Introduction: “SRE’s approach starts with the belief that operations is fundamentally a software engineering problem.”

Operations is a software problem — From SRE Book Introduction: “SRE’s approach starts with the belief that operations is fundamentally a software engineering problem.”

Automate what is currently done manually — Automation is a central SRE philosophy to reduce toil.

Reduce the cost of failure — Error budgets and controlled risk-taking are core SRE concepts designed to reduce the cost of failure.

Thus, the only option that is NOT an SRE principle is C.

Comprehensive and Detailed Explanation From Exact Extract:

A Service Level Indicator (SLI) is a measurement of some aspect of reliability (e.g., latency, availability, quality). One of its defining characteristics is that it must be measured over a specific time window. Without a time horizon, the SLI has no actionable meaning.

From the Site Reliability Engineering Book, Chapter “Service Level Indicators”:

“An SLI is a quantitative measure of some aspect of the level of service that is provided. SLIs are evaluated over a specific period of time in order to understand reliability as experienced by the user.”

The SRE Workbook further states:

“Every SLI must define a measurement window. Without a time horizon, the indicator cannot be used to calculate SLO compliance.”

Why the other options are incorrect:

A SLIs do not need to appear in an SLA; SLAs are external contracts, SLOs/SLIs are internal engineering tools.

B SLIs may include client-side, server-side, or network metrics depending on what reflects user experience.

D SLI agreement is not defined by SRE vs. Agile teams; it is defined by business and user need.

Thus, the correct answer is C.

Comprehensive and Detailed Explanation From Exact Extract:

The SRE Workbook describes an Error Budget Policy as a formal decision-making framework that defines what actions to take when a service consumes its error budget. Specifically, Google writes: “An error budget policy establishes when and how teams must intervene, whether to pause releases, prioritize reliability work, or adjust processes.” (SRE Workbook – Error Budget Policies). The purpose is to create predictable responses to reliability degradation—not simply alerting, innovation boosting, or bug prevention.

Option C best matches the definition: deciding when and how to intervene based on error budget burn.

Option A is only an alerting rule, not a policy.

Option B is an outcome of a healthy budget, not the policy’s purpose.

Option D is too narrow and is not how error budgets are framed.

Thus, C is correct.

Comprehensive and Detailed Explanation From Exact Extract:

“Toil” in SRE has a very specific meaning. According to the Site Reliability Engineering Book, Chapter “Eliminating Toil”:

“Toil is the kind of work tied to running a production service that tends to be manual, repetitive, automatable, tactical, has no enduring value, and scales linearly as the service grows.”

The key phrase is “no enduring value.” Toil does not produce lasting improvement, even though it may be necessary in the short term. It consumes engineering effort without making the system better over time.

Why the other options are incorrect:

B Work that has some enduring value cannot be classified as toil by definition.

C Engineering work that adds service features is explicitly non-toil, because SRE defines feature work as “project work,” not operational toil.

D Seems close but is misleading: engineering work without enduring value is poor engineering, not necessarily toil. Toil refers to operations workload specifically.

Thus, A is the correct and precise definition of toil.