Exercise 1: Where the Routing Wiring Actually Lives — Possible Solution
====================================================================

DJANGO'S APPROACH
------------------------------
Django keeps the URL-to-code mapping in a dedicated urls.py file, using path() to associate a URL pattern with a specific view function imported from views.py. The view function itself, in views.py, contains only the actual logic - it has no direct knowledge of what URL will trigger it. The two pieces of information (which URL, and what code runs) are declared in two separate files and wired together explicitly by name.

FASTAPI'S APPROACH
------------------------------
FastAPI combines both pieces of information in a single place: a decorator like @app.get("/path") is placed directly above the function it applies to, so the URL pattern and the handler code live together, in the same file, right next to each other.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly identifies that Django separates the URL pattern (urls.py) from the handling code (views.py) as two distinct files wired together, while FastAPI co-locates both in one place via a decorator directly above the function, correctly describing where "this URL maps to this code" is actually declared in each framework.