Challenge 3: One Vector File Producing Both a Web SVG and a Print PDF — Solution Walkthrough

The answer:

Per Chapter 1's own core paradigm, a vector file stores mathematical
descriptions of shapes rather than a fixed pixel grid. Neither an SVG
export nor a PDF export requires converting that underlying
description into pixels ahead of time — both formats preserve the
same vector data, just packaged for a different destination (a
browser for SVG, a print or general-purpose viewer for PDF).

Why this avoids maintaining two separate source files:

Because the underlying paths are identical regardless of which format
they're exported to, both exports are generated from exactly the same
source file, at export time, rather than requiring the artwork itself
to be redrawn or resized differently for each destination. This is
different from raster work, where a web-resolution image and a
print-resolution image genuinely are different files with different
pixel grids.

Why this matters practically:

A change made once to the vector source — fixing a shape, adjusting a
color — is reflected correctly in every future export, web or print,
without needing to separately update multiple resolution-specific
files the way raster workflows often require.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise checks that producing multiple export formats from one
vector source is correctly traced back to resolution independence
(no fixed pixel grid to duplicate or resize separately for each
destination).