[2026年02月16日] 最新版を今すぐ試そうDevOps-SRE練習テスト問題解答
DevOps-SRE問題集と試験テストエンジン
PeopleCert DevOps-SRE認定は、DevOps環境で働くプロフェッショナルで、サイト信頼性エンジニアリングのスキルを向上させたい人を対象としています。この認定は、サイト信頼性エンジニア、システム管理者、インフラエンジニア、DevOpsエンジニア、ITマネージャーに適しています。また、クラウドベースのシステムの設計や実装に関わるプロフェッショナルにも有益です。
PeopleCert DevOps-SRE認定試験は、サイト信頼性エンジニアリングの主要な概念、原則、および実践に対する候補者の理解を評価します。試験は、サービスレベル契約（SLA）、インシデント管理、変更管理、モニタリングとアラート、容量計画、災害復旧などのトピックをカバーしています。この認定を持つ候補者は、お客様とビジネスのニーズを満たす信頼性の高いシステムを設計、構築、および維持する方法について深い理解を持っています。
PeopleCert DevOps-SRE認定は、DevOps環境でのサイトリライアビリティエンジニア（SRE）のスキルと知識を検証するために設計されています。この認定は、異なるドメインで専門認定を提供するグローバル認定機関であるPeopleCertによって提供されています。この認定は、プロフェッショナルがシステムの信頼性、可用性、拡張性を実装および維持する能力を実証するのに役立ちます。
質問 # 21
Which of the following is the BEST description of a Customer Reliability Engineer (CRE)?
- A. They take a software engineering approach to redesign all cloud services
- B. They use deep engineering expertise to improve the cloud provider's services
- C. They integrate with the customer's operations team to share responsibilities
- D. They work with the cloud provider's SRE team to ship and build new features
正解：C
解説：
Comprehensive and Detailed Explanation From Exact Extract:
Customer Reliability Engineering (CRE) is described in Google's SRE literature as an extension of SRE practices outward to customers who run workloads on cloud platforms. The SRE Book and the SRE Workbook state: "CRE is the practice of sharing SRE principles with customers, working closely with their operations teams, and establishing shared responsibility for reliability." (SRE Workbook - Chapter: Customer Reliability Engineering). A CRE team collaborates directly with customer engineering and operations teams to identify reliability risks, review architectures, and co-manage SLOs, but does not redesign cloud services or build new features.
Option D matches the exact intention: CRE integrates with the customer's operations team to share reliability responsibilities, applying SRE methods to customer systems and ensuring both customer and provider work jointly on reliability goals.
Option A is incorrect-CRE does not redesign cloud services.
Option B misinterprets CRE as improving the provider's internal systems.
Option C incorrectly focuses on feature shipping; CRE is about reliability guidance, not feature delivery.
Thus, D is the correct and SRE-authentic answer.
References:
The Site Reliability Workbook, Chapter: "Customer Reliability Engineering." Google Cloud documentation on CRE practices.
質問 # 22
Before getting into the technical details of a Service Level Objective, what should be done?
- A. Assess what resources would be needed to meet the Service Level Objective
- B. Identify which tasks should be categorized as toil
- C. Start a conversation from the customer's point of view
- D. Evaluate automation capabilities
正解：C
解説：
Comprehensive and Detailed Explanation From Exact Extract:
Before defining any technical details of an SLO, the SRE guidance is clear: the conversation must start from the customer's point of view. SLOs exist to represent what reliability level users genuinely require-not internal assumptions or engineering preferences.
The SRE Workbook, Chapter "Implementing SLOs," states:
"The process must begin by understanding what your users need from the service and what good performance actually means from the user's perspective." Likewise, in the Site Reliability Engineering Book:
"SLOs capture the reliability target that makes sense for the users and the product, which is why defining them must begin with understanding the user experience." This means that SLO development begins with analyzing:
* What users value
* What reliability thresholds they notice
* What failures matter to them most
Only after this understanding is established should teams discuss metrics, thresholds, SLIs, and error budgets.
Why the other options are incorrect:
* A. Identify toil - Relevant to operations, not SLO creation.
* B. Evaluate automation - Important for reducing toil, unrelated to initial SLO definition.
* D. Assess resources - Planning happens after SLO definition, not before.
Thus, the correct answer is C.
References:
SRE Workbook, Chapter: "Implementing SLOs"
Site Reliability Engineering Book, Chapter: "Service Level Objectives"
質問 # 23
Which of the following is the MOST likely outcome when the workforce puts the "parts" before the "whole"?
- A. Increased introversion and decreased efficiency
- B. Increased employee motivation and morale
- C. A focus on common interests and lesser conflicts
- D. A voluntary sharing of resources and information
正解：A
解説：
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.
質問 # 24
Which of the following BEST defines a Service Level Indicator (SLI)?
- A. A subjective assessment of the performance aspects of the level of service required
- B. A subjective measure of the consequences if the level of service is not achieved
- C. A quantitative measure of some aspect of the level of service that is provided
- D. A quantitative target value for aspects of the level of service that are provided
正解：C
解説：
Comprehensive and Detailed Explanation From Exact Extract:
Google's definition is explicit: "An SLI is a carefully defined QUANTITATIVE measure of some aspect of the level of service provided." (SRE Book - Chapter: Service Level Objectives). Examples include error rate, latency, throughput, and availability. SLIs are measurements, not targets-targets are SLOs.
Option D repeats Google's definition almost exactly.
Option C incorrectly describes an SLO (a target), not an SLI.
Options A and B mention subjective assessments-SRE explicitly rejects subjectivity in measurement, stating: "SLIs must be objective and measurable." Thus, D is the correct and SRE-authentic answer.
References:
Site Reliability Engineering, Chapter: "Service Level Objectives."
The Site Reliability Workbook, Chapter: "Implementing SLOs."
質問 # 25
What types of outages must fit into an Error Budget?
- A. Any planned or unplanned outage
- B. Defect fixes
- C. Unplanned incidents
- D. Any change approved by the CAB or decision authority
正解：A
解説：
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.
References:
Site Reliability Engineering Book, "Service Level Objectives"
SRE Workbook, "Implementing SLOs"
質問 # 26
What is the benefit of strategically burning the Error Budget to zero every month?
- A. It can be revised every month as necessary
- B. It creates a dialog between strategic partners
- C. It allows for the measurement of capacity and reliability
- D. It allows a balance between velocity and stability
正解：D
解説：
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"
質問 # 27
An error budget policy is BEST described as being designed to do which of the following?
- A. Shift the locus toward more innovation
- B. Prevent introduction of significant bugs
- C. Send alerts when error budget is at half
- D. Decide when and how to intervene
正解：D
質問 # 28
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 ignored in subsequent months as it is creating the wrong kind of behavior
- B. The Error Budget is reviewed to determine if it was realistic for the product or timeline
- C. The Error Budget is extended for another month to determine if this breach was an anomaly
- D. Sprint planning may only pull post-mortem action items from the backlog
正解：D
解説：
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"
質問 # 29
Which of the following describes work that would be considered "toil"?
- A. Engineering work to add service features
- B. Engineering work that does not add enduring value
- C. Work that has some enduring value but requires manual tasks
- D. Work that is devoid of enduring value
正解：D
解説：
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.
References:
Site Reliability Engineering Book, "Eliminating Toil"
質問 # 30
Which of the following BEST describes the capabilities and scope of DevOps continuous monitoring?
- A. The application of widespread system event monitoring by automating the end-user transactions
- B. The combination of tools and the process for rapid incident detection and response of cloud services
- C. The use of multiple monitoring tools and an event management process for all applications
- D. The deployment of a set of integrated monitoring tools and event thresholds for infrastructure
正解：B
解説：
Comprehensive and Detailed Explanation From Exact Extract:
SRE and DevOps share a common view of continuous monitoring-a holistic approach that enables rapid detection, diagnosis, and response across all parts of the system. The SRE Book states: "Monitoring must enable fast detection of anomalies, quick diagnosis, and effective incident response." Continuous monitoring includes application metrics, infrastructure signals, logs, traces, service health, and user-experience telemetry.
Option B captures this accurately: a combination of tools and processes enabling rapid incident detection and response, especially for cloud services.
Option A is partially correct but too narrow (only end-user transactions).
Option C is generic and does not emphasize continuous or rapid detection.
Option D describes infrastructure monitoring only-not full DevOps/SRE continuous monitoring.
Thus, B is the correct answer.
References:
Site Reliability Engineering, Chapter: "Monitoring Distributed Systems." The Site Reliability Workbook, Observability and Monitoring.
質問 # 31
Which of the following BEST describes the two key elements that an error budget balances?
- A. Innovation and reliability
- B. Features and benefits
- C. Time and money
- D. Risk and reward
正解：A
解説：
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.
質問 # 32
Which of these approaches can alleviate linear scaling toil?
- A. Outsourcing development
- B. Switching cloud providers
- C. Using auto-scaling capabilities
- D. Manual scaling of services
正解：C
解説：
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.
References:
Site Reliability Engineering Book, "Eliminating Toil"
SRE Workbook, "Toil Reduction Strategies"
質問 # 33
An organization has invested heavily in ITIL and ITSM processes.
What's one way that SRE can support ITSM activities?
- A. SRE can help with ITSM compliance activities through automation & engineering
- B. SRE can help the Change Advisory Board (CAB) approve changes by adhering to an Error Budget
- 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
正解：A
解説：
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"
質問 # 34
In a safety culture, engineers are allowed to do more with the production environment without fear of repercussions.
What else do engineers need to do?
- A. Share production incidents on social media
- B. Skip all blameless post-mortems
- C. Be accountable for their actions
- D. Avoid being on-call
正解：C
解説：
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.
References:
Site Reliability Engineering Book, "Postmortem Culture"
SRE Workbook, "Learning from Incidents"
質問 # 35
An organization is experiencing significant turnover of IT operational staff with most not staying more than one year. The HR Director and IT Director are trying to determine why they are having difficulty retaining IT operations professionals.
What could be one of the reasons?
- A. Lack of time for skills development
- B. More time spent managing the backlog than fixing problems
- C. All of the above
- D. Overload and disruptive work patterns
正解：C
解説：
Comprehensive and Detailed Explanation From Exact Extract:
High turnover in IT operations roles is often driven by a combination of factors, not just one. The Google SRE Book, Chapter "Eliminating Toil," outlines that excessive toil, unpredictable work, and overload contribute to burnout and churn:
"Excessive operational workload and interrupt-driven work lead to burnout and high attrition among engineering and operational staff." The SRE Workbook adds:
"Teams overwhelmed with toil struggle to innovate, automate, or develop new skills, creating frustration and increasing turnover." Each option listed represents a recognized driver of burnout in SRE and operations environments:
* Overload and disruptive work patterns are known contributors to burnout.
* Lack of time for skills development demotivates engineers and prevents career growth.
* Backlog-driven cultures force teams into reactive rather than proactive work.
The combination of these factors matches common causes of attrition in operations teams. Therefore, all of the above is the correct answer.
References:
Site Reliability Engineering Book, "Eliminating Toil"
SRE Workbook, "Addressing Operational Overload"
質問 # 36
Microservices are independent services that are developed deployed, and maintained separate^ Which of the following BEST justifies the use of this application architecture?
- A. Modernizing and refactoring legacy applications
- B. Modernizing the user interface of the core system
- C. Building a basic product, fast, as a proof of concept
- D. Creating a simple, lightweight business application
正解：D
質問 # 37
......
2026年最新のFast2test DevOps-SREのPDFで最近更新された問題です：https://jp.fast2test.com/DevOps-SRE-premium-file.html
Peoplecert DevOps-SRE問題集にはリアル試験問題解答：https://drive.google.com/open?id=10Invz93L46ZBKj_LLS18EXTGQzXDWsxA