Identify the defense-in-depth (DiD) layer where data flows in from, and out to, other networks, including the Internet.
Correct Answer: C
Comprehensive and Detailed Explanation From Exact Extract: Defense-in-Depth (DiD) is a layered security strategy referenced in SRE's discussions of secure infrastructure and resilience. The perimeter layer is responsible for controlling and monitoring traffic flowing into and out of the network from external sources, such as the public Internet. This includes firewalls, intrusion detection systems, load balancers, and boundary network controls. While SRE focuses primarily on reliability, the SRE Book stresses the importance of resilient system boundaries: "Perimeter protections are critical where external traffic enters the system." (SRE Book - Security and Infrastructure considerations). Option C correctly identifies the Perimeter Layer as the network boundary where data flows in/out from other networks-including the Internet. Option A (Host layer) secures individual machines. Option B (Physical layer) refers to hardware, power, racks, etc. Option D (Data layer) protects stored data, not ingress/egress traffic. Thus, C is correct. References: Site Reliability Engineering, discussions on system boundaries and secure infrastructure. Defense-in-Depth model (industry standard, aligned with SRE security considerations).
Question 22
Which of the followingcommunication and collaboration practices BEST contribute to the effectiveness of the SRE team?
Correct Answer: D
Question 23
"Problem-solving with a group of people with different skillsets." Which of the following concepts is BEST inferred by the above statement?
Correct Answer: B
Comprehensive and Detailed Explanation From Exact Extract: The SRE model heavily emphasizes cross-functional teamwork. In the SRE Workbook and chapters addressing incident management, Google defines collaboration as "bringing together individuals with diverse expertise to jointly solve problems and make decisions." Collaboration implies active engagement, shared goals, and joint execution-exactly what the statement describes. Option B, Collaboration, fits perfectly because effective problem-solving during incidents, launches, or reliability engineering work requires engineers from multiple disciplines (e.g., SRE, developers, network teams, product teams) to work together directly. Option A (Coordination) is more about task alignment, not joint problem-solving. Option C (Communication) is necessary but insufficient for solving problems together. Option D (Cooperation) implies helpfulness, not necessarily integrated problem-solving. Thus, B is the correct concept. References: The Site Reliability Workbook, Chapter: "Effective Incident Management." Site Reliability Engineering, Sections on teamwork and cross-functional collaboration.
Question 24
Which type of engineering work will reduce toil within the service?
Correct Answer: D
Comprehensive and Detailed Explanation From Exact Extract: Toil-reduction engineering focuses on making the service itself easier to operate. The most direct way to achieve this is through internal automation - automation built into the service that eliminates repetitive, manual operational tasks. The Site Reliability Engineering Book, Chapter "Eliminating Toil," states: "Automation that replaces manual, repetitive operational tasks is the primary mechanism for reducing toil. The most effective form of toil reduction is automation that is integrated directly into the service itself." The SRE Workbook reinforces: "Internal automation contributes directly to service reliability and reduces the operational burden by ensuring that manual tasks are permanently removed." Why the other options are not the best answer: * A Continuous delivery pipelines reduce release friction but do not directly remove service-operational toil. * B External scripts and tools help but are less effective and harder to maintain than internal automation. * C Scalable infrastructure reduces linear-scaling toil but does not address broader operational burdens. Thus, the correct answer is D. References: Site Reliability Engineering Book, "Eliminating Toil" SRE Workbook, "Toil Reduction Approaches"
Question 25
Which of the following BEST illustrates the engineering approach for work done within SRE?
Correct Answer: B
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.
