1. Indie game live only in DE + FR storefronts
Who: A two-person studio shipping a free game with rewarded ads that already call ATT.
Task: Before enabling iOS 27.2, confirm they cannot keep the classic alert in Germany and France, and prepare sheet copy.
Steps: Select five-country region and ATT yes on the matrix. Add NSUserTrackingMarkdownUsageDescription with short bullets about ad personalization. Adopt requestTrackingAuthorizationPreferringExpandedInterface. Test a German-region device and account.
Result: Path badge shows forced alternative sheet; ship checklist includes Markdown key and five-country device test. Failure symptom avoided: one-line alert layout looking broken on a full-page sheet.
2. Pan-EU productivity app that wants one expanded UX
Who: A B2C SaaS iOS client sold across the EU, including NL and ES plus the five mandated countries.
Task: Show the same expanded ATT sheet everywhere in the EU so privacy copy and screenshots stay consistent.
Steps: Choose multi-region on the matrix, set expand preference to yes, keep both usage description keys, pass preferExpandedInterface: true, and QA DE (forced) plus NL (flag-dependent) plus US (classic).
Result: One EU sheet design; non-EU still classic. Failure symptom avoided: designers only mocking the alert while NL users suddenly see the sheet after a flag flip.
3. US-primary app with no EU storefront yet
Who: A US startup binary that does not list EU countries today but may expand next quarter.
Task: Decide whether to invest in Markdown strings and the new API now.
Steps: Select outside-EU on the matrix. Keep classic NSUserTrackingUsageDescription. Optionally stub Markdown and the 27.2 API behind availability checks so a future EU listing is a config change, not an emergency rewrite.
Result: Unaffected badge for display behaviour today; checklist reminds them to re-run the matrix before EU launch. Failure symptom avoided: assuming EU rules already changed US alert UI.