01
Explain SLIs, SLOs, SLAs, error budgets and toil
Apply this point to a real GitHub Actions Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
GitHub Actions Academy · Enterprise Assessment Center
SRE and Observability Assessment
Assess SLIs, SLOs, error budgets, telemetry, alerting, incident response, capacity and reliability engineering.
Objective: Demonstrate quantitative reliability thinking and the ability to convert incidents into engineering improvements.
Practical guidance
Assessment scope and competencies
02
Describe metrics, logs, traces, alert quality and service ownership
Apply this point to a real GitHub Actions Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
03
Connect capacity, saturation, dependencies and graceful degradation
Apply this point to a real GitHub Actions Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
Practical guidance
Scenario and practical challenges
01
Design alerts for a latency-sensitive customer journey
Apply this point to a real GitHub Actions Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
02
Lead response to a cascading dependency failure
Apply this point to a real GitHub Actions Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
03
Choose between reliability work and feature delivery using evidence
Apply this point to a real GitHub Actions Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
Practical guidance
Scoring and evidence standards
01
Score signal quality, incident structure and remediation depth
Apply this point to a real GitHub Actions Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
02
Require timeline, contributing-factor and action evidence
Apply this point to a real GitHub Actions Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
03
Evaluate whether proposed controls reduce recurrence
Apply this point to a real GitHub Actions Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
Practical guidance
Improvement and readiness plan
01
Create one service-level objective
Apply this point to a real GitHub Actions Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
02
Build an incident-review template
Apply this point to a real GitHub Actions Academy design, delivery or operational scenario and record the evidence used to validate the outcome.
03
Repeat using a reliability game-day scenario
Apply this point to a real GitHub Actions Academy design, delivery or operational scenario and record the evidence used to validate the outcome.