PeopleCert Updated DevOps-SRE Exam Questions and Answers by avery

Comprehensive and Detailed Explanation From Exact Extract:

A Service Level Indicator (SLI) is a measurement of some aspect of reliability (e.g., latency, availability, quality). One of its defining characteristics is that it must be measured over a specific time window. Without a time horizon, the SLI has no actionable meaning.

From the Site Reliability Engineering Book, Chapter “Service Level Indicators”:

“An SLI is a quantitative measure of some aspect of the level of service that is provided. SLIs are evaluated over a specific period of time in order to understand reliability as experienced by the user.”

The SRE Workbook further states:

“Every SLI must define a measurement window. Without a time horizon, the indicator cannot be used to calculate SLO compliance.”

Why the other options are incorrect:

A SLIs do not need to appear in an SLA; SLAs are external contracts, SLOs/SLIs are internal engineering tools.

B SLIs may include client-side, server-side, or network metrics depending on what reflects user experience.

D SLI agreement is not defined by SRE vs. Agile teams; it is defined by business and user need.

Thus, the correct answer is C.

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.

Comprehensive and Detailed Explanation From Exact Extract:

Availability is the most widely tracked and commonly understood SLO across nearly all digital services. It measures whether users are able to successfully access and use the system. Because unavailability directly impacts user experience, revenue, trust, and reliability, it is the primary SLO used across industries.

The Site Reliability Engineering Book, Chapter “Service Level Objectives,” states:

“Availability is one of the most common and important SLOs since it reflects the basic ability of the service to function for users.”

The SRE Workbook also notes:

“Availability targets (e.g., 99.9%, 99.99%) are the most widely used form of SLOs and form the foundation of error budget policies.”

While performance SLOs are also common, availability SLOs are almost universal and foundational.

Thus, D. Availability is the correct answer.

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.