SRE On-Call Practices & Runbooks 4

Question 1

What is a 'canary alert' in the context of on-call alerting strategy?

Accepted Answer

A synthetic probe alert used to validate that the alerting pipeline itself is functional

Answer

A canary alert is a deliberately triggered test alert that verifies the end-to-end alerting and paging pipeline is working correctly.

Question 2

Which practice helps ensure runbooks remain accurate over time?

Accepted Answer

Requiring runbook review as part of every post-mortem and system change

Answer

Linking runbook reviews to post-mortems and change processes ensures documentation is updated when systems or failure patterns change.

Question 3

An alert fires at 3 AM and the on-call engineer determines no user impact exists. What is the appropriate action?

Accepted Answer

Acknowledge, document the lack of impact, and create a ticket to tune the alert

Answer

Non-impacting alerts should be acknowledged and documented, then a follow-up ticket created to reduce noise — silencing without investigation risks missing real issues.

Question 4

What is 'toil' in SRE terminology as it relates to on-call work?

Accepted Answer

Repetitive, manual, and automatable operational work that scales with service growth

Answer

Toil is repetitive manual work tied to running a production service that provides no enduring value and grows with the system — a primary target for automation.

Question 5

Which on-call handoff practice is most effective for continuity?

Accepted Answer

A structured handoff document covering open incidents, recent changes, and known risks

Answer

A structured handoff document ensures the incoming on-call engineer is aware of ongoing issues, recent changes, and system risks without having to rediscover them.

(SRE) Site Reliability Engineering Foundation Certification Practice Test

(SRE) Site Reliability Engineering Foundation Certification Practice Test

SRE On-Call Practices & Runbooks 4