DevOps-SRE PeopleCert Site Reliability Engineering (SRE) Foundation v1.2 Free Practice Exam Questions (2025 Updated)

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:

The future growth envelope refers to the anticipated growth trajectory of a service, including expected load, user demand, data volume, and performance requirements. Planning for this growth is essential to ensuring that a service can scale reliably without violating SLOs.

The Site Reliability Engineering Book, in discussions on capacity planning, states:

“A key element of capacity planning is estimating future demand so that systems can scale to meet user needs without sacrificing reliability.”

The SRE Workbook reinforces this concept:

“Understanding expected growth enables teams to design systems that scale and remain reliable as usage increases.”

Having the growth envelope defined enables:

Proper capacity planning

Avoiding resource exhaustion

Ensuring scalability before it becomes a reliability problem

Designing architectures that can handle future load

Why the other options are incorrect:

A Signed artifacts relate to supply chain security, not scaling.

C SLO/SLI reviews do not require growth envelope analysis.

D Error budgets relate to reliability thresholds, not capacity forecasting.

Thus, B is the correct answer.

Comprehensive and Detailed Explanation From Exact Extract:

Embracing failure—through practices such as blameless postmortems, chaos engineering, and proactive detection—enables organizations to improve their incident response performance. This directly improves:

MTTD (Mean Time to Detect)

MTTR (Mean Time to Recover)

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

“By examining failures without blame and learning from them, organizations improve their ability to detect issues faster and recover more quickly.”

Similarly, in the SRE Workbook, section on incident response:

“Learning from incidents is essential to reducing time to detection and time to mitigation.”

Why the other options are incorrect:

A MTBSI (Mean Time Between System Incidents) is influenced by architecture and testing, not directly by embracing failure.

B These are DORA metrics — important, but not primarily tied to failure-embracing practices.

C Too vague and not a standard SRE metric pair.

Thus, D is the correct answer.