Question 475 of 507
Scaling with Google Cloud operationsmediumMultiple ChoiceObjective-mapped

Cloud Digital Leader Scaling with Google Cloud operations Practice Question

This GCDL practice question tests your understanding of scaling with google cloud operations. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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.

Exhibit

{
  "metric": {
    "type": "custom.googleapis.com/inventory/items_sold",
    "labels": {}
  },
  "resource": {
    "type": "global",
    "labels": {
      "project_id": "my-project"
    }
  },
  "points": [
    {
      "interval": {
        "endTime": "2023-01-01T12:00:00Z"
      },
      "value": {
        "int64Value": "100"
      }
    }
  ],
  "metricKind": "GAUGE",
  "valueType": "INT64"
}

Refer to the exhibit. A DevOps engineer wants to create a chart showing the rate of items sold per second over time. What is a limitation of this metric for that purpose?

Question 1mediummultiple choice
Full question →

Exhibit

{
  "metric": {
    "type": "custom.googleapis.com/inventory/items_sold",
    "labels": {}
  },
  "resource": {
    "type": "global",
    "labels": {
      "project_id": "my-project"
    }
  },
  "points": [
    {
      "interval": {
        "endTime": "2023-01-01T12:00:00Z"
      },
      "value": {
        "int64Value": "100"
      }
    }
  ],
  "metricKind": "GAUGE",
  "valueType": "INT64"
}

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

The metric kind is GAUGE, so it cannot be used to calculate rate

Option A is correct because a GAUGE metric type represents a point-in-time value (e.g., current number of items), not a cumulative counter. To calculate a rate (items per second), you need a CUMULATIVE counter metric that monotonically increases, allowing Cloud Monitoring to compute the derivative over time. GAUGE metrics lack the necessary monotonicity and cumulative semantics, so they cannot be used to derive a meaningful rate of change.

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.

  • The metric kind is GAUGE, so it cannot be used to calculate rate

    Why this is correct

    GAUGE metrics are snapshots; rate requires DELTA or CUMULATIVE.

    Related concept

    Read the scenario before looking for a memorised answer.

  • The interval should include a startTime

    Why it's wrong here

    For GAUGE, only endTime is required.

  • The metric has no labels to filter

    Why it's wrong here

    Labels affect filtering but not rate computation.

  • The value should be DOUBLE instead of INT64

    Why it's wrong here

    INT64 is fine for counts.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Google Cloud often tests the misconception that any numeric metric can be used to compute a rate, when in fact only CUMULATIVE counters support rate-of-change calculations in Cloud Monitoring.

Detailed technical explanation

How to think about this question

Under the hood, Cloud Monitoring's rate calculation relies on the metric's kind and type. For a CUMULATIVE counter, the service samples the counter at two points and divides the difference by the time interval (Δvalue/Δt). A GAUGE metric, however, only reports an instantaneous snapshot; any attempt to compute a rate from two GAUGE samples would yield the average value over the interval, not a true rate of change. In real-world scenarios, this distinction is critical when monitoring request rates or throughput, where using a GAUGE (e.g., current connections) instead of a CUMULATIVE counter (e.g., total requests) leads to misleading dashboards.

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

An e-commerce site experiences heavy traffic on Black Friday and near-zero traffic during off-peak weeks. Rather than provisioning permanent large VMs, the team uses auto-scaling groups that add capacity automatically under load and reduce it overnight. Questions like this test whether you understand elasticity, availability zones, and cloud compute scaling patterns.

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 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.

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: The metric kind is GAUGE, so it cannot be used to calculate rate — Option A is correct because a GAUGE metric type represents a point-in-time value (e.g., current number of items), not a cumulative counter. To calculate a rate (items per second), you need a CUMULATIVE counter metric that monotonically increases, allowing Cloud Monitoring to compute the derivative over time. GAUGE metrics lack the necessary monotonicity and cumulative semantics, so they cannot be used to derive a meaningful rate of change.

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

More GCDL practice questions

Last reviewed: Jun 30, 2026

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…

Sign in to join the discussion.

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.