Challenge 2: Pick the Right Tool — Possible Solution
====================================================================

(a) Quickly checking whether a public GET endpoint is up — BROWSER.
This is the simplest possible check on the simplest possible request
type: no headers, no body, no auth, just "does this URL return
something." Opening Postman or writing a curl command for this is
strictly more setup than pasting the URL into the address bar for the
exact same answer.

(b) A teammate needs to reproduce your exact request with no Postman
installed — CURL. A curl command is a single, self-contained,
copy-pasteable line of text that works in any terminal on any machine
— no app installation required, no shared Postman workspace needed.
This is exactly why cURL is the tool of choice for bug reports and
reproduction steps.

(c) A request definition that should be reviewed in a pull request
alongside the code that calls it — VS CODE .HTTP FILE. A .http file is
plain text living in the same Git repository as the application code,
so it shows up in a diff, gets reviewed like any other file, and stays
version-controlled — none of which is true of a request saved only
inside Postman's own local application state (without deliberately
exporting/syncing the collection, which Chapter 3 covers as its own
separate concern).