Exercise 2: Why Scoped Deploys Are Preferable — Possible Solution
====================================================================

WHY SCOPED DEPLOYS ARE PREFERRED
------------------------------
A full firebase deploy redeploys hosting, functions, and Firestore rules/indexes together, regardless of which of them actually changed. If only a Cloud Function was edited, redeploying the entire React build and Firestore rules along with it adds unnecessary time to the deploy and introduces unnecessary risk - any of those other pieces could theoretically fail to deploy cleanly, or interact with the environment in some unexpected way, even though nothing about them actually changed.

WHY IT "TECHNICALLY WORKS" ISN'T THE SAME AS "PREFERABLE"
------------------------------
A full deploy would still succeed and end up in the same correct final state most of the time - it isn't wrong, just less precise. Deploying only what changed (--only functions, for instance) keeps each deploy small, fast, and easy to reason about: if something goes wrong, the scope of what could have caused it is immediately narrower, since unrelated pieces of the app were never touched by that particular deploy at all.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly explains that a full deploy touches every piece regardless of what actually changed, adding avoidable time and risk, and correctly distinguishes "would still work" from "is the better practice," identifying narrower scope and easier troubleshooting as the real benefit of scoped deploys.