Free Peoplecert (DevOps-SRE) Certification Sample Questions with Online Practice Test
DevOps-SRE Certification Study Guide Pass DevOps-SRE Fast
NEW QUESTION # 43
Which of the following BEST describes the two key elements that an error budget balances?
- A. Time and money
- B. Features and benefits
- C. Innovation and reliability
- D. Risk and reward
Answer: C
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.
References:
Site Reliability Engineering, Chapter: "Service Level Objectives."
The Site Reliability Workbook, Error Budget Policy discussions.
NEW QUESTION # 44
A team has exceeded their error budget by 10% in a particular month.
Give an example of what should happen next as a consequence.
- A. The Error Budget is extended for another month to determine if this breach was an anomaly
- B. The error budget is ignored in subsequent months as it is creating the wrong kind of behavior
- C. Sprint planning may only pull post-mortem action items from the backlog
- D. The Error Budget is reviewed to determine if it was realistic for the product or timeline
Answer: C
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.
References:
Site Reliability Engineering Book, "Service Level Objectives"
SRE Workbook, "Managing Load" and "Implementing SLOs"
NEW QUESTION # 45
Which of the following is the BEST description of a customer reliability engineer (CRE)?
- A. They work with me cloud provider's SRE team to ship and build new features
- B. They use deep engineering expertise to improve the cloud provider's services
- C. They take a software engineering approach to redesign allcloud services
- D. They integrate with the customer's operations team to share responsibilities
Answer: B
NEW QUESTION # 46
When applied to service levels, the principleof decreasing marginal productivity can be represented in three stages.Which of the following is NOT one of these stages?
- A. Negative returns
- B. Possible returns
- C. increasing returns
- D. Diminishing returns
Answer: B
NEW QUESTION # 47
Which of the following communication and collaboration practices BEST contribute to the effectiveness of the SRE team?
- A. Data is flowing freely within and around the SRE team.
- B. Project managers share limited data only upon request.
- C. Data in SRE should be managed separately from others.
- D. Team members should manage their own data discretely.
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
SRE is built on transparency and broad information sharing. The SRE Book states: "High-quality operations require that information flows freely between product development, SRE, and associated teams." (SRE Book
- Chapter: Communication and Collaboration). Effective incident management also depends on complete data availability: "Centralized, shared information reduces cognitive load and improves incident resolution." (SRE Workbook - Incident Management).
Option B aligns perfectly with SRE principles: data must flow freely, ensuring everyone has access to metrics, logs, architecture details, incident context, and SLOs.
Options A, C, and D promote restricted or fragmented data practices, which are directly contrary to SRE design. SRE teams avoid information silos.
Thus, B is correct.
References:
Site Reliability Engineering, Chapters: "Communication and Collaboration," "Incident Management." The Site Reliability Workbook, guidance on transparency in incident handling.
NEW QUESTION # 48
Which of the following BEST describes the relationship between Service Level Objectives and Service Level Indicators?
- A. Service level indicators are the measurements for the service level objectives
- B. Service level objectives are the measurements for the service level indicators
- C. Service level indicators are the performance targets for service level objectives
- D. Service level objectives are the performance metrics for service level indicators
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
The SRE Book provides a precise definition: "SLIs are the carefully defined quantitative measures of some aspect of the level of service provided. SLOs are the target values or ranges for these indicators." (SRE Book
- Chapter: Service Level Objectives). This establishes a clear hierarchical relationship: SLIs are the measurements, while SLOs define the acceptable target levels for those measurements.
Therefore, option A is correct: SLIs measure things like latency, availability, throughput, and error rate.
SLOs then define the goal such as "99.9% availability over 30 days."
Option B reverses the relationship.
Option C incorrectly says SLOs measure SLIs, which is backwards.
Option D confuses metrics and targets.
Thus, A is the only choice that aligns with Google's official SRE definitions.
References:
Site Reliability Engineering: How Google Runs Production Systems, Chapter: "Service Level Objectives." The Site Reliability Workbook, Chapter: "Implementing SLOs."
NEW QUESTION # 49
Which of the following BEST explains now an error budget allows for a maximum change velocity?
- A. Developers focus only on new feature work versus operational work if the budget is empty.
- B. Developers rush to do development work if me budget is high and stow down when it is low.
- C. Developers must slow down feature changes in line with the percentage the budget is used.
- D. Developers can focus on pushing out feature changes unite the error budget remains high.
Answer: D
NEW QUESTION # 50
Microservices are independent services that are developed, deployed, and maintained separately.
Which of the following BEST justifies the use of this application architecture?
- A. Creating a simple, lightweight business application
- B. Modernizing and refactoring legacy applications
- C. Building a basic product fast, as a proof of concept
- D. Modernizing the user interface of the core system
Answer: B
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
SRE supports microservices architecture because it improves reliability by reducing blast radius, allowing independent deployments, and enabling scalable autonomous teams. The SRE Book notes: "Microservices enable teams to independently iterate and improve reliability without the constraints of large monolithic systems." (SRE Book - Distributed Systems). One of the strongest reasons to adopt microservices is modernizing and refactoring large legacy monoliths, allowing them to be broken into independently deployable, maintainable components.
Option A is therefore the best justification.
Options B, C, and D may involve architectural choices, but they do not explain why microservices are the preferred architecture for reliability and scalability.
Thus, A is correct.
References:
Site Reliability Engineering, Chapters on Distributed Systems and Microservice Reliability Patterns.
NEW QUESTION # 51
Which of the following BEST describes the engineering side of SRE?
- A. Applying network and infrastructure development best practices for stable operations and good reliability
- B. Applying infrastructure engineering principles to build and maintain the stable delivery of operational services
- C. Applying network design and deployment best practices to achieve operational performance targets
- D. Applying software development best practices to solving operational problems and automating solutions
Answer: D
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
The foundational definition of SRE, as stated in Google's SRE Book, is that SRE uses software engineering as its primary tool to solve operational problems: "SRE is fundamentally doing operations work using software engineering approaches." (SRE Book - What Is SRE?). This includes building automation, writing tools, creating pipelines, and eliminating manual work. The "engineering side" focuses specifically on applying coding practices, testing, CI/CD, version control, and automation frameworks to operational domains such as deployment, monitoring, incident response, and capacity planning.
Option D captures this precisely: using software engineering best practices to solve operational issues and drive automation.
Options A, B, and C focus too narrowly on network or infrastructure engineering. While these can be components of SRE, they do not describe its engineering foundation as Google defines it.
Thus, D is the correct answer.
References:
Site Reliability Engineering: How Google Runs Production Systems, Introduction & Chapter: "What is SRE?" The Site Reliability Workbook, Chapter: "Eliminating Toil."
NEW QUESTION # 52
What is the primary difference between SRE and DevOps?
- A. DevOps is mostly for software engineers and SRE is mostly for infrastructure engineers
- B. DevOps and SRE are the same thing
- C. SRE is an implementation of DevOps but focuses mostly on post-production responsibilities
- D. DevOps encourages closer collaboration between development and operations whereas SRE is about building a silo around production operations
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
The primary difference between SRE and DevOps lies in their implementation focus and origins, though they share similar objectives. According to Google's official SRE documentation:
"SRE can be seen as a specific implementation of DevOps with some idiosyncratic extensions."
- Site Reliability Engineering Book, Chapter: What is Site Reliability Engineering?
While DevOps is a broad cultural and organizational philosophy aimed at closing the gap between development and operations through collaboration and automation, SRE provides a concrete, engineering- driven approach to achieving those goals - particularly through practices like error budgets, SLIs/SLOs, toil reduction, and incident response.
SRE focuses heavily on the post-production lifecycle - including reliability, monitoring, capacity planning, and incident response - whereas DevOps includes these concerns but emphasizes the entire software delivery lifecycle. Hence, Option A is the correct and most accurate answer.
Options B and C are incorrect:
* B wrongly implies a division of roles (DevOps = developers, SRE = infrastructure), which is not how these frameworks operate.
* C misrepresents SRE - it does not build silos but instead emphasizes shared responsibility and transparency in production systems.
* D is incorrect because, while aligned, SRE and DevOps are not identical.
References:
Site Reliability Engineering Book - Chapter: What is Site Reliability Engineering?https://sre.google/books/ The Site Reliability Workbook - Chapter 1: Introduction Google Cloud Blog - SRE vs DevOps: Companions, not Competitors
NEW QUESTION # 53
Which of the following is a principle of SRE-Led Service Automation?
- A. Using unsigned artifacts in production
- B. Adding as much hardware as possible
- C. No automated tests in production
- D. Environments provisioned using IaC
Answer: D
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
SRE-led service automation focuses on making environments reproducible, reliable, and consistent. One of the key principles aligned with Google SRE practices is the use of Infrastructure as Code (IaC), which allows environments to be provisioned automatically, consistently, and predictably.
The Site Reliability Engineering Book, in its discussions on automation, states:
"Automation implemented as code ensures that environments are consistent, repeatable, and less prone to human error." The SRE Workbook expands on this concept:
"Infrastructure as Code allows services to scale and evolve reliably by ensuring that configuration and infrastructure changes are automated and version-controlled." IaC is fundamental to:
* Reducing toil
* Increasing reliability
* Enabling consistent automation across environments
* Reducing configuration drift
Why the other options are incorrect:
* A SRE supports testing in production; it does not ban automated tests.
* C Using unsigned artifacts violates security and reliability best practices.
* D Adding hardware is not an automation principle and contradicts efficiency goals.
Thus, the correct answer is B.
References:
Site Reliability Engineering Book, "Eliminating Toil" and automation sections SRE Workbook, "Automation and Infrastructure as Code"
NEW QUESTION # 54
Which of the following BEST describe the characteristics of a product team?
1. They are small and collaborative
2. They have cross-functional skillsets
3. They do not share responsibilities.
4. They discourage any feedback
- A. 1 and 2
- B. 1 and 4
- C. 2 and 3
- D. 3 and 4
Answer: A
NEW QUESTION # 55
Which of the following BEST explains how an error budget allows for a maximum change-velocity?
- A. Developers focus only on new feature work versus operational work if the budget is empty.
- B. Developers can focus on pushing out feature changes while the error budget remains high.
- C. Developers must slow down feature changes in line with the percentage the budget is used.
- D. Developers rush to do development work if the budget is high and slow down when it is low.
Answer: B
Explanation:
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.
References:
Site Reliability Engineering: How Google Runs Production Systems, Chapter: "Service Level Objectives." The Site Reliability Workbook, Sections on implementing error budgets and release governance.
NEW QUESTION # 56
When outages are repetitive and similar they become a form of toll.
Which or the following describes the MOST compelling reason to adopt advanced technologies and artificial intelligence (AI)?
- A. To increase the mean tune to restore services (MTRS)
- B. To increase reliability by reducing MTTR and MTRS
- C. To increase the mean time to repair services (MTTR)
- D. To increase reliability and achieve perfect MTRS
Answer: B
NEW QUESTION # 57
Identify the defense depth (DiD) layer where data flows in from,and out to, other networks,including the Internet
- A. Physicallayer
- B. Host layer
- C. Data layer
- D. Perimeter layer
Answer: A
NEW QUESTION # 58
Which of the following BEST describes the relationship between service level objectives and service level indicators?
- A. Service level indicators are the measurements for the service level objectives
- B. Service level objectives are the measurements foe the service level indicators
- C. Service level indicators are the performance targets for service level objectives
- D. Service level objectives are the performance metrics for service level indicators
Answer: A
NEW QUESTION # 59
Reliability is a key pillar of digital experience monitoring and incident management.
Which of the following describes the BEST type of reliability monitoring strategy in SRE?
- A. A strategy that focuses on monitoring and discovering useful patterns in the performance of all active networks
- B. A strategy that uses traditional and familiar monitoring tools rather than advanced artificial intelligence
- C. A strategy that instruments observability and provides monitoring insights across all components and layers
- D. A strategy that harnesses advanced technologies to measure, analyze, and maintain the fitness of applications
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
SRE defines effective monitoring as comprehensive observability across all layers of a system, including latency, traffic, errors, saturation, dependencies, and infrastructure. The SRE Book states: "Monitoring must offer insight across all system components, enabling teams to rapidly detect and diagnose issues." (SRE Book
- Monitoring Distributed Systems). Observability instrumentation (logs, metrics, traces) provides the necessary depth for reliable digital experience monitoring.
Option B captures this exactly: broad observability across all components and layers.
Option A rejects modern observability practices-contradicting SRE guidance.
Option C is too narrow (network-only).
Option D focuses only on advanced technologies, not comprehensive coverage.
Thus, B is the best answer.
References:
Site Reliability Engineering, Chapter: "Monitoring Distributed Systems." The Site Reliability Workbook, Observability and Monitoring chapters.
NEW QUESTION # 60
Which or the following B6ST identifies a desired objective of the production reachless review (PRR)?
- A. To improve the reliability of the service in the development and testing environment
- B. To validate the service meets international quality standards and frameworks
- C. To ensure the service owner transitions operational accountability to the SRE team
- D. To ensure the service is ready for an SRE team to take over support and care for it
Answer: B
NEW QUESTION # 61
Identify the missing word(s) in the following sentence.
Site reliability engineering is a_________approach to IT operations.
- A. ....software engineering....
- B. ....structural engineering....
- C. ....security engineering....
- D. ....simulation engineering....
Answer: A
NEW QUESTION # 62
If SREs own some sections of a service, but not others, then this organizational approach is known as
__________________
- A. Platform
- B. Slice and dice
- C. Full SRE
- D. Consultant
Answer: B
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
The Slice-and-Dice model is an SRE adoption pattern where the SRE team owns specific portions of a service-typically the most critical, complex, or high-risk components-while development teams own the rest.
From the SRE Workbook, Organizational Models section:
"In the slice-and-dice model, SREs take responsibility for particular portions of a service or system rather than owning the entire thing. This works well when parts of the system require stronger reliability engineering than others." This model is used when:
* Services are large or complex
* Only certain components need SRE-level reliability
* Full SRE ownership is not feasible
Why the other options are incorrect:
* A Consultant # SREs advise; they do not own components
* B Full # SRE fully owns the entire service
* D Platform # SRE builds shared reliability tooling, not owning service slices Thus, C. Slice and dice is the correct answer.
References:
SRE Workbook, "SRE Organizational Patterns"
Site Reliability Engineering Book, "Engagement Models"
NEW QUESTION # 63
Which of the following BEST illustrates the engineering approach for work done within SRE?
- A. An SRE is deploying a solution using an end-to-end pipeline that has been carefully analyzed from the start.
- B. An SRE is designing a solution to eliminate toil and scale up service delivery by learning from other successful solutions.
- C. An SRE is rapidly coding a solution to automate a daily tuning activity by following a set of best practices and principles.
- D. An SRE is resolving an incident as quickly as possible using a well-designed implemented process and knowledge base.
Answer: B
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Google defines SRE as "what happens when you ask a software engineer to design an operations function." (SRE Book - Introduction). The core engineering approach in SRE focuses on:
* Eliminating toil
* Building scalable systems
* Applying software engineering to operational challenges
* Learning from previous solutions and patterns
The SRE Book emphasizes: "SREs focus on designing and engineering solutions that reduce manual operations and scale service delivery." (Chapter: Eliminating Toil). This aligns directly with Option B:
designing a solution to eliminate toil and scale service delivery, informed by prior successful engineering patterns.
Option A focuses only on automating a single tuning activity-not holistic engineering.
Option C describes deployment, not engineering approach to operations.
Option D is about incident response, not engineering strategy.
Thus, B is the best representation of SRE's engineering approach.
References:
Site Reliability Engineering, Chapters: "What Is SRE?", "Eliminating Toil." The Site Reliability Workbook, Engineering scalable solutions.
NEW QUESTION # 64
What is the benefit of strategically burning the Error Budget to zero every month?
- A. It allows for the measurement of capacity and reliability
- B. It can be revised every month as necessary
- C. It allows a balance between velocity and stability
- D. It creates a dialog between strategic partners
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Burning the error budget to zero - strategically, not accidentally - helps ensure the correct balance between release velocity and system stability, which is the fundamental purpose of error budgets. Error budgets exist to encourage a healthy level of risk-taking up to the point where user experience is not impacted.
From the Site Reliability Engineering Book, SLO chapter:
"Error budgets provide a mechanism for balancing innovation and reliability by allowing measured risk- taking while ensuring user expectations are met." The SRE Workbook adds:
"Teams should aim to use their full error budget. Not using it implies missed opportunities to deliver features or improvements." This means that strategically burning the error budget to zero ensures:
* Teams are shipping value at maximum safe velocity
* Reliability goals are still respected
* Risk is managed and intentional
Why other options are incorrect:
* B Capacity measurement is unrelated to error budget consumption.
* C Error budgets should not be continually revised unless business needs change.
* D Conversations with partners may occur, but this is not the primary benefit.
Thus, the correct answer is A.
References:
Site Reliability Engineering Book, "Service Level Objectives"
SRE Workbook, "SLO Engineering"
NEW QUESTION # 65
In which of the following SRE adoption models is reliability a 'first class citizen'?
- A. Platform
- B. Embedded
- C. Full
- D. Consulting
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
In the Full SRE model, reliability becomes a first-class citizen because SREs own the complete operational responsibility for the service and apply SRE principles end-to-end. The Google SRE Book describes several adoption models (Consulting, Embedded, and Full), and only the Full SRE model has SREs fully accountable for reliability outcomes.
From the Site Reliability Engineering Book, Chapter "SRE Engagement Models":
"In the Full SRE model, the SRE team is responsible for end-to-end reliability. Reliability becomes a first- class objective, supported through SLOs, error budgets, and systematic reduction of toil." The Full model includes:
* Full ownership of reliability
* Enforcement of SLOs
* Error budget policies
* Engineering-driven improvement
Other models:
* Consulting # SRE gives guidance but doesn't own reliability
* Embedded # temporary embedding to train teams, not full ownership
* Platform # focuses on shared tooling, not service ownership
Thus, D. Full is correct.
References:
Site Reliability Engineering Book, "Engagement Models"
SRE Workbook, "Adopting SRE in Your Organization"
NEW QUESTION # 66
......
Get Perfect Results with Premium DevOps-SRE Dumps Updated 82 Questions: https://www.trainingquiz.com/DevOps-SRE-practice-quiz.html
DevOps-SRE Dumps PDF 2026 Program Your Preparation EXAM SUCCESS: https://drive.google.com/open?id=1q-vqjZO4picwfmPCtDeLmixpvNMvz08U
