MD-102 Exam Review: Intune Enrollment, Co-Management, and Windows Support Lifecycles (Q1–Q5)
Why These Intune and Windows Management Answers Matter (MD-102/MS-102 Mini Blog)
If you are preparing for MD-102 or MS-102, many questions are not testing whether you memorized a setting name. They test whether you recognize the management model behind the scenario. The five questions below all revolve around the same theme: what must be configured first before devices can be managed, supported, or co-managed.
Question 1: “My Windows 10 devices must meet Intune requirements”
When an exam question asks what you need to do to manage Windows devices with Intune, think in two layers:
- Tenant readiness in Entra ID (Azure AD)
- Device readiness through enrollment
What you configure in Entra ID
You enable Mobility (MDM and MAM). This is where you define Intune as the MDM authority and allow devices to be managed through MDM.
What you configure in Intune
You ensure device enrollment is in place. Without enrollment, Intune cannot deliver configuration profiles, compliance policies, or apps to that device.
Exam takeaway: If the device is not enrolled, Intune cannot manage it, even if your tenant is configured correctly.
Question 2: “How long will devices remain supported?”
This kind of question is usually about Windows feature update servicing, not monthly quality updates. The servicing timeline depends heavily on the Windows edition being used in each office.
Typical exam logic:
- Enterprise/Education are often supported longer than Pro for feature updates.
- Some Windows 10 Enterprise/Education releases follow a 30-month lifecycle, while Pro commonly follows 18 months.
So if the scenario describes different editions in different locations, the exam expects you to map servicing time to edition.
Exam takeaway: When you see “supported for how long,” immediately ask: Which edition and which feature update servicing model?
Question 3: “Can I manage Device1 with Intune and Configuration Manager?”
This is classic co-management.
In co-management, you typically:
- Enable co-management in Configuration Manager
- Target devices using a device collection
- Use that collection to control which clients are enrolled or transitioned into co-management
So, adding Device1 into the right Configuration Manager device collection can absolutely be part of meeting the goal, assuming the co-management configuration exists.
Answer: Yes
Why: In many real deployments, collections define the scope of co-management enrollment and workload targeting.
Exam takeaway: When co-management appears, look for “device collections” as the targeting mechanism.
Question 4: “What if I just create a configuration profile?”
This question tests whether you can separate policy delivery from management onboarding.
A configuration profile is something you push after a device is already under management. It does not establish:
- Hybrid Azure AD Join
- Automatic MDM enrollment
- Co-management enablement
So creating a device configuration profile in the Device Management admin center is not the fix for a co-management onboarding requirement.
Answer: No
Why: Profiles configure devices. They do not onboard them into co-management.
Exam takeaway: If the requirement is “make it co-managed,” a configuration profile alone will never be the correct first step.
Question 5: “Minimum support technicians required for Montreal mobile devices”
This is really a question about Device Enrollment Manager (DEM) capacity planning.
DEM accounts are used when you need technicians (or staging staff) to enroll many devices, often without direct user sign-in during enrollment.
The question’s correct option is:
Minimum technicians required: 4
Exam takeaway: When you see “support technicians enrolling many mobile devices,” translate it to DEM scaling and enrollment capacity.
Final Exam Pattern to Remember
These questions look different, but they share one pattern: setup order matters.
- Entra ID MDM settings must exist before Intune management works.
- Enrollment must occur before policies apply.
- Co-management requires onboarding steps and targeting, not just profiles.
- Windows servicing questions always depend on edition and lifecycle model.
- Technician enrollment scenarios usually point to DEM.
