Exercise 1: What ->get() Actually Returns — Possible Solution
====================================================================

WHAT ->get() RETURNS
------------------------------
Per this chapter, ->get() is a TERMINAL method - calling it executes the built-up query immediately, right at that point in the code, and returns a real Eloquent Collection: an already-fetched, enhanced array-like object containing the actual result rows, with its own useful methods like ->map(), ->filter(), and ->pluck().

WHY YOU CAN'T CHAIN ANOTHER ->where() ONTO IT
------------------------------
Per this chapter, a Collection is not a query anymore - it's the finished, already-executed RESULT of one. The chained ->where()/->orderBy() calls that come BEFORE ->get() operate on a query Builder object, which is what stays lazy and buildable. Once ->get() runs, that Builder's job is done, and what you're left holding is real, static data already pulled from the database - there's no database connection or pending query left attached to a Collection for a further ->where() to refine. Calling ->where() on the returned Collection either wouldn't work at all, or (Collection does have its own separate ->where() method for filtering an in-memory PHP collection) would filter the ALREADY-FETCHED PHP data in memory, not run any new SQL against the database.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly explains that ->get() is a terminal method that executes the query and returns an already-fetched Collection, and correctly explains why that Collection is no longer a queryable database object - the query itself is finished, and only in-memory PHP data remains.