- A
SLI is the contract with customers; SLO is the internal target; SLA is the measurement.
Why wrong: The definitions are scrambled. SLI = measurement (metric), SLO = internal target, SLA = customer contract.
- B
SLI is the measured metric; SLO is the internal target for that metric; SLA is the contractual customer commitment.
SLI measures performance (e.g., 99.95% availability). SLO sets the internal reliability goal (e.g., maintain 99.9%). SLA is the customer contract (e.g., credit if < 99.5%).
- C
SLI, SLO, and SLA are all the same thing — different names for uptime guarantees.
Why wrong: They are distinct concepts at different layers: measurement (SLI), internal goal (SLO), and customer contract (SLA). Conflating them leads to poor reliability engineering.
- D
SLA is measured in milliseconds; SLO is measured in percentage; SLI has no unit.
Why wrong: SLIs can have any unit appropriate to what's measured (percentage for availability, milliseconds for latency). The distinction is about their roles, not their units.
SLI vs SLO vs SLA
This GCDL practice question tests your understanding of scaling with google cloud operations. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
What is the difference between a Service Level Indicator (SLI), a Service Level Objective (SLO), and a Service Level Agreement (SLA)?
Quick Answer
The answer is that an SLI is the measured metric, an SLO is the internal target for that metric, and an SLA is the contractual customer commitment. This distinction is correct because it follows the core Site Reliability Engineering (SRE) framework: you first measure a specific metric like request latency at the 99th percentile (the SLI), then set an internal goal such as 99.9% of requests under 200ms (the SLO), and finally formalize a legal agreement with the customer, like 99.9% uptime with financial penalties (the SLA). On the Google Cloud Digital Leader exam, this question tests your understanding of how reliability is quantified and promised, often appearing in scenarios about monitoring and customer expectations. A common trap is confusing the SLO with the SLA, but remember that the SLO is your internal target, while the SLA is the binding contract you might miss. For a quick memory tip, think of the acronym “M-I-C”: Metric (SLI), Internal target (SLO), Contract (SLA).
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
SLI is the measured metric; SLO is the internal target for that metric; SLA is the contractual customer commitment.
Option B is correct because it accurately defines the relationship: an SLI is a specific metric (e.g., request latency at the 99th percentile), an SLO is the internal target for that metric (e.g., 99.9% of requests under 200ms), and an SLA is the contractual commitment to a customer (e.g., 99.9% uptime with financial penalties). This aligns with Google Cloud's Site Reliability Engineering (SRE) practices, where SLIs are measured, SLOs are internal goals, and SLAs are legal agreements.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
SLI is the contract with customers; SLO is the internal target; SLA is the measurement.
Why it's wrong here
The definitions are scrambled. SLI = measurement (metric), SLO = internal target, SLA = customer contract.
- ✓
SLI is the measured metric; SLO is the internal target for that metric; SLA is the contractual customer commitment.
Why this is correct
SLI measures performance (e.g., 99.95% availability). SLO sets the internal reliability goal (e.g., maintain 99.9%). SLA is the customer contract (e.g., credit if < 99.5%).
Related concept
Read the scenario before looking for a memorised answer.
- ✗
SLI, SLO, and SLA are all the same thing — different names for uptime guarantees.
Why it's wrong here
They are distinct concepts at different layers: measurement (SLI), internal goal (SLO), and customer contract (SLA). Conflating them leads to poor reliability engineering.
- ✗
SLA is measured in milliseconds; SLO is measured in percentage; SLI has no unit.
Why it's wrong here
SLIs can have any unit appropriate to what's measured (percentage for availability, milliseconds for latency). The distinction is about their roles, not their units.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The GCDL exam often tests the confusion between SLI, SLO, and SLA by swapping their definitions, so the trap here is assuming SLI is the contract or that all three terms are synonymous, when in reality they form a hierarchy of measurement, target, and agreement.
Detailed technical explanation
How to think about this question
In Google Cloud's SRE framework, SLIs are often derived from metrics like request latency, error rate, or throughput, collected via tools like Cloud Monitoring. SLOs are set based on business impact, and exceeding them triggers error budgets, which allow for controlled risk-taking. SLAs are legally binding and often include service credits if breached, as seen in Google Cloud's Compute Engine SLA (99.95% monthly uptime for single-instance VMs).
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Scaling with Google Cloud operations — study guide chapter
Learn the concepts, then practise the questions
- →
Scaling with Google Cloud operations practice questions
Targeted practice on this topic area only
- →
All GCDL questions
1,000 questions across all exam domains
- →
Google Cloud Digital Leader study guide
Full concept coverage aligned to exam objectives
- →
GCDL practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related GCDL practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Why Cloud Technology Can Transform Business practice questions
Practise GCDL questions linked to Why Cloud Technology Can Transform Business.
Fundamental Cloud Concepts practice questions
Practise GCDL questions linked to Fundamental Cloud Concepts.
Google Cloud Security practice questions
Practise GCDL questions linked to Google Cloud Security.
How Google Cloud Resources Are Managed practice questions
Practise GCDL questions linked to How Google Cloud Resources Are Managed.
Google Cloud Products and Services practice questions
Practise GCDL questions linked to Google Cloud Products and Services.
Why cloud technology is transforming business practice questions
Practise GCDL questions linked to Why cloud technology is transforming business.
Google Cloud products, services, and solutions practice questions
Practise GCDL questions linked to Google Cloud products, services, and solutions.
Scaling with Google Cloud operations practice questions
Practise GCDL questions linked to Scaling with Google Cloud operations.
Trust and security with Google Cloud practice questions
Practise GCDL questions linked to Trust and security with Google Cloud.
GCDL fundamentals practice questions
Practise GCDL questions linked to GCDL fundamentals.
GCDL scenario practice questions
Practise GCDL questions linked to GCDL scenario.
GCDL troubleshooting practice questions
Practise GCDL questions linked to GCDL troubleshooting.
Practice this exam
Start a free GCDL practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this GCDL question test?
Scaling with Google Cloud operations — This question tests Scaling with Google Cloud operations — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: SLI is the measured metric; SLO is the internal target for that metric; SLA is the contractual customer commitment. — Option B is correct because it accurately defines the relationship: an SLI is a specific metric (e.g., request latency at the 99th percentile), an SLO is the internal target for that metric (e.g., 99.9% of requests under 200ms), and an SLA is the contractual commitment to a customer (e.g., 99.9% uptime with financial penalties). This aligns with Google Cloud's Site Reliability Engineering (SRE) practices, where SLIs are measured, SLOs are internal goals, and SLAs are legal agreements.
What should I do if I get this GCDL question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Keep practising
More GCDL practice questions
- A DevOps team wants to adopt GitOps practices for managing their Google Cloud infrastructure. Which combination of tools…
- A startup is building an application that sends daily promotional push notifications to millions of mobile users on both…
- An organization's leadership wants to foster a 'fail fast' culture to accelerate innovation. A cloud environment directl…
- A company's on-premises applications occasionally need more compute capacity than their own infrastructure can provide (…
- A digital media company hosts video content globally. They want to reduce origin server load and deliver content faster…
- A security audit finds that a company's application service accounts have been granted broad IAM roles (e.g., Storage Ad…
Last reviewed: Jun 11, 2026
This GCDL practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the GCDL exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.