Exercise 1: Why a Regional MIG, Not a Zonal One — Possible Solution
====================================================================

A zonal Managed Instance Group places every one of its instances in a
single real zone. If that one zone experiences an outage, every web
tier instance in the group goes down at the same time - autoscaling
and autohealing both operate within that same zone, so there is
nothing left for either feature to fall back on. The application
would become fully unavailable for the duration of that zone's own
outage, even though the group was "healthy" and correctly configured
in every other respect.

A regional Managed Instance Group avoids this by automatically
spreading instances across multiple zones within the region. If one
zone fails, the instances running in the other zones keep serving
traffic, giving the application genuine protection against a single
zone's own failure - the same real gap Azure Fundamentals Chapter 8
already flagged for a Virtual Machine Scale Set left in its own
default, non-multi-zone configuration.

ANSWER: A zonal MIG alone leaves the application fully exposed to a
single zone's own failure, since every instance would live in that one
zone with nothing to fall back on. A regional MIG addresses this by
spreading instances across multiple zones, so the application keeps
running even if one zone goes down.

WHY THIS WORKS AS AN ANSWER
------------------------------
This correctly identifies the real zone-level risk a zonal MIG leaves
unaddressed and explains how the regional MIG choice made in the
capstone directly closes that gap, reusing Chapter 8's own central
finding.