Exercise 1: A 25-Minute Job on Lambda vs. Azure Functions — Possible Solution
====================================================================

AWS Lambda enforces a real, fixed maximum execution time of 15
minutes, with no exceptions -- this is a hard architectural ceiling,
not a configurable setting that can be raised for a specific
workload. A job that reliably needs 25 minutes to complete genuinely
CANNOT run to completion in a single Lambda invocation, no matter how
the function is configured; it would be forcibly terminated partway
through every single time.

Azure Functions on the Flex Consumption plan works differently: its
own real default timeout is 30 minutes, and there's no enforced
maximum execution timeout duration at all (with only a 60-minute
grace period during scale-in events, and 10 minutes during platform
updates -- neither of which is a hard ceiling on normal execution). A
25-minute job fits comfortably within Flex Consumption's own real
30-minute default, let alone its effectively unbounded real maximum.

ANSWER: This job cannot run unmodified on Lambda because 25 minutes
exceeds Lambda's own real, fixed 15-minute ceiling -- the function
would need to be redesigned (e.g. split into multiple shorter
invocations, or moved to a different compute service entirely) to run
there. On Azure Functions' Flex Consumption plan, the same 25-minute
job fits within the real 30-minute default timeout with no redesign
needed at all, since that plan doesn't enforce Lambda's kind of
universal hard maximum.

WHY THIS WORKS AS AN ANSWER
------------------------------
This correctly treats Lambda's 15-minute limit as a genuine
architectural boundary requiring redesign, not just "a longer wait,"
and cites the specific real Flex Consumption default (30 minutes) that
comfortably accommodates the described job, rather than vaguely
asserting Azure Functions "supports longer jobs."