← GCDL·Google Cloud

Question 494 of 507

Scaling with Google Cloud operations →hardMultiple ChoiceObjective-mapped

Quick Answer

The correct answer is Service Level Indicators (SLIs), which are the metrics that collectively define how reliability is quantified from the user’s perspective. In Site Reliability Engineering, SLIs like p99 latency, error rate, and requests per second are carefully chosen quantitative measures of specific service behaviors—such as availability, responsiveness, and throughput—that directly reflect the end-user experience. On the Google Cloud Digital Leader exam, this concept tests your understanding of the foundational SRE triad: SLIs, SLOs, and SLIs metrics definition, often appearing in scenario-based questions where you must distinguish SLIs (the raw measurements) from SLOs (the target thresholds). A common trap is confusing SLIs with SLOs; remember that SLIs are the “what you measure,” while SLOs are the “what you aim for.” A helpful memory tip: SLI stands for “Service Level Indicator”—think of it as the indicator light on your dashboard showing actual performance, not the goal you set.

Cloud Digital Leader Scaling with Google Cloud operations Practice Question

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.

An operations team tracks the following metrics for their customer portal: request latency p99, error rate, and requests per second. In Site Reliability Engineering terminology, what are these metrics called, and what do they collectively define?

Question 1hardmultiple choice

Full question →

A
Key Performance Indicators (KPIs) that define the overall health of the business
Why wrong: KPIs is a general business term. In SRE, these specific technical metrics measuring service health from the user's perspective are specifically called Service Level Indicators — a more precise term with defined meaning in the SRE framework.
B
Service Level Agreements (SLAs), defining the contractual commitments made to customers
Why wrong: SLAs are contracts with customers that define consequences when service falls below standards. The metrics themselves — latency p99, error rate, throughput — are SLIs, not SLAs. SLAs reference SLIs but are a distinct concept.
C
Service Level Indicators (SLIs), which measure specific dimensions of service behavior from the user's perspective and collectively define how reliability is quantified
SLIs are the specific measurable quantities that capture how users experience the service. Latency (is it fast enough?), error rate (is it working?), and throughput (is it keeping up?) are the canonical SLI types. Together they provide a quantitative picture of reliability that can be used to set SLO targets.
D
Operational metrics that are only relevant to the infrastructure team and not to business stakeholders
Why wrong: SLIs and the SLOs derived from them are directly relevant to business stakeholders — they quantify the reliability of customer experience. Error rate and latency directly affect customer satisfaction and revenue.

Full breakdown with real-world context →

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

✓

Service Level Indicators (SLIs), which measure specific dimensions of service behavior from the user's perspective and collectively define how reliability is quantified

In Site Reliability Engineering (SRE), the metrics p99 latency, error rate, and requests per second are classified as Service Level Indicators (SLIs). SLIs are carefully chosen quantitative measures of specific aspects of the service's behavior, such as availability, latency, or throughput, as experienced by the end user. Collectively, these SLIs define how reliability is quantified and are used to set and monitor Service Level Objectives (SLOs).

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.

✗
Key Performance Indicators (KPIs) that define the overall health of the business
Why it's wrong here
KPIs is a general business term. In SRE, these specific technical metrics measuring service health from the user's perspective are specifically called Service Level Indicators — a more precise term with defined meaning in the SRE framework.
✗
Service Level Agreements (SLAs), defining the contractual commitments made to customers
Why it's wrong here
SLAs are contracts with customers that define consequences when service falls below standards. The metrics themselves — latency p99, error rate, throughput — are SLIs, not SLAs. SLAs reference SLIs but are a distinct concept.
✓
Service Level Indicators (SLIs), which measure specific dimensions of service behavior from the user's perspective and collectively define how reliability is quantified
Why this is correct
SLIs are the specific measurable quantities that capture how users experience the service. Latency (is it fast enough?), error rate (is it working?), and throughput (is it keeping up?) are the canonical SLI types. Together they provide a quantitative picture of reliability that can be used to set SLO targets.
Related concept
Read the scenario before looking for a memorised answer.
✗
Operational metrics that are only relevant to the infrastructure team and not to business stakeholders
Why it's wrong here
SLIs and the SLOs derived from them are directly relevant to business stakeholders — they quantify the reliability of customer experience. Error rate and latency directly affect customer satisfaction and revenue.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates confuse SLIs with SLAs or KPIs, not realizing that SLIs are the raw measurements that feed into SLOs, which then underpin SLAs, and that they are specifically defined from the user's perspective to quantify reliability.

Detailed technical explanation

How to think about this question

Under the hood, a p99 latency SLI means that 99% of requests must complete within a certain threshold, and this is typically measured using histogram buckets in monitoring systems like Prometheus or Google Cloud Monitoring. The error rate SLI is often calculated as the ratio of HTTP 5xx responses to total requests, and requests per second (RPS) measures throughput. A real-world scenario: if the p99 latency spikes above the SLO threshold, automated alerting triggers a rollback or scaling action before users are broadly impacted, demonstrating how SLIs directly drive operational decisions.

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.

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 is transforming business practice questions

Practise GCDL questions linked to Why cloud technology is transforming business.

Fundamental cloud concepts practice questions

Practise GCDL questions linked to Fundamental cloud concepts.

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.

10 questions 20 questions 30 questions 50 questions Timed 30

GCDL practice-test guide →Study guide →Browse all practice tests

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: Service Level Indicators (SLIs), which measure specific dimensions of service behavior from the user's perspective and collectively define how reliability is quantified — In Site Reliability Engineering (SRE), the metrics p99 latency, error rate, and requests per second are classified as Service Level Indicators (SLIs). SLIs are carefully chosen quantitative measures of specific aspects of the service's behavior, such as availability, latency, or throughput, as experienced by the end user. Collectively, these SLIs define how reliability is quantified and are used to set and monitor Service Level Objectives (SLOs).

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 →

How Courseiva writes practice questions · Editorial policy

Keep practising

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.

Loading comments…

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.