Lesson proof
Concept, demo, checklist, lab, and assignment evidence.
SRE / OpenTelemetry / Cloud Operations / Site Reliability and Observability Engineer
Site Reliability and Observability Engineer
Build reliability engineering skill with SLIs, SLOs, error budgets, OpenTelemetry, logs, metrics, traces, alerting, incident command, postmortems, capacity planning, chaos testing, and toil reduction.
SRE readinessObservability evidenceIncident response discipline
Start domain mock testPlatform-wide module outputs
Every module now feeds portfolio proof and CV readiness.
Portfolio pack
Requirement, artifact, validation, risk note, and interview story.
CV signal
Role-specific skill statement linked to a score or artifact.
Review queue
Submitted evidence can support dashboard, readiness, and career exports.
Open materials
SRE foundations SLIs SLOs and error budgetsLesson + portfolio pack + CV evidenceOpenTelemetry instrumentation and tracingLesson + portfolio pack + CV evidenceMetrics logs traces and eventsLesson + portfolio pack + CV evidencePrometheus Grafana and dashboard designLesson + portfolio pack + CV evidenceAlerting on-call and escalation policyLesson + portfolio pack + CV evidenceIncident command communication and timelineLesson + portfolio pack + CV evidencePostmortems learning reviews and corrective actionsLesson + portfolio pack + CV evidenceCapacity planning load testing and performance budgetsLesson + portfolio pack + CV evidenceChaos testing resilience and failure injectionLesson + portfolio pack + CV evidenceRunbook automation and toil reductionLesson + portfolio pack + CV evidenceReliability scorecards and executive reportingLesson + portfolio pack + CV evidenceSRE observability capstoneLesson + portfolio pack + CV evidence
Certification objective coverage
Every provider-aligned module is connected to a lesson, labs, mock questions, and implementation proof.
This is the track-level audit view for blueprint alignment. Exact exam wording should still be checked against the current official provider guide before public exam-code claims are made.
site-reliability-observability-engineer.sre-foundations-slis-slos-and-error-budgets.01 / 8% weight
Apply SRE foundations SLIs SLOs and error budgets decisions to Site Reliability and Observability Engineer scenarios
Implementation proof
- Define SRE foundations SLIs SLOs and error budgets in plain language and explain the provider service family it belongs to.
- Show how SRE foundations SLIs SLOs and error budgets is implemented through a guided configuration, simulator, command, diagram, notebook, or case study.
- Capture evidence with screenshots, command output, logs, metrics, topology state, policy review, query result, or troubleshooting notes.
- Connect the evidence to a portfolio pack, CV-ready skill statement, and mock-test weak-domain recovery action.
Evidence requirements
- Correct scenario decision in mock exam
- Written explanation of the key requirement or constraint
- Hands-on lab evidence or troubleshooting proof
- Portfolio pack with requirement, artifact, validation, risk note, and interview story
- CV-ready skill statement linked to a score, artifact, or project result
site-reliability-observability-engineer.opentelemetry-instrumentation-and-tracing.02 / 8% weight
Apply OpenTelemetry instrumentation and tracing decisions to Site Reliability and Observability Engineer scenarios
Implementation proof
- Define OpenTelemetry instrumentation and tracing in plain language and explain the provider service family it belongs to.
- Show how OpenTelemetry instrumentation and tracing is implemented through a guided configuration, simulator, command, diagram, notebook, or case study.
- Capture evidence with screenshots, command output, logs, metrics, topology state, policy review, query result, or troubleshooting notes.
- Connect the evidence to a portfolio pack, CV-ready skill statement, and mock-test weak-domain recovery action.
Evidence requirements
- Correct scenario decision in mock exam
- Written explanation of the key requirement or constraint
- Hands-on lab evidence or troubleshooting proof
- Portfolio pack with requirement, artifact, validation, risk note, and interview story
- CV-ready skill statement linked to a score, artifact, or project result
site-reliability-observability-engineer.metrics-logs-traces-and-events.03 / 8% weight
Apply Metrics logs traces and events decisions to Site Reliability and Observability Engineer scenarios
Implementation proof
- Define Metrics logs traces and events in plain language and explain the provider service family it belongs to.
- Show how Metrics logs traces and events is implemented through a guided configuration, simulator, command, diagram, notebook, or case study.
- Capture evidence with screenshots, command output, logs, metrics, topology state, policy review, query result, or troubleshooting notes.
- Connect the evidence to a portfolio pack, CV-ready skill statement, and mock-test weak-domain recovery action.
Evidence requirements
- Correct scenario decision in mock exam
- Written explanation of the key requirement or constraint
- Hands-on lab evidence or troubleshooting proof
- Portfolio pack with requirement, artifact, validation, risk note, and interview story
- CV-ready skill statement linked to a score, artifact, or project result
site-reliability-observability-engineer.prometheus-grafana-and-dashboard-design.04 / 8% weight
Apply Prometheus Grafana and dashboard design decisions to Site Reliability and Observability Engineer scenarios
Implementation proof
- Define Prometheus Grafana and dashboard design in plain language and explain the provider service family it belongs to.
- Show how Prometheus Grafana and dashboard design is implemented through a guided configuration, simulator, command, diagram, notebook, or case study.
- Capture evidence with screenshots, command output, logs, metrics, topology state, policy review, query result, or troubleshooting notes.
- Connect the evidence to a portfolio pack, CV-ready skill statement, and mock-test weak-domain recovery action.
Evidence requirements
- Correct scenario decision in mock exam
- Written explanation of the key requirement or constraint
- Hands-on lab evidence or troubleshooting proof
- Portfolio pack with requirement, artifact, validation, risk note, and interview story
- CV-ready skill statement linked to a score, artifact, or project result
site-reliability-observability-engineer.alerting-on-call-and-escalation-policy.05 / 8% weight
Apply Alerting on-call and escalation policy decisions to Site Reliability and Observability Engineer scenarios
Implementation proof
- Define Alerting on-call and escalation policy in plain language and explain the provider service family it belongs to.
- Show how Alerting on-call and escalation policy is implemented through a guided configuration, simulator, command, diagram, notebook, or case study.
- Capture evidence with screenshots, command output, logs, metrics, topology state, policy review, query result, or troubleshooting notes.
- Connect the evidence to a portfolio pack, CV-ready skill statement, and mock-test weak-domain recovery action.
Evidence requirements
- Correct scenario decision in mock exam
- Written explanation of the key requirement or constraint
- Hands-on lab evidence or troubleshooting proof
- Portfolio pack with requirement, artifact, validation, risk note, and interview story
- CV-ready skill statement linked to a score, artifact, or project result
site-reliability-observability-engineer.incident-command-communication-and-timeline.06 / 8% weight
Apply Incident command communication and timeline decisions to Site Reliability and Observability Engineer scenarios
Implementation proof
- Define Incident command communication and timeline in plain language and explain the provider service family it belongs to.
- Show how Incident command communication and timeline is implemented through a guided configuration, simulator, command, diagram, notebook, or case study.
- Capture evidence with screenshots, command output, logs, metrics, topology state, policy review, query result, or troubleshooting notes.
- Connect the evidence to a portfolio pack, CV-ready skill statement, and mock-test weak-domain recovery action.
Evidence requirements
- Correct scenario decision in mock exam
- Written explanation of the key requirement or constraint
- Hands-on lab evidence or troubleshooting proof
- Portfolio pack with requirement, artifact, validation, risk note, and interview story
- CV-ready skill statement linked to a score, artifact, or project result
site-reliability-observability-engineer.postmortems-learning-reviews-and-corrective-actions.07 / 8% weight
Apply Postmortems learning reviews and corrective actions decisions to Site Reliability and Observability Engineer scenarios
Implementation proof
- Define Postmortems learning reviews and corrective actions in plain language and explain the provider service family it belongs to.
- Show how Postmortems learning reviews and corrective actions is implemented through a guided configuration, simulator, command, diagram, notebook, or case study.
- Capture evidence with screenshots, command output, logs, metrics, topology state, policy review, query result, or troubleshooting notes.
- Connect the evidence to a portfolio pack, CV-ready skill statement, and mock-test weak-domain recovery action.
Evidence requirements
- Correct scenario decision in mock exam
- Written explanation of the key requirement or constraint
- Hands-on lab evidence or troubleshooting proof
- Portfolio pack with requirement, artifact, validation, risk note, and interview story
- CV-ready skill statement linked to a score, artifact, or project result
site-reliability-observability-engineer.capacity-planning-load-testing-and-performance-budgets.08 / 8% weight
Apply Capacity planning load testing and performance budgets decisions to Site Reliability and Observability Engineer scenarios
Implementation proof
- Define Capacity planning load testing and performance budgets in plain language and explain the provider service family it belongs to.
- Show how Capacity planning load testing and performance budgets is implemented through a guided configuration, simulator, command, diagram, notebook, or case study.
- Capture evidence with screenshots, command output, logs, metrics, topology state, policy review, query result, or troubleshooting notes.
- Connect the evidence to a portfolio pack, CV-ready skill statement, and mock-test weak-domain recovery action.
Evidence requirements
- Correct scenario decision in mock exam
- Written explanation of the key requirement or constraint
- Hands-on lab evidence or troubleshooting proof
- Portfolio pack with requirement, artifact, validation, risk note, and interview story
- CV-ready skill statement linked to a score, artifact, or project result
site-reliability-observability-engineer.chaos-testing-resilience-and-failure-injection.09 / 8% weight
Apply Chaos testing resilience and failure injection decisions to Site Reliability and Observability Engineer scenarios
Implementation proof
- Define Chaos testing resilience and failure injection in plain language and explain the provider service family it belongs to.
- Show how Chaos testing resilience and failure injection is implemented through a guided configuration, simulator, command, diagram, notebook, or case study.
- Capture evidence with screenshots, command output, logs, metrics, topology state, policy review, query result, or troubleshooting notes.
- Connect the evidence to a portfolio pack, CV-ready skill statement, and mock-test weak-domain recovery action.
Evidence requirements
- Correct scenario decision in mock exam
- Written explanation of the key requirement or constraint
- Hands-on lab evidence or troubleshooting proof
- Portfolio pack with requirement, artifact, validation, risk note, and interview story
- CV-ready skill statement linked to a score, artifact, or project result
site-reliability-observability-engineer.runbook-automation-and-toil-reduction.10 / 8% weight
Apply Runbook automation and toil reduction decisions to Site Reliability and Observability Engineer scenarios
Implementation proof
- Define Runbook automation and toil reduction in plain language and explain the provider service family it belongs to.
- Show how Runbook automation and toil reduction is implemented through a guided configuration, simulator, command, diagram, notebook, or case study.
- Capture evidence with screenshots, command output, logs, metrics, topology state, policy review, query result, or troubleshooting notes.
- Connect the evidence to a portfolio pack, CV-ready skill statement, and mock-test weak-domain recovery action.
Evidence requirements
- Correct scenario decision in mock exam
- Written explanation of the key requirement or constraint
- Hands-on lab evidence or troubleshooting proof
- Portfolio pack with requirement, artifact, validation, risk note, and interview story
- CV-ready skill statement linked to a score, artifact, or project result
site-reliability-observability-engineer.reliability-scorecards-and-executive-reporting.11 / 8% weight
Apply Reliability scorecards and executive reporting decisions to Site Reliability and Observability Engineer scenarios
Implementation proof
- Define Reliability scorecards and executive reporting in plain language and explain the provider service family it belongs to.
- Show how Reliability scorecards and executive reporting is implemented through a guided configuration, simulator, command, diagram, notebook, or case study.
- Capture evidence with screenshots, command output, logs, metrics, topology state, policy review, query result, or troubleshooting notes.
- Connect the evidence to a portfolio pack, CV-ready skill statement, and mock-test weak-domain recovery action.
Evidence requirements
- Correct scenario decision in mock exam
- Written explanation of the key requirement or constraint
- Hands-on lab evidence or troubleshooting proof
- Portfolio pack with requirement, artifact, validation, risk note, and interview story
- CV-ready skill statement linked to a score, artifact, or project result
site-reliability-observability-engineer.sre-observability-capstone.12 / 12% weight
Apply SRE observability capstone decisions to Site Reliability and Observability Engineer scenarios
Implementation proof
- Define SRE observability capstone in plain language and explain the provider service family it belongs to.
- Show how SRE observability capstone is implemented through a guided configuration, simulator, command, diagram, notebook, or case study.
- Capture evidence with screenshots, command output, logs, metrics, topology state, policy review, query result, or troubleshooting notes.
- Connect the evidence to a portfolio pack, CV-ready skill statement, and mock-test weak-domain recovery action.
Evidence requirements
- Correct scenario decision in mock exam
- Written explanation of the key requirement or constraint
- Hands-on lab evidence or troubleshooting proof
- Portfolio pack with requirement, artifact, validation, risk note, and interview story
- CV-ready skill statement linked to a score, artifact, or project result
Test readiness
Mock test by domain
Practice every domain in this track with exam-style questions, answer keys, and explanations.
Open mock testMost in-demand certification materials
High-value certificates connected to this track.
SRE / OpenTelemetry / Cloud Operations
SRE and observability readiness
Needs reviewLast verified: Not verifiedNext review: Provider source review required
Cloud, DevOps, platform, and operations engineers responsible for reliability, incident response, observability, and production health.
SRE and observability readiness is mapped to platform lessons and labs, but still needs a dated official-source review.
- SLO, SLI, error-budget, and burn-rate workbook
- Observability dashboard checklist for metrics, logs, traces, events, dependencies, and golden signals
- Incident command, postmortem, capacity, chaos, and reliability reporting evidence pack
SRE / Incident Management
Production reliability portfolio
Needs reviewLast verified: Not verifiedNext review: Provider source review required
Learners who need to prove production ownership through incident, capacity, resilience, and executive reporting evidence.
Production reliability portfolio is mapped to platform lessons and labs, but still needs a dated official-source review.
- Postmortem and corrective-action template
- Load testing and performance budget worksheet
- Reliability executive summary and service review rubric
Certification provider connections
Connect this learning path to the official exam provider.
Certification provider
SRE and observability readiness
Confirm the official provider, exam code, delivery rules, ID policy, and reschedule window before booking.
Booking partner: Provider exam partner
- Create or confirm the Provider learner account.
- Review the official exam guide, ID policy, delivery options, and reschedule rules.
- Add target exam date, booking status, renewal date, and certificate proof to the learner record.
Certification provider
Production reliability portfolio
Confirm the official provider, exam code, delivery rules, ID policy, and reschedule window before booking.
Booking partner: Provider exam partner
- Create or confirm the Provider learner account.
- Review the official exam guide, ID policy, delivery options, and reschedule rules.
- Add target exam date, booking status, renewal date, and certificate proof to the learner record.
01 Match
Map each Daskerel track to the official provider, exam code, registration page, and verification route.
02 Prepare
Use provider objectives with Daskerel lessons, mock exams, labs, and evidence packs before booking.
03 Book
Send learners to the official scheduling partner while keeping target dates and next actions in the dashboard.
04 Verify
Capture certificate URL, badge, expiry, renewal plan, and portfolio proof after the learner passes.
Study plan
Start by defining what reliability means for a service: user journey, SLI, SLO, error budget, and business impact.
Instrument before alerting: collect metrics, logs, traces, and events that explain symptoms, causes, and recovery signals.
Practise incidents end to end: detection, triage, command, communication, mitigation, postmortem, corrective action, and reliability report.
Hands-on labs
Create an SLO worksheet for a web service with availability, latency, error rate, user journey, error budget, and burn-rate alert.
Design an observability dashboard with metrics, logs, traces, service dependencies, saturation, and golden signals.
Write an incident command timeline with detection, severity, roles, mitigation, customer update, rollback decision, and recovery validation.
Run a capacity planning exercise with traffic assumptions, bottlenecks, scaling thresholds, cost impact, and performance budget.
Create a postmortem with root cause, contributing factors, user impact, corrective actions, owners, due dates, and prevention evidence.
Track learning assets
Templates and revision tools for this path.
Exam blueprint checklistSite Reliability and Observability Engineer
Weekly study plannerSite Reliability and Observability Engineer
Command and service cheat sheetSite Reliability and Observability Engineer
Architecture pattern cardsSite Reliability and Observability Engineer
Flashcard revision setSite Reliability and Observability Engineer
Mock exam review sheetSite Reliability and Observability Engineer
Lab evidence templateSite Reliability and Observability Engineer
Interview story builderSite Reliability and Observability Engineer
Portfolio project rubricSite Reliability and Observability Engineer
Final readiness checklistSite Reliability and Observability Engineer
Practice questions
Why are SLOs better than vague uptime goals?
SLOs define a measurable reliability target tied to user experience, which supports alerting, error budgets, prioritization, and business communication.
What should an incident report include?
It should include timeline, impact, detection source, root cause, mitigation, recovery validation, communication, contributing factors, corrective actions, owners, and follow-up evidence.