Peoplecert DevOps-SRE認定試験問題集には82練習テスト問題があります
最新DevOps-SRE試験問題集には高得点で一発合格
PeopleCert DevOps SRE認定試験は、DevOpsとSREのスキルと知識を検証したいIT専門家向けに設計されています。この試験は、自動化、監視、インシデント管理、継続的な改善など、DevOpsとSREの原則と実践を包括的に理解しています。この認定により、履歴書が強化され、競争力のある雇用市場で際立っています。
PeopleCert DevOps-SRE Examは、DevOpsとSite Reliability Engineeringでキャリアを進めたいITプロフェッショナルにとって貴重な認定資格です。この認定資格は、プロフェッショナルが自身のスキルと知識を潜在的な雇用主に証明するのに役立つだけでなく、組織内での認知度を高めることもできます。さらに、最新のトレンドやベストプラクティスに常に精通していることを保証するために、この認定資格は、プロフェッショナルが常に自身の組織に価値を提供できるようにすることもできます。
質問 # 18
An organization has invested heavily in ITIL and ITSM processes.
What's one way that SRE can support ITSM activities?
- A. SRE can help the Change Advisory Board (CAB) approve changes by adhering to an Error Budget
- B. SRE can help with ITSM compliance activities through automation & engineering
- C. SRE can engineer a configuration management system to capture assets and documentation
- D. SRE can work with ITSM tool vendors to accelerate ticket creation and closure
正解：B
解説：
Comprehensive and Detailed Explanation From Exact Extract:
One of SRE's strengths is using software engineering and automation to reduce manual, process-heavy work.
This aligns perfectly with ITSM goals around repeatability, compliance, and quality.
The SRE Workbook, section "SRE and ITIL Integration," explains:
"SRE can complement ITSM by applying automation and engineering practices to reduce manual process load, increase consistency, and meet compliance requirements." Examples include:
* Automating change processes
* Automating incident response flows
* Improving configuration consistency
* Reducing ticket-driven toil through engineering
Why the other options are incorrect:
* A CAB approvals are not governed by error budgets
* C Ticket acceleration is not the goal of SRE
* D Engineering CMDBs is not the primary mechanism for ITSM alignment
Thus, B is correct.
References:
SRE Workbook, "Modernizing Operations and ITIL Alignment"
質問 # 19
What is the primary difference between SRE and DevOps?
- A. DevOps is mostly for software engineers and SRE is mostly for infrastructure engineers
- B. SRE is an implementation of DevOps but focuses mostly on post-production responsibilities
- C. DevOps encourages closer collaboration between development and operations whereas SRE is about building a silo around production operations
- D. DevOps and SRE are the same thing
正解：B
解説：
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
質問 # 20
"Problem-solving with a group of people with different skillsets''
Which of the following concepts is BEST interred by the above statement?
- A. Coordination
- B. Communication
- C. Cooperation
- D. Collaboration
正解：D
質問 # 21
What does the Westrum model study?
- A. The flow of information and how it affects organizational culture
- B. The flow of communication and how it affects organizational design
- C. The flow of technology in order to deploy faster and more frequently
- D. The flow of critical resources necessary to recover in the event of a major incident
正解：A
解説：
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.
References:
SRE Workbook, "Cultural Change"
Google DORA Research, "Accelerate State of DevOps Report"
Ron Westrum, "A Typology of Organizational Cultures"
質問 # 22
Which of the following is the BEST example of an SRE team that embraces full-service ownership?
- A. The team is responsible for the coding and improvement of the application.
- B. The team is accountable for the application development and performance.
- C. The team is responsible for application performance and reliability aspects.
- D. The team is accountable for coding, shipping, and improving the application.
正解：D
解説：
Comprehensive and Detailed Explanation From Exact Extract:
In SRE practice, "full-service ownership" means the same team is responsible for the service across its entire lifecycle: design, development, deployment, operation, and continuous improvement. Google's Site Reliability Engineering: How Google Runs Production Systems describes SRE as a software-engineering- focused approach to operations, where engineers are responsible not only for writing the code but also for running it in production and improving its reliability over time. This aligns with the "you build it, you run it" model, which removes the traditional wall between development and operations and makes one team accountable for the whole service.
Option D - "The team is accountable for coding, shipping, and improving the application" - best matches this concept because it explicitly includes building (coding), releasing (shipping), and iterating (improving).
Options A and B do not clearly include operational responsibility, and option C narrows the focus only to performance and reliability, omitting ownership of development and releases. Therefore, D most accurately reflects full-service ownership as described in SRE literature.
References (conceptual alignment):
* Site Reliability Engineering: How Google Runs Production Systems, Betsy Beyer et al., O'Reilly, particularly:
* Introduction & "What Is Site Reliability Engineering?"
* "Introduction to SRE at Google" and discussions of dev/ops ownership boundaries.
質問 # 23
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. 3 and 4
- B. 2 and 3
- C. 1 and 4
- D. 1 and 2
正解：D
質問 # 24
Which of the following communication and collaboration practices BEST contribute to the effectiveness of the SRE team?
- A. Team members should manage their own data discretely.
- B. Data is flowing freely within and around the SRE team.
- C. Data in SRE should be managed separately from others.
- D. Project managers share limited data only upon request.
正解：B
解説：
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.
質問 # 25
Following a major outage, an analysis of the outage is conducted. This BEST describes an example of which of the following?
- A. A follow-up culture
- B. A problem culture
- C. A major incident culture
- D. A postmortem culture
正解：D
解説：
Comprehensive and Detailed Explanation From Exact Extract:
Google's SRE approach emphasizes a blameless postmortem culture as a core learning mechanism. After a major outage, SRE teams conduct structured analyses to understand the root causes, contributing factors, and systemic weaknesses. The SRE Book defines this culture explicitly: "Postmortems are written analyses following incidents, designed to capture what happened, why it happened, and how to prevent the issue from recurring." (SRE Book - Chapter: Postmortem Culture). This learning-focused approach reduces blame, increases resilience, and improves future reliability.
Option C aligns exactly with this principle.
Option A (follow-up culture) is vague and not an SRE term.
Option B (major incident culture) refers to incident handling, not learning afterward.
Option D (problem culture) is unrelated to SRE's structured post-incident learning.
Thus, C is correct.
References:
Site Reliability Engineering, Chapter: "Postmortem Culture: Learning From Failure." The Site Reliability Workbook, Incident Review processes.
質問 # 26
When outages are repetitive and similar, they become a form of toil.
Which of the following describes the MOST compelling reason to adopt advanced technologies and artificial intelligence (AI)?
- A. To increase the mean time to restore services (MTRS)
- B. To increase reliability and achieve perfect MTRS
- C. To increase the mean time to repair services (MTTR)
- D. To increase reliability by reducing MTTR and MTRS
正解：D
解説：
Comprehensive and Detailed Explanation From Exact Extract:
SRE defines toil as "manual, repetitive, automatable, tactical work tied to running a service" (SRE Book - Eliminating Toil). Repetitive outages are specifically noted as a form of operational toil. The SRE Book and SRE Workbook emphasize adopting automation, intelligent tooling, and machine-learning-assisted systems to reduce toil and decrease Mean Time to Repair (MTTR) and Mean Time to Restore Service (MTRS). The books state: "Reducing MTTR directly increases system reliability more effectively than attempting to eliminate all failures." (SRE Book - Chapter: Managing Incidents).
AI and advanced automation help detect issues faster, classify patterns, trigger automated remediation, and reduce human intervention-delivering reliability gains through faster repair rather than perfect uptime.
Option A is the only option aligned with SRE's reliability philosophy.
Options B and C incorrectly suggest increasing MTTR/MTRS.
Option D refers to "perfect MTRS," which is impossible and contradicts SRE's acceptance of failure.
Thus, A is correct.
References:
Site Reliability Engineering, Chapter: "Eliminating Toil," "Managing Incidents." The Site Reliability Workbook, ML/automation case studies.
質問 # 27
Which of the following BEST defines the golden signal for errors?
- A. The time it takes to service successful as well as failed requests
- B. The demand that is placed on your system by me volume of requests
- C. The rate of failed requests either explicitly implicitly, or by policy
- D. The percent of capacity used by your system for current requests
正解：C
質問 # 28
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 instruments observability and provides monitoring insights across all components and layers
- B. A strategy that uses traditional and familiar monitoring tools rather than advanced artificial intelligence
- C. A strategy that harnesses advanced technologies to measure, analyze, and maintain the fitness of applications
- D. A strategy that focuses on monitoring and discovering useful patterns in the performance of all active networks
正解：A
解説：
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.
質問 # 29
Which of the following BEST describe the characteristics of a product team?
* They are small and collaborative
* They have cross-functional skillsets
* They do not share responsibilities
* They discourage any feedback
- A. 3 and 4
- B. 2 and 3
- C. 1 and 4
- D. 1 and 2
正解：D
解説：
Comprehensive and Detailed Explanation From Exact Extract:
Modern SRE-aligned organizations use small, cross-functional product teams capable of owning design, development, testing, and operational reliability. The SRE Book emphasizes: "Effective service ownership arises from small, autonomous teams with diverse skillsets and strong collaboration habits." These teams share responsibility, encourage feedback, and maintain open communication to meet reliability goals.
Option A correctly identifies the two positive characteristics:
* Small and collaborative
* Cross-functional skillsets
Options 3 and 4 represent dysfunctional behaviors-SRE literature explicitly discourages responsibility silos and discouraging feedback, as these reduce reliability and slow incident learning.
Thus, A is the correct answer.
References:
Site Reliability Engineering, Chapter: "Organization and Culture."
The Site Reliability Workbook, discussions on product-oriented team structures.
質問 # 30
Which of the following BEST describes a business continuity plan?
- A. The management of risks that seriously affect the organization
- B. The way the organization maintains operations during a disaster
- C. The way that data, files, applications, and systems are restored
- D. The activity of returning a configuration item back to normal
正解：B
解説：
Comprehensive and Detailed Explanation From Exact Extract:
A Business Continuity Plan (BCP) is a critical component of organizational resilience. While not unique to SRE, SRE strongly intersects with continuity planning because reliable systems must continue functioning during disruptions. According to Google's SRE principles, reliability extends beyond typical outages and includes "ensuring services continue to operate even under exceptional conditions." (SRE Book - Chapter:
Addressing Risks). A business continuity plan specifically outlines how essential operations are maintained during major disruptions such as natural disasters, data center outages, or large-scale system failures.
Option A-"The way the organization maintains operations during a disaster"-matches the formal definition of BCP.
Option B refers to disaster recovery (DR), which is separate; DR focuses on restoring systems, not maintaining ongoing operations.
Option C refers to configuration management activities, not continuity.
Option D refers to risk management, which informs BCP but does not define it.
Therefore, A is the correct answer because it directly reflects the purpose of continuity planning as supported by reliability-focused guidance.
References:
Site Reliability Engineering: How Google Runs Production Systems, Chapters: "Addressing Risks,"
"Managing Critical State."
The Site Reliability Workbook, Sections discussing resilience and continuity in distributed systems.
質問 # 31
Which of the following BEST describes the relationship between service level objectives and service level indicators?
- A. Service level objectives are the performance metrics for service level indicators
- B. Service level indicators are the performance targets for service level objectives
- C. Service level indicators are the measurements for the service level objectives
- D. Service level objectives are the measurements foe the service level indicators
正解：C
質問 # 32
Which of the following is the MOST likely outcome when the workforce puts the "parts" before the "whole"?
- A. Increased employee motivation and morale
- B. Increased introversion and decreased efficiency
- C. A voluntary sharing of resources and information
- D. A focus on common interests and lesser conflicts
正解：B
解説：
Comprehensive and Detailed Explanation From Exact Extract:
SRE emphasizes organizational alignment and collaboration, warning against siloed thinking. The SRE Book highlights: "Local optimizations at the expense of the broader system lead to inefficiency, misalignment, and reduced reliability." When individuals or teams focus only on their own "parts" instead of shared goals ("the whole"), it results in decreased cross-team communication, isolation, operational friction, and reduced efficiency.
Option B captures this SRE-documented outcome: increased introversion (siloing) and decreased efficiency.
Option A and D describe positive outcomes that contradict SRE principles of collaboration.
Option C implies healthy sharing, which does not result from silo-first behavior.
Thus, B is correct.
References:
Site Reliability Engineering, Chapter: "Organization and Culture."
The Site Reliability Workbook, sections on collaboration, alignment, and anti-silo culture.
質問 # 33
Which of the following BEST explains how an error budget allows for a maximum change-velocity?
- A. Developers rush to do development work if the budget is high and slow down when it is low.
- B. Developers must slow down feature changes in line with the percentage the budget is used.
- C. Developers focus only on new feature work versus operational work if the budget is empty.
- D. Developers can focus on pushing out feature changes while the error budget remains high.
正解：D
解説：
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.
質問 # 34
Which of the following is the definition for Application Performance Management (APM)?
- A. Ways for engineers to communicate quantitative data about systems
- B. The use of a hardware or software component to monitor system resources and performance of a computer system
- C. The monitoring and management of performance and availability of software applications
- D. The highly automated communications process by which measurements are made and other data collected at remote or inaccessible points and transmitted to receiving equipment for monitoring
正解：C
解説：
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.
References:
SRE Workbook, "Monitoring"
Google Cloud Operations Suite (APM documentation)
質問 # 35
Where should an organization store versioned and signed artifacts that are used to deploy system components?
- A. In a Subversion source code repository
- B. In a Definitive Media Library (DML)
- C. In the Configuration Management System (CMS)
- D. In a secure artifact repository
正解：D
解説：
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.
References:
Site Reliability Engineering Book, "Release Engineering"
SRE Workbook, "Safe Deployments"
Google Cloud Build & Artifact Registry documentation
質問 # 36
......
無料提供中DevOps-SREブレーン問題集とDevOps-SREリアル試験問題を試そう：https://www.passtest.jp/Peoplecert/DevOps-SRE-shiken.html
Peoplecert DevOps-SRE実際の問題とブレーン問題集：https://drive.google.com/open?id=1j4ycYRxmoCMScaVdzbzgonmRE84WP6El