Why would some Service Level Indicators require client-side data?
Correct Answer: A
Comprehensive and Detailed Explanation From Exact Extract: SLIs must measure user experience, and sometimes server-side metrics alone do not show the full picture. Client-side data may reveal issues such as: * Slow networks * Browser rendering delays * Mobile device limitations * CDN performance issues * Last-mile latency The Site Reliability Engineering Book, Chapter "Service Level Indicators," states: "Server-side metrics do not always fully capture the user experience. In many cases, client-side measurements are required to understand the actual reliability delivered to users." The SRE Workbook reinforces: "Some SLIs require client instrumentation because user-visible performance problems may not be observable from backend systems alone." Why the other options are incorrect: * B SLA negotiation has nothing to do with SLI selection. * C Automation engineering is unrelated to client-side measurement needs. * D Achievability of SLOs does not determine whether client-side data is needed; accuracy of user- experience measurement does. Thus, the correct answer is A. References: Site Reliability Engineering Book, "Service Level Indicators" SRE Workbook, "Choosing the Right SLIs"
Question 37
Which of the following BEST explains how an error budget allows for a maximum change-velocity?
Correct Answer: A
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.
Question 38
Which of the following is BEST described as the role responsible to maintain the live incident state document?
Correct Answer: C
Comprehensive and Detailed Explanation From Exact Extract: In SRE incident management, Google defines several formal roles during a major incident, including Incident Commander (IC), Communications Lead, Operations/Responder, and Planning Specialist. According to the SRE Workbook: "The Planning Lead is responsible for maintaining the source-of-truth incident state document, tracking action items, and ensuring the IC has the current situation overview." (SRE Workbook - Chapter: Incident Management). This document contains timelines, changes, decisions, diagnostics, and action items-all crucial for reducing cognitive load during high-stress situations. Option C-Planning Specialist-is therefore correct. Option A (Logistics Specialist) is not defined as a core SRE incident role. Option B (Communications Lead) manages outward communication, not the live incident log. Option D (Incident Commander) leads the incident but delegates documentation to the planning role. Hence, option C is the only answer that aligns with SRE's defined responsibilities. References: The Site Reliability Workbook, Chapter: "Effective Incident Management." Site Reliability Engineering: How Google Runs Production Systems, Section on incident roles and responsibilities.
Question 39
When of the following BEST completes the definition of a canary release? A new set of features 6 released.....
Correct Answer: A
Question 40
Which of the following communication and collaboration practices BEST contribute to the effectiveness of the SRE team?
Correct Answer: 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.
