5. Manage and Secure Applications (15–20%)
Users don't ask for a compliant device or a well-tuned update ring. They ask for Outlook, Teams, the expense app and the line-of-business tool the warehouse runs on. Everything in Phases 2 to 4 exists so that apps can reach people safely, and this domain, worth 15–20% of the exam, is where that promise is kept or broken. On the job, a failed install is a lost workday and a leaked customer file is an incident. On the exam, app questions are dense with specifics: which app type to choose, which assignment intent wins, which policy works without enrollment.
The mental model is a split between delivering and protecting. Delivery (section 5.1) moves apps onto devices: you package or pick the app, assign it with an intent, and watch it install. Protection (section 5.2) governs what happens to organization data inside apps once they're running, through app protection policies, the Conditional Access grant that insists on them, and app configuration policies that pre-set apps for users. Delivery mostly depends on enrollment. Protection deliberately doesn't, which is why it's the answer for personal phones.
⚠️ Exam Trap: "App protection" and "app deployment" are different jobs. A scenario that asks you to stop users copying work email into personal apps on unenrolled phones wants an app protection policy, not a Required app assignment — Required assignments aren't supported on unenrolled devices at all.