Exercise 1: Staying Within the Free Tier — Possible Solution
====================================================================

The workload runs roughly 200 times per day. Over a typical month
(using 30 days for a round estimate):

    200 requests/day x 30 days = 6,000 requests/month

The chapter's own real, documented free tier covers 1,000,000 requests
per month at no cost. 6,000 requests is a tiny fraction of that limit
-- roughly 0.6% of the free tier's own request allowance.

ANSWER: Yes, this workload would comfortably stay within Lambda's real
free tier for requests -- 6,000 requests/month is far below the real
1,000,000-request monthly threshold, using well under 1% of the
available free allowance. (The duration side of the free tier, 400,000
GB-seconds/month, would also need checking against the function's own
memory setting and the 2-second-per-run duration, but at this real
request volume it's very unlikely to be the limiting factor either.)

WHY THIS WORKS AS AN ANSWER
------------------------------
This does the actual real arithmetic against the chapter's own
specific documented free-tier figure, rather than just asserting the
workload "sounds small," and correctly identifies that a full answer
would also need to check the duration-based half of the free tier,
not just the request count alone.