SRE Reliability Principles & Service Level Objectives 1

Question 1

What is the primary purpose of setting Service Level Objectives (SLOs)?

Accepted Answer

To align business and reliability expectations

Answer

Service Level Objectives (SLOs) are targets for a service's reliability, defining an acceptable level of performance or availability. Their primary purpose is to create a shared understanding and alignment between the service provider (SRE team) and business stakeholders regarding what constitutes 'good enough' reliability. This alignment helps in making informed decisions about resource allocation, feature development, and operational priorities.

Question 2

What metric represents the frequency of successful system responses?

Accepted Answer

Availability

Answer

Availability is a key Service Level Indicator (SLI) that measures the proportion of time a system or service is operational and capable of performing its intended function. It is typically expressed as a percentage of successful requests or uptime over a given period. High availability indicates a system that is consistently accessible and responsive to user requests, representing the frequency of successful system responses.

Question 3

How does an error budget help SRE teams?

Accepted Answer

It defines the acceptable level of unreliability

Answer

An error budget is the maximum amount of acceptable downtime or unreliability a service can experience over a specific period, derived directly from its Service Level Objectives (SLOs). It provides a quantitative measure of how much 'unreliability' the system can tolerate before violating its SLOs. This budget allows SRE teams to balance the need for new feature development with the imperative of maintaining system reliability, enabling calculated risks.

Question 4

Which of the following is an example of a latency metric?

Accepted Answer

Request response time

Answer

Latency refers to the delay between a user's request and the system's response. Request response time directly measures this delay, indicating how quickly a service processes and returns a result for a given request. It is a crucial metric for user experience, as high latency can lead to frustration and perceived slowness, making it a direct example of a latency metric.

Question 5

Why should SLOs be reviewed periodically?

Accepted Answer

To align with changing requirements and reliability targets

Answer

SLOs are not static; they should evolve as the business, user expectations, and system capabilities change over time. Periodic review ensures that SLOs remain relevant and accurately reflect current business objectives and user needs. This dynamic approach allows SRE teams to adapt their reliability efforts and resource allocation to new priorities and technological advancements, maintaining their effectiveness.

(SRE) Site Reliability Engineering Foundation Certification Practice Test

(SRE) Site Reliability Engineering Foundation Certification Practice Test

SRE Reliability Principles & Service Level Objectives 1