Cloud Digital Leader Practice Question: A company's cloud spending suddenly spikes by…

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Requiring all cloud resource creation to go through a central IT approval process to prevent accidental VM creation

  Why it's wrong here

  A central IT approval process is a preventive governance control that could reduce accidental VM creation, but it does not provide any monitoring of actual spending patterns or trigger an alert when expenditure deviates from expected baselines. In practice, it becomes a manual bottleneck that slows development, is often bypassed via pre-approved projects or direct IAM permissions, and does not scale to dynamic environments where developers need agility. The core requirement is early detection of abnormal cost behavior, not preventing all resource creation, so budget alerts are the appropriate control because they are automated, real-time, and focused on spend thresholds.

• ✓

  Setting Cloud Billing budget alerts that notify stakeholders when spending approaches defined thresholds, enabling early detection and response to abnormal spending patterns

  Why this is correct

  Budget alerts are the direct preventive control. A budget alert at 150% of normal daily spending would have triggered early Saturday morning, prompting investigation. This gives the team time to act before a full weekend of over-spending accumulates. Budget alerts with escalating thresholds (50%, 80%, 100%, 150%) are a best practice.

• ✗

  Reviewing cloud bills at the end of each month to identify cost anomalies and address them retroactively

  Why it's wrong here

  A monthly bill review is a lagging indicator: Cloud Billing data is aggregated and exported only periodically, so by the time the bill is examined the abnormal spending has already fully accrued. Budget alerts, in contrast, evaluate spending continuously against thresholds and push notifications in near-real-time, allowing the team to investigate a Saturday-morning spike before a full weekend of overage builds up. Retroactive reconciliation can help optimize future spending, but it cannot prevent or limit the cost impact of an ongoing anomaly.

• ✗

  Using Reserved Instances for all VM workloads to reduce per-hour costs, making accidental long-running VMs less expensive

  Why it's wrong here

  Committing to reserved capacity for all VMs (including accidentally running ones) would reduce the per-hour rate but not prevent or detect the accidental over-spending. Budget alerts address detection; reserved pricing only addresses cost per unit.

Go deeper

Related to this question