Challenge 1: Create and Confirm a Database — Possible Solution
====================================================================

STEP 1: Switch to the new database
  use shop

At this point, running "show dbs" would NOT show "shop" in the list
yet — this is exactly this chapter's gotcha. Switching context with
"use" doesn't create the database on its own.

STEP 2: Insert at least one document into a collection
  db.products.insertOne({ name: "Notebook", price: 3.50 })

STEP 3: Now confirm it exists
  show dbs

"shop" now appears in the list, because it has actually been
persisted to disk — the insert is what triggered MongoDB to really
create the database, not the earlier "use" command.

WHY THIS WORKS AS AN ANSWER
------------------------------
The key point being tested is the two-step reality behind what looks
like database creation: "use shop" only changes what your CURRENT
SESSION is pointed at, and MongoDB defers actually creating the
database until the first real write happens. Any correct answer has
to include an actual insert as the step that makes "shop" genuinely
exist — simply repeating "use shop" or running read-only commands
against it would never cause it to appear in "show dbs".