Pass the PeopleCert DevOps DevOps-SRE Questions and answers with ExamsMirror

Comprehensive and Detailed Explanation From Exact Extract:

Known workarounds represent toil that has no enduring value, one of the key characteristics of toil defined by the SRE framework.

From the Site Reliability Engineering Book, Chapter “Eliminating Toil”:

“Toil is work that is manual, repetitive, automatable, tactical, has no enduring value, and scales linearly with service size.”

Known workarounds fit this definition because:

They solve the same recurring problems repeatedly

They do not permanently fix the underlying issue

They consume engineer time without contributing long-term improvements

These activities lack enduring value and should be eliminated through automation or engineering fixes.

Why the other options are incorrect:

A. Linear scaling — Many forms of toil scale linearly, but this does not specifically describe workarounds.

B. Tactical — Tactical means short-term, but not all tactical work is a workaround.

C. Automatable — While some workarounds can be automated, not all are.

D. No enduring value — This is the defining trait of workaround-type toil.

Therefore, option D is correct.

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.

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:

In SRE practice, “full-service ownership” means the same team is responsible for the service across its entire lifecycle: design, development, deployment, operation, and continuous improvement. Google’s Site Reliability Engineering: How Google Runs Production Systems describes SRE as a software-engineering-focused approach to operations, where engineers are responsible not only for writing the code but also for running it in production and improving its reliability over time. This aligns with the “you build it, you run it” model, which removes the traditional wall between development and operations and makes one team accountable for the whole service.

Option D — “The team is accountable for coding, shipping, and improving the application” — best matches this concept because it explicitly includes building (coding), releasing (shipping), and iterating (improving). Options A and B do not clearly include operational responsibility, and option C narrows the focus only to performance and reliability, omitting ownership of development and releases. Therefore, D most accurately reflects full-service ownership as described in SRE literature.

References (conceptual alignment):

Site Reliability Engineering: How Google Runs Production Systems, Betsy Beyer et al., O’Reilly, particularly:

Introduction & “What Is Site Reliability Engineering?”

“Introduction to SRE at Google” and discussions of dev/ops ownership boundaries.

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.

Comprehensive and Detailed Explanation From Exact Extract:

A Production Readiness Review (PRR) is a core SRE practice ensuring that a service meets specific reliability, operational, monitoring, and alerting standards before SRE assumes responsibility. The Site Reliability Engineering (SRE) Workbook states: “PRRs validate that a service is prepared for production and ready for SRE engagement, ensuring operational readiness, monitoring completeness, on-call preparation, and automation maturity.” The goal is not merely organizational handover but ensuring the service is fully prepared for reliable operation in production.

Option A fits this definition exactly: ensuring the service is ready for SRE support.

Option B focuses on development/testing readiness, not production readiness.

Option C references standards/frameworks not part of PRR’s purpose.

Option D is only a partial implication—transition of accountability happens after PRR readiness, not the main purpose of PRR.

Thus, A is the correct SRE-aligned answer.

Comprehensive and Detailed Explanation From Exact Extract:

SRE emphasizes decision-making based on measured data, not intuition. The SRE Book explains: “Monitoring and SLOs provide an objective basis for decision-making, replacing guesswork with quantifiable data.” (SRE Book – SLOs & Monitoring). Data enables SRE teams to understand system behavior, validate assumptions, detect anomalies, and prioritize engineering work. The primary benefit is not merely collecting data, but analyzing and interpreting it to support decisions grounded in facts rather than opinion.

Option A accurately reflects this principle: data analysis and interpretation enable fact-based decisions, which is the core justification for SRE’s reliance on SLIs and observability signals.

Option B overstates by claiming data alone is always sufficient.

Option C refers to data mining, which is not a core SRE concept.

Option D is partially true but narrower than the SRE philosophy of data-driven operations.

Thus, A is the most accurate SRE-aligned answer.

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

Comprehensive and Detailed Explanation From Exact Extract:

In SRE incident management, Google defines several formal roles during a major incident, including Incident Commander (IC), Communications Lead, Operations/Responder, and Planning Specialist. According to the SRE Workbook: “The Planning Lead is responsible for maintaining the source-of-truth incident state document, tracking action items, and ensuring the IC has the current situation overview.” (SRE Workbook – Chapter: Incident Management). This document contains timelines, changes, decisions, diagnostics, and action items—all crucial for reducing cognitive load during high-stress situations.

Option C—Planning Specialist—is therefore correct.

Option A (Logistics Specialist) is not defined as a core SRE incident role.

Option B (Communications Lead) manages outward communication, not the live incident log.

Option D (Incident Commander) leads the incident but delegates documentation to the planning role.

Hence, option C is the only answer that aligns with SRE’s defined responsibilities.

Comprehensive and Detailed Explanation From Exact Extract:

SRE-led service automation focuses on making environments reproducible, reliable, and consistent. One of the key principles aligned with Google SRE practices is the use of Infrastructure as Code (IaC), which allows environments to be provisioned automatically, consistently, and predictably.

The Site Reliability Engineering Book, in its discussions on automation, states:

“Automation implemented as code ensures that environments are consistent, repeatable, and less prone to human error.”

The SRE Workbook expands on this concept:

“Infrastructure as Code allows services to scale and evolve reliably by ensuring that configuration and infrastructure changes are automated and version-controlled.”

IaC is fundamental to:

Reducing toil

Increasing reliability

Enabling consistent automation across environments

Reducing configuration drift

Why the other options are incorrect:

A SRE supports testing in production; it does not ban automated tests.

C Using unsigned artifacts violates security and reliability best practices.

D Adding hardware is not an automation principle and contradicts efficiency goals.

Thus, the correct answer is B.