MD-102 Prepare infrastructure for devices Practice Question
Which THREE factors should you consider when planning a Microsoft Intune migration from Configuration Manager?
⚠ Common exam trap
A common mix-up: candidates assume Intune can manage on-premises servers like Configuration Manager does, or that an on-premises Intune server exists, when in reality Intune is purely cloud-based and cannot replace Configuration Manager for server management.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The use of co-management to gradually move workloads.
Option A is correct because co-management lets you attach Configuration Manager-managed devices to Intune and progressively shift workloads such as compliance policies, resource access, and Windows Update policies from Configuration Manager to Intune, enabling a controlled, phased migration rather than a disruptive cutover. Option C is correct because existing Configuration Manager applications and packages must be repackaged or converted into Intune-supported formats such as Win32 apps (.intunewin), line-of-business (LOB) apps, or Microsoft Store apps, and this compatibility assessment is essential for planning remediation and testing effort. Option E is correct because Intune is a cloud service, so devices must reach Microsoft endpoints over the internet, making bandwidth, proxy, firewall, and content-download requirements (for example, Windows Update for Business and Win32 app content) a key planning factor. Option B is not correct because Intune does not manage on-premises Windows Server workloads the way Configuration Manager does; servers generally remain with Configuration Manager or another on-premises tool. Option D is not correct because Intune is a fully cloud-hosted Microsoft service and requires no on-premises Intune server; only the Configuration Manager site infrastructure remains on-premises during co-management.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The use of co-management to gradually move workloads.
Why this is correct
Co-management lets you move workloads such as compliance policies and Windows Update rings incrementally, keeping Configuration Manager authoritative until each is proven. This staged authority transfer satisfies the migration factor of controlling risk while devices transition to Microsoft Intune.
- ✗
The ability to manage on-premises servers with Intune.
Why it's wrong here
Intune cannot manage on-premises servers; that remains Configuration Manager's role, so this is not a migration planning factor. It tempts because co-management and tenant attach blur the boundary, yet server workloads stay on-premises and are managed through Configuration Manager or Azure Arc.
- ✓
The compatibility of existing application packages with Intune formats (Win32, LOB).
Why this is correct
Intune deploys Win32 and line-of-business apps rather than Configuration Manager's legacy package and program model, so each existing package must be repackaged or replaced. Assessing this format compatibility satisfies the migration factor of application readiness before cutover.
- ✗
The need for an on-premises Intune server.
Why it's wrong here
Intune is a cloud service with no on-premises server component, so no such server needs planning. It tempts because Configuration Manager sites are on-premises infrastructure that must be sized and maintained, and hybrid scenarios do involve connectors, but Intune itself requires none.
- ✓
Network bandwidth requirements for device communication with Intune.
Why this is correct
Intune-managed devices communicate directly with Microsoft cloud endpoints rather than on-premises distribution points, so internet egress and bandwidth must be sized for policy, app and update traffic. This satisfies the migration factor of network capacity for cloud-based device communication.
Go deeper
Related to this question
Learn chapter
Managing Conditional Access for Devices
Key term
Co-management
Co-management is a device management strategy that lets organizations simultaneously manage Windows 10 and later devices using both Configuration Manager (on-premises) and Microsoft Intune (cloud), enabling a gradual transition to modern management.
Key term
Win32 app
A Win32 app is a traditional Windows program that runs directly on a Windows PC, using the same system resources and displaying a standard window with menus and buttons.
About these practice questions
This MD-102 question is part of Courseiva's 556-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This MD-102 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the MD-102 exam.