Important PeopleCert DevOps SRE Exam Questions

Answer: C

Explanation:

Comprehensive and Detailed Explanation From Exact Extract:

In the context of SRE tooling and automation, configuration management platforms like Puppet support large-scale infrastructure reliability by enabling consistency, repeatability, and automation. Puppet's Discovery capability allows engineers to automatically locate, identify, classify, and group cloud nodes or infrastructure resources. Although not directly from Google's SRE Book, Discovery aligns with SRE principles of reducing toil and enabling scalable automation. SRE emphasizes ''automating away the manual work of locating and managing infrastructure at scale.'' (SRE Book -- Chapter: Eliminating Toil). Puppet Discovery does precisely this by automatically scanning environments, detecting nodes, and providing metadata to group or manage them.

Option A (Provisioning) refers to creating infrastructure, not identifying it.

Option B (Delivery) relates to CI/CD processes.

Option D (Insight) relates to analytics and reporting, not node identification.

Therefore, C. Discovery is correct as it directly represents the capability described.

Site Reliability Engineering: How Google Runs Production Systems, Chapter: ''Eliminating Toil.''

Puppet Labs Documentation (Discovery feature).

Answer: C

Explanation:

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

Answer: B

Explanation:

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

Answer: B

Explanation:

Comprehensive and Detailed Explanation From Exact Extract:

Using verified and signed artifacts is essential for safe automation, ensuring that deployments are consistent and free of dependency or supply chain errors. This is a fundamental principle in Google's release engineering and SRE practices.

The Site Reliability Engineering Book, chapter ''Release Engineering,'' states:

''Releases should be built once, tested, signed, and stored in a secure repository. Only signed and verified artifacts should be promoted to production to prevent configuration drift and dependency inconsistencies.''

The SRE Workbook echoes this:

''Automated promotions depend on the integrity and immutability of artifacts. Signed artifacts ensure consistency and prevent errors related to mismatched dependencies.''

Why the other options are incorrect:

A External visibility is irrelevant and may create security risks.

C Error budgets relate to reliability, not artifact promotion.

D SLOs do not define artifact signing; this is handled by release engineering processes.

Thus, the correct answer is B.

Site Reliability Engineering Book, ''Release Engineering''

SRE Workbook, ''Automation and Safe Releases''

Answer: A

Explanation:

Comprehensive and Detailed Explanation From Exact Extract:

When a team exceeds its error budget, SRE practice requires applying error budget policies that restrict feature releases and shift focus toward reliability improvement. The idea is to prevent further degradation of user experience and ensure the service meets the agreed reliability targets.

The Site Reliability Engineering Book, Chapter ''Service Level Objectives,'' states:

''If the service exceeds its error budget, all new feature launches or risky changes are halted until reliability returns to acceptable levels. Engineering work should be directed toward addressing the causes of the budget overrun.''

This aligns with option A, which describes a reliability-focused response during sprint planning. Limiting sprint planning to post-mortem action items and reliability improvements is a direct application of error budget policies.

Additional guidance from the SRE Workbook:

''Error budget burn should directly influence decision-making. When the budget is exhausted, the team must focus on remediation work rather than new features.''

Why the other options are incorrect:

B Reviewing the error budget's realism can be done periodically, but it is not the immediate consequence of a breach.

C Extending the error budget invalidates its purpose and is discouraged.

D Ignoring the error budget contradicts the entire SRE model and Google's official guidance.

Therefore, A is the only correct answer.

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

SRE Workbook, ''Managing Load'' and ''Implementing SLOs''