A: To spend 50% of a SRE's time on operational tasks and 50% of the time on development tasks to reduce toil
B: To ensure that Service Level Objectives are consistently met through monitoring and observability
C: To create highly reliable post-deployment operational systems that align with DevOps and Agile
D: To create ultra-scalable and highly reliable distributed software systems
正解：D
Explanation: Comprehensive and Detailed Explanation From Exact Extract: The goal of Site Reliability Engineering (SRE) is to create ultra-scalable and highly reliable distributed software systems. This principle is clearly articulated in the foundational text of SRE, the Google Site Reliability Engineering book. From Chapter 1: Introduction of the Site Reliability Engineering book: "SRE is what happens when you ask a software engineer to design an operations team. Our approach to service management is rooted in our belief that engineering work to create scalable and highly reliable systems is critical to the success of modern software." ― Site Reliability Engineering Book, Chapter 1 This statement establishes that building and maintaining scalable, reliable systems is the core mission of SRE. While concepts like reducing toil (option A), implementing SLOs (option B), and aligning with DevOps (option C) are vital components of the SRE practice, they support the overarching goal ― which is option D. Therefore, the correct answer is D: To create ultra-scalable and highly reliable distributed software systems. Reference: Site Reliability Engineering Book ― Chapter 1: Introduction https://sre.google/books/ The Site Reliability Workbook ― Google SRE Google Cloud Blog: An Overview of SRE
サンプル問題 2： What is the primary difference between SRE and DevOps?
A: SRE is an implementation of DevOps but focuses mostly on post-production responsibilities
B: DevOps is mostly for software engineers and SRE is mostly for infrastructure engineers
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
正解：A
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. Reference: 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
サンプル問題 3： Which of the following is NOT a SRE principle?
A: Operations is a software problem
B: Automate what is currently done manually
C: Toil is not important work
D: Reduce the cost of failure
正解：C
Explanation: Comprehensive and Detailed Explanation From Exact Extract: The statement “Toil is not important work” is NOT an SRE principle. This is incorrect based on the official Google SRE documentation. In the Site Reliability Engineering Book, toil is treated as a critical concept, because identifying and reducing toil directly enables reliability improvements and more engineering-focused work. The SRE book emphasizes that toil must be taken seriously and systematically reduced, but never dismissed. From the SRE Book, Chapter “Eliminating Toil”: “Toil is the kind of work tied to running a production service that tends to be manual, repetitive, automatable, tactical, with no enduring value, and that scales linearly as a service grows.” The SRE book further emphasizes: “SRE teams should measure toil, track it, and make constant efforts to reduce it.” This demonstrates that toil is significant and should not be ignored. Therefore, any suggestion that “toil is not important work” contradicts the documentation. The other answer choices are actual SRE principles: Operations is a software problem ― From SRE Book Introduction: “SRE’s approach starts with the belief that operations is fundamentally a software engineering problem.” Automate what is currently done manually ― Automation is a central SRE philosophy to reduce toil. Reduce the cost of failure ― Error budgets and controlled risk-taking are core SRE concepts designed to reduce the cost of failure. Thus, the only option that is NOT an SRE principle is C. Reference: Site Reliability Engineering Book, “Introduction” and “Eliminating Toil” Chapters SRE Workbook, “Eliminating Toil” Section
Peoplecert DevOps-SRE試験準備をしていますか？それとも自分は全部できそうです。復習する必要がないと思いますか？それとも自分は何もできないような気がします。どうすればいいでしょうか？実は、この問題を解決するのは難しくないです。勉強者がやるべきのは分解分析をマスターすることです。ここではDevOps-SRE問題集を使って学習中の課題を確認し、知識を整理してPeopleCert DevOps Site Reliability Engineer (SRE)試験の準備を進めます。
