Exercise 2: Why No Separate Route 53/CloudFront-Style Layer Is Needed — Possible Solution
====================================================================

On AWS, an Application Load Balancer is inherently a regional
construct - it cannot by itself present one address that spans
multiple regions, which is exactly why the AWS Fundamentals capstone
needed a separate global-routing layer (Route 53 or CloudFront) on
top of any regional ALBs to get one global entry point.

GCP's own global external Application Load Balancer does not have
that same limitation. It already presents a single, real anycast IP
address as the frontend for backend instances across multiple regions
at once, with automatic cross-region failover built directly into
that same load balancer - this is the real, distinguishing
architecture Chapter 8 covers. Because that global behavior is already
native to the load balancer itself, there is no separate service
needed on top of it to get the same real capability AWS assembles
from two separate pieces.

ANSWER: This GCP build doesn't need a separate global-routing service
because GCP's own global load balancer is already a multi-region
service by default - one anycast IP natively fronts backends across
regions with built-in failover, unlike AWS's regional ALB, which needs
a separate layer such as Route 53 added on top to achieve the same
real capability.

WHY THIS WORKS AS AN ANSWER
------------------------------
This correctly reuses the chapter's own central real structural
finding - that GCP's load balancer is global by default - to explain
why the capstone's own architecture needed one fewer real service than
the equivalent AWS build.