Exercise 2: Why match's Encrypted Git Storage Genuinely Helps a Real Team — Possible Solution
===================================================================================================

Chapter 4 established that a certificate is a real public/private key
pair, with the private key staying securely in Keychain on the
specific Mac that created it, and that a provisioning profile binds
that certificate together with the app's own App ID, entitlements, and
(for Development/Ad Hoc) an authorized device list. Every one of those
real pieces has to genuinely match across every developer's own
machine, and across whatever machine actually runs a real CI build, or
the build will fail to sign correctly.

Without a shared, coordinated system, each individual developer on a
real team would need to separately request, download, and manually
install their own copies of these real certificates and profiles -
and any time one gets renewed, revoked, or regenerated, every other
team member's own local copy silently goes stale, a genuinely common
and frustrating real source of "it builds on my machine but not
theirs" failures.

match's real approach - storing certificates and provisioning profiles
in one shared, encrypted git repository - solves this directly: every
team member, and any real CI machine like Xcode Cloud or a Fastlane
lane running elsewhere, can pull the exact same, currently valid
signing identity from one single, coordinated real source, rather than
each maintaining their own separate local copy that can drift out of
sync. The encryption specifically protects the real private key
material described in Chapter 4, since it's sensitive enough that it
genuinely shouldn't sit in a plain, unencrypted git repository.

ANSWER: match solves the real coordination problem Chapter 4's own
certificate/profile material implies for a team - without it, every
developer and CI machine needs its own separately-maintained copy of
the same signing identity, which easily drifts out of sync. Storing
them in one shared, encrypted git repository lets the whole team and
any CI system pull the exact same, currently valid certificate and
profile from a single source, while the encryption protects the real
sensitive private-key material involved.

WHY THIS WORKS AS AN ANSWER
------------------------------
This connects match's own real function directly to the specific
certificate/profile mechanics Chapter 4 established, explaining the
concrete team-coordination problem it solves rather than just
describing what match does in isolation.