Exercise 2: A 20-Minute Event-Driven Function on 2nd Gen — Possible Solution
====================================================================

This is not possible as an event-driven function. The real 60-minute
maximum timeout on 2nd-generation Cloud Functions only applies to
HTTP-triggered functions. Event-driven functions - the kind triggered
by something other than a direct HTTP request, such as a Cloud
Storage or Pub/Sub event - are capped at a real maximum of 9 minutes,
even on 2nd gen, the same 9-minute ceiling 1st gen has always had for
every function type.

A 20-minute execution requirement genuinely exceeds that 9-minute
event-driven cap, regardless of generation. The real limit standing
in the way is specifically the event-driven timeout ceiling, not a
general 2nd-gen limitation - an HTTP-triggered 2nd-gen function could
run for up to 60 minutes, but this team's function is event-driven,
not HTTP-triggered.

ANSWER: No, this is not possible - even on 2nd generation, an
event-driven function (as opposed to an HTTP-triggered one) is capped
at a real maximum of 9 minutes, well short of the 20 minutes the team
needs. The 60-minute maximum only applies to HTTP-triggered functions.

WHY THIS WORKS AS AN ANSWER
------------------------------
This correctly distinguishes the chapter's own real, trigger-type-
specific timeout limits (60 min HTTP vs. 9 min event-driven) rather
than assuming 2nd gen uniformly grants the longer maximum to every
function regardless of trigger type.