厳密検証されたDevOps-SRE試験問題集と解答で無料提供のDevOps-SRE問題と正解付き
あなたを合格させるDevOps-SRE問題集で無料最新Peoplecert練習テスト
PeopleCert DevOps-SRE Examは、DevOpsとSite Reliability Engineeringでキャリアを進めたいITプロフェッショナルにとって貴重な認定資格です。この認定資格は、プロフェッショナルが自身のスキルと知識を潜在的な雇用主に証明するのに役立つだけでなく、組織内での認知度を高めることもできます。さらに、最新のトレンドやベストプラクティスに常に精通していることを保証するために、この認定資格は、プロフェッショナルが常に自身の組織に価値を提供できるようにすることもできます。
認定試験では、DevOpsおよびサイトの信頼性エンジニアリングの概念、自動化およびオーケストレーションツール、監視と警告戦略、インシデント管理慣行など、さまざまなトピックをカバーしています。この試験は、概念に関する候補者の知識をテストする理論的部分と、実際のシナリオでこれらの概念を適用する候補者の能力を評価する実用的な部分の2つの部分に分けられます。この認定は、スキルを向上させ、DevOpsとサイトの信頼性エンジニアリングの分野の最新トレンドを最新の状態に保ちたい専門家に最適です。
質問 # 22
An organization has been adopting DevOps practices including Continuous Integration and Continuous Delivery pipelines.
How would implementing SRE improve DevOps for this organization?
- A. Infrastructure as Code will force organizations to move to the cloud
- B. Continuous delivery pipelines become redundant
- C. Continuous delivery pipelines will go further and extend into production
- D. DevOps engineers will be forced to become SREs
正解：C
解説：
Comprehensive and Detailed Explanation From Exact Extract:
SRE strengthens DevOps by adding reliability engineering, SLOs, error budgets, and production-focused automation. One key improvement is that the CI/CD pipeline extends safely into production using automated, tested, reliable deployment mechanisms.
The Site Reliability Engineering Book, "Release Engineering" chapter states:
"SRE complements DevOps by creating safe pathways for automated production deployments through engineering practices such as canarying, automation, and release gates." The SRE Workbook adds:
"SRE helps mature DevOps pipelines so they can operate safely in production, enabling continuous delivery to reach all the way through deployment." Why the other options are incorrect:
* B SRE makes CD more necessary, not redundant
* C SRE does not replace DevOps engineers
* D IaC does not require moving to the cloud
Thus, the correct answer is A.
References:
Site Reliability Engineering Book, "Release Engineering"
SRE Workbook, "Safe Deployments and CI/CD Integration"
質問 # 23
Which of the following BEST describes me two key elements that an error budget balances?
- A. Risk and reward
- B. Time and money
- C. Innovation and reliability
- D. Features and benefits
正解：C
質問 # 24
The value of data-driven measurements can be MOST accurately explained by which of the following?
- A. Objectives can only be appropriately designed when based upon actual data
- B. An analysis and understanding of data helps to ensure fact-based decision-making
- C. The garnering of data will provide an the necessary facts to enable better decisions
- D. Data mining enables an organization to determine the legitimacy of all metrics
正解：B
質問 # 25
Known workarounds represent what type of toil?
- A. Tactical
- B. Linear scaling
- C. No enduring value
- D. Automatable
正解：C
解説：
Comprehensive and Detailed Explanation From Exact Extract:
Known workarounds represent toil that has no enduring value, one of the key characteristics of toil defined by the SRE framework.
From the Site Reliability Engineering Book, Chapter "Eliminating Toil":
"Toil is work that is manual, repetitive, automatable, tactical, has no enduring value, and scales linearly with service size." Known workarounds fit this definition because:
* They solve the same recurring problems repeatedly
* They do not permanently fix the underlying issue
* They consume engineer time without contributing long-term improvements These activities lack enduring value and should be eliminated through automation or engineering fixes.
Why the other options are incorrect:
* A. Linear scaling - Many forms of toil scale linearly, but this does not specifically describe workarounds.
* B. Tactical - Tactical means short-term, but not all tactical work is a workaround.
* C. Automatable - While some workarounds can be automated, not all are.
* D. No enduring value - This is the defining trait of workaround-type toil.
Therefore, option D is correct.
References:
Site Reliability Engineering Book, "Eliminating Toil"
SRE Workbook, "Toil Reduction Strategies"
質問 # 26
An error budget policy is BEST described as being designed to do which of the following?
- A. Prevent introduction of significant bugs
- B. Send alerts when error budget is at half
- C. Shift the locus toward more innovation
- D. Decide when and how to intervene
正解：D
質問 # 27
Which of the following terms is BEST described by the definition below?
"The probability that the system will meet certain performance standards and yield correct output for a specific time."
- A. Availability
- B. Durability
- C. Reliability
- D. Throughput
正解：C
解説：
Comprehensive and Detailed Explanation From Exact Extract:
The SRE Book defines reliability as: "the probability that a system will perform its intended function correctly for a specified period of time." (SRE Book - Introduction). Reliability focuses on correctness and consistent performance, not simply uptime. Availability (option A) refers to system uptime or accessibility.
Durability (option C) refers to long-term data persistence. Throughput (option D) measures volume of work processed over time.
Because the definition explicitly mentions probability of meeting performance standards and correct output over time, it directly matches the SRE definition of reliability.
Thus, B is correct.
References:
Site Reliability Engineering, Introduction section on reliability definitions.
The Site Reliability Workbook, Reliability fundamentals.
質問 # 28
Which of the following BEST explains now an error budget allows for a maximum change velocity?
- A. Developers rush to do development work if me budget is high and stow down when it is low.
- B. Developers focus only on new feature work versus operational work if the budget is empty.
- 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.
正解：D
質問 # 29
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 repair services (MTTR)
- B. To increase the mean time to restore services (MTRS)
- C. To increase reliability and achieve perfect MTRS
- D. To increase reliability by reducing MTTR and MTRS
正解：D
質問 # 30
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 focus only on new feature work versus operational work if the budget is empty.
- 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 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.
質問 # 31
Identify the missing word(s) in the following sentence:
Site reliability engineering is a _________ approach to IT operations.
- A. structural engineering
- B. software engineering
- C. security engineering
- D. simulation engineering
正解：B
解説：
Comprehensive and Detailed Explanation From Exact Extract:
Google's SRE definition is explicit: "Site Reliability Engineering is what happens when you ask a software engineer to design an operations team." (SRE Book - Introduction). This clearly defines SRE as a software engineering approach applied to operational problems. The goal is to use software techniques-automation, coding, testing, version control, CI/CD, observability-to improve reliability and reduce toil. The book emphasizes: "SRE applies software engineering to operations work." (SRE Book - What Is SRE?).
Option C is the only answer fully aligned with the official definition.
Options A, B, and D do not correspond to the SRE definition provided by Google.
Thus, the correct missing phrase is software engineering.
References:
Site Reliability Engineering: How Google Runs Production Systems, Introduction and Chapter: "What is SRE?"
質問 # 32
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 repair services (MTTR)
- B. To increase the mean time to restore services (MTRS)
- C. To increase reliability and achieve perfect MTRS
- 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.
質問 # 33
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 postmortem culture
- C. A major incident culture
- D. A problem culture
正解：B
解説：
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.
質問 # 34
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. 2 and 3
- B. 1 and 4
- C. 3 and 4
- D. 1 and 2
正解：D
質問 # 35
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 quantitative target value for aspects of the level of service that are provided
- C. A quantitative measure of some aspect of the level of service that is provided
- D. A subjective measure of the consequences if the level of service is not achieved
正解：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."
質問 # 36
"Problem-solving with a group of people with different skillsets''
Which of the following concepts is BEST interred by the above statement?
- A. Communication
- B. Coordination
- C. Cooperation
- D. Collaboration
正解：D
質問 # 37
Which of the following BEST defines the golden signal for errors?
- A. The percent of capacity used by your system for current requests
- B. The time it takes to service successful as well as failed requests
- C. The demand that is placed on your system by me volume of requests
- D. The rate of failed requests either explicitly implicitly, or by policy
正解：D
質問 # 38
Which of me following BEST describes an advantage of a container-based structure?
- A. Software runs much more efficiently in containers because of the* ability to run on virtual machines
- B. The portability created by containers enables software to run independently of the host operating system
- C. The security of applications in containers is simplified because they share the security of the host system
- D. The lightweight nature of containers requires fewer developers to actually create the software code
正解：B
質問 # 39
Which of the following BEST describes the capabilities and scope of DevOps continuous monitoring?
- A. The use of multiple monitoring tools and an eventmanagement process for all applications
- B. The combination of tools and the process for a rapid incident detection and response of cloud services
- C. The application of widespread system event monitoring by automating the end user transactions
- D. The deployment of a set of integrated monitoring tools and event thresholds for infrastructure
正解：D
質問 # 40
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. Overload and disruptive work patterns
- B. All of the above
- C. Lack of time for skills development
- D. More time spent managing the backlog than fixing problems
正解：B
解説：
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"
質問 # 41
Which of the following BEST illustrates the role of a launch coordination engineer?
- A. A software developer focused on building efficient application startup and shutdown performance
- B. A software engineer who acts as a consultant and liaison between the parties involved in a launch
- C. A site reliability engineer focused on stabilizing manual tuning and event monitoring activities
- D. A server engineer focused on rolling out a dynamically scaled application hosting environment
正解：B
解説：
Comprehensive and Detailed Explanation From Exact Extract:
Google's SRE model includes the role of Launch Coordination Engineer (LCE), described in the SRE Book as: "an engineer who serves as the central liaison between product teams, SRE, and other stakeholders to ensure safe and reliable launches." (SRE Book - Chapter: Production Environment & Launch Coordination).
Their responsibilities include assessing launch readiness, ensuring SLOs are defined, facilitating cross-team communication, and managing risk associated with new service rollouts.
Option C precisely reflects this role: acting as a consultant and liaison across all parties involved in a launch.
Option A focuses on server engineering, which is not the focus of LCE.
Option B describes application-level performance work, unrelated to cross-team launch facilitation.
Option D describes operational tuning, not coordination.
Thus, C is the correct answer, capturing the SRE-defined launch coordination function.
References:
Site Reliability Engineering: How Google Runs Production Systems, Chapter: "Handling Overload and Launch Coordination." The Site Reliability Workbook, Sections on production readiness and launch processes.
質問 # 42
Which of the following is the LEAST useful metric when working to improve antifragility?
- A. Service Level Objective
- B. Recovery Point Objective
- C. Mean Time To Detect
- D. Deployment frequency
正解：D
解説：
Comprehensive and Detailed Explanation From Exact Extract:
Anti-fragility focuses on an organization's ability to respond, adapt, learn, and recover from incidents. The most useful metrics relate to incident detection, response, reliability, and recovery. Deployment frequency, while important in DevOps and DORA metrics, does not directly measure anti-fragility.
From the SRE Workbook, Incident Response section:
"Improving antifragility requires better detection, better recovery mechanisms, and clear reliability goals." Key metrics relevant to anti-fragility:
* MTTD (Mean Time To Detect) - quicker detection improves resilience
* MTTR/RPO - recoverability measures
* SLOs - define acceptable reliability thresholds and guide learning
Deployment frequency primarily measures delivery velocity, not resilience.
The Site Reliability Engineering Book emphasizes:
"Antifragility is improved by learning from incidents and strengthening recovery mechanisms rather than by increasing release cadence." Why other options are correct for anti-fragility:
* A. Mean Time To Detect - critical for detecting failures quickly
* B. SLOs - define boundaries for reliability and failure tolerance
* D. Recovery Point Objective - measures potential loss during failures Thus, C is the least useful metric for improving antifragility.
References:
SRE Workbook, "Incident Response"
Site Reliability Engineering Book, "Postmortem Culture"
Google DORA Research (role of deployment frequency vs. resilience metrics)
質問 # 43
Which of the following terms is BEST described by the definition below?
The probability that the system will meet certain performance standards and yield correct output for a specific time.
- A. Availability
- B. Durability
- C. Reliability
- D. Throughput
正解：C
質問 # 44
In a blameless post-mortem, those involved report
- A. Without fear of retribution
- B. Assumptions they had made
- C. Both A and B
- D. Using testing data
正解：C
解説：
Comprehensive and Detailed Explanation From Exact Extract:
A blameless post-mortem is a foundational SRE practice that encourages truthful, detailed reporting after an incident. The purpose is to learn, not punish. Google SRE emphasizes that engineers must feel psychologically safe to report what they did, what they assumed, and why they made those decisions.
From the Site Reliability Engineering Book, Chapter "Postmortem Culture":
"Blameless postmortems encourage engineers to share the full details of their actions and assumptions without fear of punishment, enabling learning and preventing repeated failures." The book further states:
"Understanding the assumptions made during an incident is critical to uncovering systemic issues." Thus:
* Engineers must report without fear of retribution
* They must report assumptions and decisions made during the incident
Therefore, the correct answer is C. Both A and B.
Why the other options are insufficient:
* A Only partially correct
* B Only partially correct
* D Testing data may be included, but it is not the defining feature of blameless postmortems References:
Site Reliability Engineering Book, "Postmortem Culture"
SRE Workbook, "Learning from Incidents"
質問 # 45
......
無料でゲット！高評価Peoplecert DevOps-SRE試験問題集今すぐダウンロード！：https://www.passtest.jp/Peoplecert/DevOps-SRE-shiken.html
DevOps-SRE試験問題集合格には最新なテスト問題集：https://drive.google.com/open?id=1GphPczNjvvqYn-SrKothNGLY5VOfiBT3