Exercise 1: What a Database-Only Backup Would Still Lose — Possible Solution
====================================================================

WHAT A DATABASE BACKUP ACTUALLY CONTAINS
------------------------------
Per this chapter's own table, the database holds "every Post, Page,
comment, and user account - the MySQL layer from WordPress
Fundamentals 1." A database-only backup preserves all of this content
data, but nothing beyond it.

WHAT WOULD STILL BE LOST IN A SERVER FAILURE
------------------------------
Per this chapter's own table, "the files" - a genuinely separate
category from the database - include "WordPress core, the active
theme, every plugin, and the media library." None of these live inside
the database at all, so a database-only backup provides zero protection
for them. In a full server failure, the site owner would lose: every
uploaded image, video, and document in the media library; the active
theme and any customizations made to it; every installed plugin and
its own configuration; and the WordPress core software installation
itself.

WHY THIS MATTERS PRACTICALLY, NOT JUST TECHNICALLY
------------------------------
Even with the database fully intact, restoring the site would mean
starting from a bare WordPress install with no theme, no plugins, and
critically, every single image or file ever referenced inside a Post
or Page would be a broken link - the database would still contain
the TEXT referencing those media files (and know their filenames), but
the actual image/video/document files themselves would be entirely
gone, since those live in the files layer, not the database.

WHY THIS SHOWS THE SITE OWNER'S BELIEF WAS WRONG
------------------------------
Per this chapter, "a real WordPress backup needs two genuinely
separate things." The site owner backed up only one of the two
required pieces, meaning their site is only partially protected -
"fully protected" significantly overstates what a database-only backup
actually accomplishes, since an entire category of essential site
material (the files) has no backup coverage at all.

WHY THIS WORKS AS AN ANSWER
------------------------------
It precisely restates what a database backup does and doesn't cover per
this chapter's own table, lists the concrete categories of loss that
follow from the missing "files" backup, and explains the practical
consequence (broken media references, a bare reinstall) rather than
stating the gap only in the abstract.