KCNA ยท Cloud native principles and patterns
DevOps, SRE, platform engineering and SLI/SLO/SLA
Cloud native roles and practices, shared responsibility, internal developer platforms, SLI/SLO/SLA.
Key points
- DevOps is a culture and set of practices joining development and operations.
- SRE applies software engineering to reliability, using error budgets.
- Platform engineering builds an internal developer platform with self-service paved roads.
- An SLI is a measured indicator (e.g. success rate), an SLO is the internal target for it, and an SLA is the contractual promise to customers, often with penalties.
Practice questions
What is an SLO?
- A target for a service level indicator over a time window
- The raw measurement of latency
- A legal contract with refunds
- A deployment pipeline stage
Show answer
Answer: A. A target for a service level indicator over a time window
An SLO is a target value for an SLI over a period. The SLI is the measurement; the SLA is the customer contract.
Which are common DevOps practices?
- Continuous integration and delivery
- Infrastructure as code
- Throwing releases over the wall to ops
- Monitoring that feeds back into development
- Manual-only quarterly releases
Show answer
Answer: A. Continuous integration and delivery, B. Infrastructure as code, D. Monitoring that feeds back into development
CI/CD, infrastructure as code and monitoring feedback loops are core. Separate silos that hand work over a wall and manual-only releases contradict DevOps.
True or false: a 99.9% SLO means the service must have exactly zero downtime.
Show answer
Answer: False
False. 99.9% allows a small error budget of unavailability; chasing 100% is costly and blocks change.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
