Exercise 2: Why a 30-Day Signed URL Request Cannot Succeed on GCP — Possible Solution
====================================================================

GCP's own real Signed URLs are capped at a platform-enforced maximum
expiration of 604,800 seconds - exactly 7 days. This isn't a
best-practice recommendation the developer can choose to ignore; it's
a real, hard limit GCP itself enforces at the platform level. A
request for a 30-day expiration exceeds that real maximum, so it
cannot be created at all, regardless of the developer's own intent to
avoid regenerating it repeatedly.

The real, structural protection this provides, compared to Azure's
own SAS token model, is significant: Azure Fundamentals Chapter 4's
own 2023 case study involved a SAS token that was effectively
permanent (valid until 2051) precisely because Azure's own platform
places no maximum expiration ceiling on SAS tokens at all - a
misconfiguration mistake was entirely possible there. On GCP, that
exact same category of mistake - creating a token that's accidentally
left valid for years or decades - is structurally impossible, because
the platform itself refuses to issue anything beyond 7 real days no
matter what a developer requests or misconfigures.

ANSWER: This specific request cannot succeed because GCP enforces a
real, hard 7-day maximum on Signed URL expiration at the platform
level, not merely as a guideline. This gives GCP a genuine structural
safety advantage over Azure's own SAS token model: the exact kind of
effectively-permanent, dangerously overscoped token that caused the
real 2023 Microsoft leak simply cannot be created on GCP, since the
platform itself refuses to allow an expiration beyond 7 days no matter
what is requested.

WHY THIS WORKS AS AN ANSWER
------------------------------
This correctly explains that the real protection here comes from
platform ENFORCEMENT, not developer discipline alone, and directly
connects the answer back to the specific, real, previously-covered
Azure case study this course's own sibling chapter documented,
showing the concrete real-world consequence this GCP limit prevents.