DevOps-SRE Exam Questions & Answers

Comprehensive and Detailed Explanation From Exact Extract:

Burning the error budget to zero --- strategically, not accidentally --- helps ensure the correct balance between release velocity and system stability, which is the fundamental purpose of error budgets. Error budgets exist to encourage a healthy level of risk-taking up to the point where user experience is not impacted.

From the Site Reliability Engineering Book, SLO chapter:

''Error budgets provide a mechanism for balancing innovation and reliability by allowing measured risk-taking while ensuring user expectations are met.''

The SRE Workbook adds:

''Teams should aim to use their full error budget. Not using it implies missed opportunities to deliver features or improvements.''

This means that strategically burning the error budget to zero ensures:

Teams are shipping value at maximum safe velocity

Reliability goals are still respected

Risk is managed and intentional

Why other options are incorrect:

B Capacity measurement is unrelated to error budget consumption.

C Error budgets should not be continually revised unless business needs change.

D Conversations with partners may occur, but this is not the primary benefit.

Thus, the correct answer is A.

Site Reliability Engineering Book, ''Service Level Objectives''

SRE Workbook, ''SLO Engineering''

Comprehensive and Detailed Explanation From Exact Extract:

SRE is built on transparency and broad information sharing. The SRE Book states: ''High-quality operations require that information flows freely between product development, SRE, and associated teams.'' (SRE Book -- Chapter: Communication and Collaboration). Effective incident management also depends on complete data availability: ''Centralized, shared information reduces cognitive load and improves incident resolution.'' (SRE Workbook -- Incident Management).

Option B aligns perfectly with SRE principles: data must flow freely, ensuring everyone has access to metrics, logs, architecture details, incident context, and SLOs.

Options A, C, and D promote restricted or fragmented data practices, which are directly contrary to SRE design. SRE teams avoid information silos.

Thus, B is correct.

Site Reliability Engineering, Chapters: ''Communication and Collaboration,'' ''Incident Management.''

The Site Reliability Workbook, guidance on transparency in incident handling.

Comprehensive and Detailed Explanation From Exact Extract:

Traditional IT escalation paths---before modern SRE practices---were generally based on hierarchical or functional structures. The SRE Workbook explains that SRE aims to ''replace rigid hierarchical escalation paths with structured incident roles and clear authority during incidents.'' (SRE Workbook -- Incident Management). These older models include:

Hierarchical escalation: issues are escalated to higher managerial or senior technical tiers.

Functional escalation: issues are escalated across functional lines depending on expertise (network team, DBAs, sysadmins, etc.).

Both models are referenced throughout reliability engineering literature as ''traditional escalation paths,'' which SRE incident management explicitly avoids by instead using role-based escalation (IC, Communications Lead, Ops Lead, etc.).

Options 3 and 4 (Cyclical and Logical) are not recognized escalation patterns in ITSM or SRE literature.

Thus, the answer is A (1 and 2).

The Site Reliability Workbook, Chapter: ''Effective Incident Management.''

ITIL v3 Escalation Concepts (hierarchical and functional escalation).

Comprehensive and Detailed Explanation From Exact Extract:

The SRE model heavily emphasizes cross-functional teamwork. In the SRE Workbook and chapters addressing incident management, Google defines collaboration as ''bringing together individuals with diverse expertise to jointly solve problems and make decisions.'' Collaboration implies active engagement, shared goals, and joint execution---exactly what the statement describes.

Option B, Collaboration, fits perfectly because effective problem-solving during incidents, launches, or reliability engineering work requires engineers from multiple disciplines (e.g., SRE, developers, network teams, product teams) to work together directly.

Option A (Coordination) is more about task alignment, not joint problem-solving.

Option C (Communication) is necessary but insufficient for solving problems together.

Option D (Cooperation) implies helpfulness, not necessarily integrated problem-solving.

Thus, B is the correct concept.

The Site Reliability Workbook, Chapter: ''Effective Incident Management.''

Site Reliability Engineering, Sections on teamwork and cross-functional collaboration.

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.

Site Reliability Engineering Book, ''Service Level Objectives''

SRE Workbook, ''Managing Load'' and ''Implementing SLOs''