Exercise 3: Does a Standard Budget Automatically Stop the Application's Services? — Possible Solution
====================================================================

The stakeholder's assumption is not correct. The Cloud Billing budget
configured in Step 9 is a standard, alerts-only budget - by real,
explicit design, it "doesn't automatically cap" usage or spending.
Its only real effect is sending notifications at the configured
50/90/100% thresholds; it has no ability on its own to pause, stop, or
otherwise interrupt any of the application's own running services,
regardless of how far spend exceeds the budgeted amount.

To make the stakeholder's assumption actually true, the team would
need to use GCP's separate spend cap budget type instead (currently in
preview, and only available for supported services) - that is the real
feature genuinely capable of pausing a service once its threshold is
reached, rather than only sending a notification. A standard budget
and a spend cap budget are two different real features with two
different real behaviors, and only one of them enforces a limit.

ANSWER: No, this assumption is not correct - the standard budget
configured here only sends alerts and cannot stop any service on its
own. To actually achieve automatic stopping, the team would need to
use GCP's separate spend cap budget feature instead, which is
genuinely capable of pausing a supported service once its threshold is
reached.

WHY THIS WORKS AS AN ANSWER
------------------------------
This correctly distinguishes the standard alerts-only budget actually
used in the capstone from the separate spend cap feature that would be
needed to satisfy the stakeholder's assumption, reusing Chapter 9's
own central finding.