PeopleCert DevOps-SRE Practice Exam Questions & Answers

Comprehensive and Detailed Explanation From Exact Extract:

Traditional monitoring works well when systems are static and predictable. However, cloud-native, distributed, and microservice-based architectures create highly dynamic environments. In these cases, observability becomes more effective because it provides visibility across entire systems, rather than focusing on individual components.

From Google's Observability guidance:

''Traditional monitoring relies on predefined dashboards and known failure modes. In modern cloud systems, component-level monitoring becomes insufficient because failures occur in ways that cannot always be predicted.''

Further, in the SRE Workbook:

''Monitoring individual components does not provide adequate visibility into complex distributed systems. Observability enables teams to understand system-wide behavior and user impact.''

Why options are incorrect:

A Observability is not inherently cheaper.

C While true, it is not the best reason; observability's benefit is broader than scale alone.

D Traditional monitoring can support containers but often becomes noisy and ineffective.

Thus, the best answer is B.

SRE Workbook, ''Monitoring and Observability''

Google Cloud Architecture Framework, ''Observability vs Monitoring''

Comprehensive and Detailed Explanation From Exact Extract:

The term observability comes directly from control theory and refers to the ability to infer the internal state of a system from its external outputs. Modern SRE and observability practices adopt this definition.

Google's Site Reliability Engineering guidance (SRE Book Addendum on Observability) states:

''Observability is a property of a system that allows operators to understand its internal state by examining its outputs such as logs, metrics, and traces.''

This aligns exactly with Option C, the formal definition.

Why the other options are incorrect:

A Monitoring is part of observability, but observability is much broader.

B Health checks are simply one signal; they do not represent observability.

D Data collection is a mechanism, not the definition of observability itself.

Thus, C is the correct and academically accurate definition.

Site Reliability Engineering Book Addendum: Observability

Google Cloud Architecture Framework: Observability Principles

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

Comprehensive and Detailed Explanation From Exact Extract:

An error budget accounts for all downtime, including both planned and unplanned outages. This is a critical SRE principle: the user does not distinguish between maintenance downtime and accidental downtime --- therefore, neither should the SLO nor the error budget.

The SRE Book, Chapter ''Service Level Objectives,'' states:

''From the user's perspective, availability is simply whether the service is working or not, regardless of whether the outage was planned or unplanned.''

This means all downtime counts toward the error budget.

Additionally, the SRE Workbook reinforces this point:

''Error budgets must include every form of unavailability --- maintenance events, configuration changes, emergency work, and unexpected incidents.''

This confirms that planned outages (maintenance windows) and unplanned outages (incidents) both consume error budget.

Why the other options are incorrect:

A Only includes unplanned incidents; SRE requires counting planned outages as well.

B Defect fixes may contribute to downtime, but ''defect fixes'' alone are not a downtime category.

D CAB approval has no bearing on whether outages count toward error budgets.

Thus, C is correct: any planned or unplanned outage must be included.

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

SRE Workbook, ''Implementing SLOs''

Comprehensive and Detailed Explanation From Exact Extract:

SRE and modern DevOps best practices require that build artifacts---such as binaries, container images, and deployment packages---be stored in a secure, versioned artifact repository. These repositories ensure integrity, traceability, immutability, and security of deployment packages.

While the SRE Book does not use the ITIL term DML, it emphasizes:

''All production binaries should be stored in a secure, versioned repository to ensure consistent, repeatable, and trustworthy deployments.''

--- Site Reliability Engineering Book, section on Release Engineering

The SRE Workbook expands on this principle by emphasizing signed and verified artifacts:

''To ensure safe rollout, artifacts must be built once, stored securely, signed, versioned, and deployed from a controlled artifact repository.''

Why the other options are incorrect:

A A CMS manages configuration, not deployment artifacts.

B Subversion is a source code repository, not an artifact repository.

C A DML is an ITIL concept, but SRE practice does not rely on it; instead, SRE uses modern artifact repositories (e.g., GCR, ACR, Artifactory).

Thus, the correct answer is D.

Site Reliability Engineering Book, ''Release Engineering''

SRE Workbook, ''Safe Deployments''

Google Cloud Build & Artifact Registry documentation

Comprehensive and Detailed Explanation From Exact Extract:

The Westrum Organizational Culture Model categorizes organizations based on how effectively they allow information to flow, particularly in high-risk and high-performance environments. This model is widely referenced in SRE and DevOps practices and is cited by Google in their SRE culture guidance.

The Westrum model identifies three culture types:

Pathological (power-oriented)

Bureaucratic (rule-oriented)

Generative (performance-oriented)

From the SRE Workbook and Google's DevOps Research (DORA):

''The Westrum model is a taxonomy of organizational cultures based on how information flows. Generative cultures---with high cooperation and open information flow---correlate with higher reliability and better outcomes.''

Why the other options are incorrect:

A Deployment frequency is a DORA metric, not Westrum's focus.

C Resource flow is unrelated to Westrum.

D While communication affects design, Westrum specifically studies information flow as a cultural health indicator, not structural design.

Thus, the correct answer is B.

SRE Workbook, ''Cultural Change''

Google DORA Research, ''Accelerate State of DevOps Report''

Ron Westrum, ''A Typology of Organizational Cultures''

Comprehensive and Detailed Explanation From Exact Extract:

Application Performance Management (APM) refers to a set of tools and practices used to monitor and manage the performance, behavior, and availability of software applications. Although APM is not defined exclusively in the Google SRE Book, it is described within the broader context of monitoring and observability.

In the SRE Workbook, under Monitoring:

''Application monitoring tools provide insights into the performance, latency, availability, and behavior of applications to help engineering teams maintain reliability.''

Industry-standard APM frameworks (including Google Cloud Operations Suite, formerly Stackdriver) define APM as:

''The monitoring and management of application performance and availability.''

Why the other options are incorrect:

A describes telemetry, not APM.

C describes system monitoring (infrastructure), not application performance monitoring.

D refers to communication of metrics, not the monitoring of application performance.

Therefore, B is the correct definition.

SRE Workbook, ''Monitoring''

Google Cloud Operations Suite (APM documentation)