PeopleCert Site Reliability Engineering Foundation v1.2 DevOps SRE SRE Exam Questions

Answer : B

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.

Site Reliability Engineering Book, ''Postmortem Culture''

SRE Workbook, ''Learning from Incidents''

Answer : A

Comprehensive and Detailed Explanation From Exact Extract:

Error budgets are a fundamental SRE mechanism for balancing reliability and innovation. The SRE book states: ''The error budget directly governs the rate of change: as long as the service stays within budget, development velocity can remain high.'' (SRE Book -- Chapter: Service Level Objectives). This means teams can push changes aggressively as long as the allowed amount of unreliability has not been consumed.

The error budget acts as a safety threshold. When reliability dips and the error budget is consumed, SRE enforces a change freeze to restore stability. Google explains: ''If the error budget is spent, releases are halted and efforts focus on improving reliability.'' Feature velocity is not arbitrarily slowed---it is governed solely by the remaining error budget.

Option A best expresses this: when the error budget is high, teams can safely accelerate feature delivery.

Option D incorrectly suggests rushing, which contradicts controlled release practices.

Option B misinterprets error budgets as a percentage-based throttling system.

Option C incorrectly implies that innovation stops entirely only when empty.

Thus, A is the correct interpretation according to official SRE principles.

Site Reliability Engineering: How Google Runs Production Systems, Chapter: ''Service Level Objectives.''

The Site Reliability Workbook, Sections on implementing error budgets and release governance.

Answer : A

Comprehensive and Detailed Explanation From Exact Extract:

Modern SRE-aligned organizations use small, cross-functional product teams capable of owning design, development, testing, and operational reliability. The SRE Book emphasizes: ''Effective service ownership arises from small, autonomous teams with diverse skillsets and strong collaboration habits.'' These teams share responsibility, encourage feedback, and maintain open communication to meet reliability goals.

Option A correctly identifies the two positive characteristics:

Small and collaborative

Cross-functional skillsets

Options 3 and 4 represent dysfunctional behaviors---SRE literature explicitly discourages responsibility silos and discouraging feedback, as these reduce reliability and slow incident learning.

Thus, A is the correct answer.

Site Reliability Engineering, Chapter: ''Organization and Culture.''

The Site Reliability Workbook, discussions on product-oriented team structures.

Answer : B

Comprehensive and Detailed Explanation From Exact Extract:

Linear-scaling toil refers to work whose effort increases proportionally to service growth, such as manually provisioning servers or handling capacity expansion. The Google SRE Book, Chapter ''Eliminating Toil,'' explains:

''Toil is work that scales linearly with the size of your service. A core strategy for reducing toil is to introduce automation that breaks the linear relationship.''

Auto-scaling capabilities directly address linear-scaling toil by automating resource allocation based on load or demand. This prevents engineers from repeatedly and manually adjusting infrastructure as usage grows.

The SRE Workbook also emphasizes:

''Infrastructure automation such as auto-scaling removes a major source of linear scaling toil by ensuring that capacity adjusts automatically as services grow.''

Why the other options are incorrect:

A Manual scaling is linear-scaling toil, not a solution.

C Outsourcing development does not reduce operational toil.

D Switching cloud providers alone does not solve toil unless automation is introduced.

Thus, B is the correct answer.

Site Reliability Engineering Book, ''Eliminating Toil''

SRE Workbook, ''Toil Reduction Strategies''

Answer : A

Comprehensive and Detailed Explanation From Exact Extract:

SRE strengthens DevOps by adding reliability engineering, SLOs, error budgets, and production-focused automation. One key improvement is that the CI/CD pipeline extends safely into production using automated, tested, reliable deployment mechanisms.

The Site Reliability Engineering Book, ''Release Engineering'' chapter states:

''SRE complements DevOps by creating safe pathways for automated production deployments through engineering practices such as canarying, automation, and release gates.''

The SRE Workbook adds:

''SRE helps mature DevOps pipelines so they can operate safely in production, enabling continuous delivery to reach all the way through deployment.''

Why the other options are incorrect:

B SRE makes CD more necessary, not redundant

C SRE does not replace DevOps engineers

D IaC does not require moving to the cloud

Thus, the correct answer is A.

Site Reliability Engineering Book, ''Release Engineering''

SRE Workbook, ''Safe Deployments and CI/CD Integration''

Answer : B

Comprehensive and Detailed Explanation From Exact Extract:

One of SRE's strengths is using software engineering and automation to reduce manual, process-heavy work. This aligns perfectly with ITSM goals around repeatability, compliance, and quality.

The SRE Workbook, section ''SRE and ITIL Integration,'' explains:

''SRE can complement ITSM by applying automation and engineering practices to reduce manual process load, increase consistency, and meet compliance requirements.''

Examples include:

Automating change processes

Automating incident response flows

Improving configuration consistency

Reducing ticket-driven toil through engineering

Why the other options are incorrect:

A CAB approvals are not governed by error budgets

C Ticket acceleration is not the goal of SRE

D Engineering CMDBs is not the primary mechanism for ITSM alignment

Thus, B is correct.

SRE Workbook, ''Modernizing Operations and ITIL Alignment''

Answer : A

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