Exercise 1: A Different Layer, Not a Missing Feature — Possible Solution
====================================================================

THE DISTINCTION EXPLAINED
------------------------------
Per this chapter, Windows 11's Public/Private profile makes one blanket decision per network that simultaneously controls both firewall behavior and discovery/sharing visibility, and picking the wrong one silently changes all of that behavior at once. macOS never asks that single blanket question at all - it doesn't have an equivalent per-network classification. Instead of missing that capability, it distributes the same underlying goal (controlling what's exposed to a network) across several smaller, independent controls, each covering a narrower piece of the same overall problem.

THE THREE SEPARATE CONTROLS MACOS USES INSTEAD
------------------------------
1. The system Firewall, toggled independently in System Settings > Network > Firewall.
2. File Sharing, off by default and toggled independently in the Sharing pane.
3. Per-app "Local Network" permission prompts (since Big Sur), which ask at the individual app level whether that specific app may access the local network at all.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly explains that macOS achieves the same underlying goal as Windows 11's Public/Private system through several independent, narrower controls rather than one blanket per-network toggle, and correctly names all three of those controls (Firewall, File Sharing, per-app Local Network permissions).