Question 444 of 1,000
Scaling with Google Cloud operationshardMultiple ChoiceObjective-mapped

Why Idle Cloud SQL Instances Cause Cost Waste and How to Prevent It

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.

A company's cloud cost has grown significantly. A FinOps analysis reveals the largest waste category is idle Cloud SQL instances — 12 database instances that were provisioned for projects that have since ended, but were never deleted. What process failure most directly caused this waste?

Clue words in this question

Noticing these words before you look at the options changes how you read each choice.

  • Clue: "never"

    Why it matters: Absolute qualifier. True only if the statement has zero exceptions — be cautious of options that seem obvious but break down in edge cases.

Quick Answer

The absence of a resource decommissioning process is the correct choice because idle Cloud SQL instances are the direct result of failing to formally retire cloud resources when projects end. In Google Cloud, Cloud SQL instances do not auto-delete; they persist and continue accruing compute and storage costs until explicitly removed, which is why a decommissioning workflow is essential to prevent cost waste. On the Google Cloud Digital Leader exam, this scenario tests your understanding of FinOps lifecycle management, often appearing as a trap where candidates blame provisioning errors rather than the missing teardown step. A common memory tip is to think of it as "no project end date equals no instance delete date" — if there is no formal step to identify and delete associated resources, idle infrastructure will persist indefinitely. Remember the mnemonic "D for Decommission" to link the root cause directly to the absence of a deletion process.

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 absence of a resource decommissioning process: when projects end, there is no formal step to identify and delete associated cloud resources, allowing idle infrastructure to persist and accrue costs indefinitely

Option B is correct because the root cause is the lack of a formal resource decommissioning process. When projects end, there is no automated or manual step to identify and delete associated Cloud SQL instances, so idle databases continue to incur costs. In Google Cloud, Cloud SQL instances do not auto-delete; they persist until explicitly removed, making a decommissioning workflow essential to prevent waste.

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 company should have used a cheaper database service instead of Cloud SQL

    Why it's wrong here

    Service choice doesn't address the root cause — idle instances of any database service would produce waste. The problem is that instances weren't deleted when no longer needed.

  • The absence of a resource decommissioning process: when projects end, there is no formal step to identify and delete associated cloud resources, allowing idle infrastructure to persist and accrue costs indefinitely

    Why this is correct

    This is the root cause. FinOps best practice requires a defined lifecycle process: when a project is closed or a service is decommissioned, associated cloud resources are explicitly identified and deleted. Without this step, idle resources accumulate. The fix is process: add resource cleanup to the project closure checklist and automate detection of idle resources.

    Clue confirmation

    The clue word "never" in the question point toward this answer.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Cloud SQL pricing is too high compared to on-premises databases, making any unused capacity expensive

    Why it's wrong here

    Pricing is not the root cause. Even at discounted prices, idle resources that serve no purpose are waste. The fix is process, not pricing negotiation.

  • The database administrators forgot to enable automatic deletion for idle Cloud SQL instances

    Why it's wrong here

    Cloud SQL doesn't have an automatic deletion feature for idle instances. The process fix is human: include resource deletion in project closure procedures, supported by automated idle resource detection tools.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The GCDL exam often tests the concept that cloud resources are not automatically cleaned up when projects end, and candidates mistakenly think technical features like auto-deletion or cheaper services are the solution, rather than recognizing the need for a process-driven decommissioning workflow.

Detailed technical explanation

How to think about this question

Under the hood, Cloud SQL instances are billed per hour based on machine type, storage, and network egress, with no built-in idle detection or auto-shutdown. In a real-world scenario, a company might use Cloud Asset Inventory or Unused IP Address alerts to identify orphaned resources, but without a decommissioning policy, even a single forgotten instance can run for months, costing thousands of dollars. Google Cloud's Recommender can flag idle instances, but it requires proactive setup and action to delete them.

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 startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.

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 absence of a resource decommissioning process: when projects end, there is no formal step to identify and delete associated cloud resources, allowing idle infrastructure to persist and accrue costs indefinitely — Option B is correct because the root cause is the lack of a formal resource decommissioning process. When projects end, there is no automated or manual step to identify and delete associated Cloud SQL instances, so idle databases continue to incur costs. In Google Cloud, Cloud SQL instances do not auto-delete; they persist until explicitly removed, making a decommissioning workflow essential to prevent waste.

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.

Are there clue words in this question I should notice?

Yes — watch for: "never". Absolute qualifier. True only if the statement has zero exceptions — be cautious of options that seem obvious but break down in edge cases.

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