Practice common DevOps and SRE abbreviations: SLO, SLI, SLA, MTTR, MTTD, DORA, CI/CD, IaC, GitOps, FinOps, and incident management terms.
0 / 5 completed
1 / 5
What is the difference between an SLI, SLO, and SLA?
SLI is the actual measurement (e.g., 99.7% uptime this month). SLO is the internal target (e.g., 99.9% uptime). SLA is the contractual agreement with customers (e.g., 99.5% uptime or we pay credits). SLOs should be stricter than SLAs.
2 / 5
What does MTTR stand for and why is it important?
MTTR (Mean Time To Recovery) measures how quickly your team can restore service after a failure. It's one of the four DORA metrics. A low MTTR indicates mature incident response processes and good observability.
3 / 5
What does 'IaC' stand for and what problem does it solve?
IaC (Infrastructure as Code) means your servers, networks, and cloud resources are defined in code files (Terraform, Pulumi, CloudFormation). This enables version control, repeatability, and eliminates 'works on my cloud' problems.
4 / 5
What does 'GitOps' mean in a DevOps context?
GitOps means your Git repository is the source of truth. When you want to change infrastructure or deploy code, you commit to Git — automated systems (like Flux or ArgoCD) detect the change and reconcile the actual state to match.
5 / 5
In PagerDuty incident management, what do ACK, SNOOZE, and RESOLVE mean?
In PagerDuty: ACK (Acknowledge) means you're aware and working on it; SNOOZE temporarily silences alerts for a set period (useful during maintenance); RESOLVE closes the incident and stops all alerts. These are standard on-call response actions.