Exercise 3: How an Action Group Could Have Changed the Outcome — Possible Solution
====================================================================

Azure's own real, documented language is explicit: crossing a budget
threshold sends a notification, but "resources aren't affected, and
your consumption isn't stopped." Without an Action Group attached,
the $10,000/month budget in this scenario can only ever notify
someone by email once the threshold is crossed -- it has no built-in
way to actually act on the unauthorized compute driving the charges.

In this scenario, a compromised credential is being used to launch
unauthorized compute. Even once the budget alert fires, the
unauthorized resources keep running and keep accumulating real
charges until a person sees the notification and manually intervenes
-- exactly the same real gap AWS Fundamentals Chapter 9 described for
AWS Budgets.

Attaching an Action Group to the budget would not change the core
lesson that the budget itself still only observes and notifies -- but
it would give the team a real, direct, built-in path to trigger an
actual automated response the moment the threshold is crossed:
calling a webhook, invoking an Azure Function, or triggering a Logic
App that could, for example, automatically disable the compromised
credential or shut down unrecognized resources, rather than waiting
for a person to read an email and react.

ANSWER: The Budget alone would not have prevented the charges because
it only notifies -- it never stops spending automatically, regardless
of whether an Action Group is attached. What an Action Group changes
is what happens NEXT: instead of relying entirely on a person noticing
an email, the team could configure the Action Group to trigger an
automated response (like an Azure Function that revokes the
compromised credential or halts the unauthorized resources)
immediately when the threshold is crossed, closing the real gap
between "we were notified" and "the problem is actually being
addressed" much faster than manual intervention alone would.

WHY THIS WORKS AS AN ANSWER
------------------------------
This correctly preserves the chapter's own core lesson (budgets
never stop spending by themselves) while explaining the GENUINE,
specific value Action Groups add on top of that -- a faster, more
automated response path -- rather than incorrectly implying the
Action Group itself makes the budget capable of directly halting
spending.