Exercise 3: Containers vs. Partitions, and APFS Among Its Peers — Possible Solution
====================================================================

HOW APFS CONTAINERS DIFFER FROM FIXED PARTITIONING
------------------------------
Per this chapter, traditional partitioning carves a disk into fixed-size sections decided up front - creating a new partition means committing to a specific size before knowing exactly how much space will actually be needed. An APFS container instead groups related volumes together and lets every volume in that container dynamically share the same pool of free space. A new APFS volume doesn't require choosing a fixed size at creation; it can grow or shrink as needed, limited only by the total space available across the whole container.

HOW THE FINDING-BOX POSITIONS APFS RELATIVE TO BTRFS AND ZFS
------------------------------
Rather than treating APFS as an unrelated fourth filesystem design, the chapter frames it as Apple's own single-vendor answer to the identical underlying problem Btrfs and ZFS were each independently built to solve: copy-on-write, cheap native snapshots, and integrity checking built directly into the filesystem itself, rather than requiring separate layered tools the way ext4 depends on LVM for anything snapshot-like.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly explains the practical difference between committing to a fixed partition size up front versus dynamically sharing space across a container's volumes, and correctly summarizes the finding-box's framing of APFS as a parallel, single-vendor solution to the same problem Btrfs and ZFS solve, rather than a separate, unrelated design.