PeopleCert DEVOPS Institute Site Reliability Engineering Foundation (DEVOPS Institute SRE Foundation) Exam Questions

Answer : B

Comprehensive and Detailed Explanation From Exact Extract:

Fixed error budgets are preferred in SRE because they encourage smaller, safer, and more predictable releases, which inherently reduces risk. A fixed budget forces the team to consistently evaluate how much reliability they can afford to trade for delivery speed each month or quarter.

From the Site Reliability Engineering Book, Chapter ''Service Level Objectives'':

''Error budgets allow teams to make controlled decisions about the risk they take on. A fixed budget naturally encourages teams to release in smaller batches, which reduces the overall risk and impact of a failure.''

Similarly, the SRE Workbook states:

''When teams work within a fixed error budget, they tend to push changes in smaller increments to avoid burning the budget too quickly.''

Why the other options are incorrect:

A Fixed budgets reduce toil by reducing firefighting, not increase it.

C Fixed budgets can be exceeded; this is not a reason they are beneficial.

D Error budgets do not predict outages; they measure tolerated unreliability.

Thus, the correct and SRE-supported answer is B.

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

SRE Workbook, ''Implementing SLOs''

Answer : C

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

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.

Site Reliability Engineering Book, ''Introduction'' and ''Eliminating Toil'' Chapters

SRE Workbook, ''Eliminating Toil'' Section

Answer : D

Comprehensive and Detailed Explanation From Exact Extract:

Google's definition is explicit: ''An SLI is a carefully defined QUANTITATIVE measure of some aspect of the level of service provided.'' (SRE Book -- Chapter: Service Level Objectives). Examples include error rate, latency, throughput, and availability. SLIs are measurements, not targets---targets are SLOs.

Option D repeats Google's definition almost exactly.

Option C incorrectly describes an SLO (a target), not an SLI.

Options A and B mention subjective assessments---SRE explicitly rejects subjectivity in measurement, stating: ''SLIs must be objective and measurable.''

Thus, D is the correct and SRE-authentic answer.

Site Reliability Engineering, Chapter: ''Service Level Objectives.''

The Site Reliability Workbook, Chapter: ''Implementing SLOs.''

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 : 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 : B

Comprehensive and Detailed Explanation From Exact Extract:

The SRE Book defines reliability as: ''the probability that a system will perform its intended function correctly for a specified period of time.'' (SRE Book -- Introduction). Reliability focuses on correctness and consistent performance, not simply uptime. Availability (option A) refers to system uptime or accessibility. Durability (option C) refers to long-term data persistence. Throughput (option D) measures volume of work processed over time.

Because the definition explicitly mentions probability of meeting performance standards and correct output over time, it directly matches the SRE definition of reliability.

Thus, B is correct.

Site Reliability Engineering, Introduction section on reliability definitions.

The Site Reliability Workbook, Reliability fundamentals.

Answer : C

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.

The Site Reliability Workbook, Kubernetes usage examples.

Kubernetes Documentation (Orchestration, Auto-scaling, Self-healing).