Challenge 1: Looking for a Missing "Save" Button — Solution Walkthrough

The answer:

There's no Save command because there's no local file being written to
in the first place. Per this chapter's own material, a Figma design
lives on Figma's own servers from the moment it's created, with every
change continuously synced to the cloud as it happens — the same
underlying model Google Workspace's own Docs, Sheets, and Slides
already use for documents.

Why this isn't actually a problem:

The designer's anxiety comes from expecting Figma to behave like
Illustrator's own file-based model, where an unsaved change really can
be lost if the application closes unexpectedly. Figma's continuous
cloud sync means there's no equivalent "unsaved state" to lose — every
edit is already stored the moment it happens, not held locally until a
manual save action commits it.

Why this connects to the chapter's own warning box:

This chapter's own warning box makes the same point from a slightly
different angle — no Save button doesn't mean no safety net, since
Figma's own automatic version history (like Google Workspace's) sits
underneath this same continuous-sync model, ready to recover an
earlier state if needed.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise checks that the absence of a Save command is correctly
traced back to Figma's cloud-native architecture having no local file
to protect in the first place, not to a missing safety feature.