Important PeopleCert DevOps SRE Exam Questions

Answer: A

Explanation:

Comprehensive and Detailed Explanation From Exact Extract:

Containers provide a major advantage that aligns with SRE: portability and environment consistency. The SRE Workbook describes containers as: ''lightweight, portable units that encapsulate applications and dependencies, ensuring consistent behavior across environments.'' This independence from the host OS environment enables predictable deployments and simplifies automation, scaling, and orchestration---especially when used with Kubernetes.

Option A captures this exact benefit: portability and independence from the host OS.

Option B is incorrect---containers do not reduce the number of developers required.

Option C incorrectly claims that efficiency comes from virtual machines; containers are typically more efficient because they avoid VM overhead, not leverage it.

Option D is incorrect---containers do not ''inherit'' security automatically; in fact, they require additional security controls.

Thus, A is the correct answer.

The Site Reliability Workbook, Sections on containers, Docker, and Kubernetes.

Site Reliability Engineering, containerization and orchestration discussions.

Answer: B

Explanation:

Comprehensive and Detailed Explanation From Exact Extract:

SRE and DevOps release engineering define a canary release as rolling out new features to a small subset of users to validate reliability and performance before full release. The SRE Book states: ''Canarying is the practice of releasing changes to a small percentage of users or servers first to detect issues before global rollout.'' This minimizes risk by catching regressions early without impacting the entire user base.

Option B fits this definition exactly.

Option A (rolling wave) is a deployment pattern but not canarying.

Option C resembles phased rollout but not specifically canary release.

Option D describes testing, not production canary deployment.

Thus, B is correct.

Site Reliability Engineering, Chapter: ''Release Engineering.''

The Site Reliability Workbook, section on Canary Releases and Safe Deployments.

Answer: A

Explanation:

Comprehensive and Detailed Explanation From Exact Extract:

''Toil'' in SRE has a very specific meaning. According to the Site Reliability Engineering Book, Chapter ''Eliminating Toil'':

''Toil is the kind of work tied to running a production service that tends to be manual, repetitive, automatable, tactical, has no enduring value, and scales linearly as the service grows.''

The key phrase is ''no enduring value.'' Toil does not produce lasting improvement, even though it may be necessary in the short term. It consumes engineering effort without making the system better over time.

Why the other options are incorrect:

B Work that has some enduring value cannot be classified as toil by definition.

C Engineering work that adds service features is explicitly non-toil, because SRE defines feature work as ''project work,'' not operational toil.

D Seems close but is misleading: engineering work without enduring value is poor engineering, not necessarily toil. Toil refers to operations workload specifically.

Thus, A is the correct and precise definition of toil.

Site Reliability Engineering Book, ''Eliminating Toil''

Answer: B

Explanation:

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

Explanation:

Comprehensive and Detailed Explanation From Exact Extract:

Error budgets represent the allowable amount of unreliability in a system. Google defines the purpose of error budgets as: ''balancing the pace of innovation with the need for reliability.'' (SRE Book -- Service Level Objectives). When the error budget is healthy, product teams can release features quickly; when it is exhausted, reliability work takes priority. This balance prevents over-investment in reliability and enables safe innovation.

Option B---innovation and reliability---is the exact phrasing used in Google's SRE literature.

Options A, C, and D do not reflect the core purpose of error budgets.

Thus, B is the correct answer.

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

The Site Reliability Workbook, Error Budget Policy discussions.