All Vendors
  1. Home
  2. Microsoft
  3. MD-102

Microsoft MD-102 (page: 1)

Microsoft Endpoint Administrator

Updated 28-Apr-2026

Page 1 of 53 MD-102 PDF — 409 Questions

Case study

Overview

Contoso, Ltd. is a consulting company that has a main office in Montreal and two branch offices in Seattle and New York.

Contoso has the users and computers shown in the following table.



The company has IT, human resources (HR), legal (LEG), marketing (MKG), and finance (FIN) departments.

Contoso recently purchased a Microsoft 365 subscription.

The company is opening a new branch office in Phoenix. Most of the users in the Phoenix office will work from home.

Existing Environment

The network contains an Active Directory domain named contoso.com that is synced to a Microsoft Entra tenant.

All member servers run Windows Server 2016. All laptops and desktop computers run Windows 10 Enterprise.

The computers are managed by using Microsoft Configuration Manager. The mobile devices are managed by using Microsoft Intune.

The naming convention for the computers is the department acronym, followed by a hyphen, and then four numbers, for example FIN-6785. All the computers are joined to the on-premises Active Directory domain.

Each department has an organizational unit (OU) that contains a child OU named Computers. Each computer account is in the Computers OU of its respective department.

Intune Configuration

The domain has the users shown in the following table.



User2 is a device enrollment manager (DEM) in Intune.

The devices enrolled in Intune are shown in the following table.



The device compliance policies in Intune are configured as shown in the following table.



The device compliance policies have the assignments shown in the following table.



The device limit restrictions in Intune are configured as shown in the following table.



Requirements

Planned changes

Contoso plans to implement the following changes:
Provide new computers to the Phoenix office users. The new computers have Windows 10 Pro preinstalled



and were purchased already.
Implement co-management for the computers.



Technical Requirements

Contoso must meet the following technical requirements:

Ensure that the users in a group named Group4 can only access Microsoft Exchange Online from devices



that are enrolled in Intune.
Deploy Windows 10 Enterprise to the computers of the Phoenix office users by using Windows Autopilot.



Create a provisioning package for new computers in the HR department.



Block iOS devices from sending diagnostic and usage telemetry data.



Use the principle of least privilege whenever possible.



Enable the users in the MKG department to use App1.



Pilot co-management for the IT department.

You need to prepare for the deployment of the Phoenix office computers.

What should you do first?

  1. Generalize the computers and configure the Device settings from the Microsoft Entra admin center.
  2. Extract the serial number of each computer to an XML file and upload the file from the Microsoft Intune admin center.
  3. Extract the hardware ID information of each computer to a CSV file and upload the file from the Microsoft Intune admin center.
  4. Generalize the computers and configure the Mobility (MDM and MAM) settings from the Microsoft Entra admin center.
  5. Extract the serial number information of each computer to a CSV file and upload the file from the Microsoft Intune admin center.

Answer(s): C

Explanation:

To manage devices through Microsoft Store for Business and Education, you'll need a .csv file that contains specific information about the devices. You should be able to get this from your Microsoft account contact, or the store where you purchased the devices. Upload the .csv file to Microsoft Store to add the devices.
Note:
Provide new computers to the Phoenix office users. The new computers have Windows 10 Pro preinstalled and were purchased already.
Deploy Windows 10 Enterprise to the computers of the Phoenix office users by using Windows Autopilot.


Reference:

https://docs.microsoft.com/en-us/microsoft-store/add-profile-to-devices




Case study

Overview

Contoso, Ltd. is a consulting company that has a main office in Montreal and two branch offices in Seattle and New York.

Contoso has the users and computers shown in the following table.



The company has IT, human resources (HR), legal (LEG), marketing (MKG), and finance (FIN) departments.

Contoso recently purchased a Microsoft 365 subscription.

The company is opening a new branch office in Phoenix. Most of the users in the Phoenix office will work from home.

Existing Environment

The network contains an Active Directory domain named contoso.com that is synced to a Microsoft Entra tenant.

All member servers run Windows Server 2016. All laptops and desktop computers run Windows 10 Enterprise.

The computers are managed by using Microsoft Configuration Manager. The mobile devices are managed by using Microsoft Intune.

The naming convention for the computers is the department acronym, followed by a hyphen, and then four numbers, for example FIN-6785. All the computers are joined to the on-premises Active Directory domain.

Each department has an organizational unit (OU) that contains a child OU named Computers. Each computer account is in the Computers OU of its respective department.

Intune Configuration

The domain has the users shown in the following table.



User2 is a device enrollment manager (DEM) in Intune.

The devices enrolled in Intune are shown in the following table.



The device compliance policies in Intune are configured as shown in the following table.



The device compliance policies have the assignments shown in the following table.



The device limit restrictions in Intune are configured as shown in the following table.



Requirements

Planned changes

Contoso plans to implement the following changes:
Provide new computers to the Phoenix office users. The new computers have Windows 10 Pro preinstalled



and were purchased already.
Implement co-management for the computers.



Technical Requirements

Contoso must meet the following technical requirements:

Ensure that the users in a group named Group4 can only access Microsoft Exchange Online from devices



that are enrolled in Intune.
Deploy Windows 10 Enterprise to the computers of the Phoenix office users by using Windows Autopilot.



Create a provisioning package for new computers in the HR department.



Block iOS devices from sending diagnostic and usage telemetry data.



Use the principle of least privilege whenever possible.



Enable the users in the MKG department to use App1.



Pilot co-management for the IT department.

HOTSPOT (Drag and Drop is not supported)

What is the maximum number of devices that User1 and User2 can enroll in Intune? To answer, select the appropriate options in the answer area.

Note: Each correct selection is worth one point.

Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:













Box 1: 10 devices
User1 is a member of GroupA. GroupA device limit is 10.

Box 2: 15 devices
User2 is a member of GroupB. GroupB device limit is 15.




Case study

Overview

ADatum Corporation is a consulting company that has a main office in Montreal and branch offices in Seattle and New York.

ADatum has a Microsoft 365 E5 subscription.

Environment

Network Environment

The network contains an on-premises Active Directory domain named adatum.com. The domain contains the servers shown in the following table.



ADatum has a hybrid Microsoft Entra tenant named adatum.com.

Users and Groups

The adatum.com tenant contains the users shown in the following table.



All users are assigned a Microsoft 365 license and an Enterprise Mobility + Security E3 license.

Enterprise State Roaming is enabled for Group1 and GroupA.

Group1 and Group2 have a Membership type of Assigned.

Devices

ADatum has the Windows 10 devices shown in the following table.



The Windows 10 devices are joined to Microsoft Entra and enrolled in Microsoft Intune.

The Windows 10 devices are configured as shown in the following table.



All the Microsoft Entra joined devices have an executable file named C:\AppA.exe and a folder named D:
\Folder1.

Microsoft Intune Configuration

Microsoft Intune has the compliance policies shown in the following table.





The Automatic Enrollment settings have the following configurations:

MDM user scope: GroupA



MAM user scope: GroupB



You have an Endpoint protection configuration profile that has the following Controlled folder access settings:

Name: Protection1



Folder protection: Enable



List of apps that have access to protected folders: C:\*\AppA.exe



List of additional folders that need to be protected: D:\Folder1



Assignments:



- Included groups: Group2, GroupB

Windows Autopilot Configuration

ADatum has a Windows Autopilot deployment profile configured as shown in the following exhibit.



Currently, there are no devices deployed by using Windows Autopilot.

The Intune connector for Active Directory is installed on Server1.

Requirements

Planned Changes

ADatum plans to implement the following changes:

Purchase a new Windows 10 device named Device6 and enroll the device in Intune



New computers will be deployed by using Windows Autopilot and will be hybrid Microsoft Entra joined.



Deployed a network boundary configuration profile that will have the following settings:



- Name: Boundary1
- Network boundary: 192.168.1.0/24
- Scope tags: Tag1
- Assignments:
* Included groups: Group1, Group2
Deploy two VPN configuration profiles named Connection1 and Connection2 that will have the following



settings:
- Name: Connection1
- Connection name: VPN1
- Connection type: L2TP
- Assignments:
* Included groups: Group1, Group2, GroupA
* Excluded groups: --
- Name: Connection2
- Connection name: VPN2
- Connection type: IKEv2
- Assignments:
* Included groups: GroupA
* Excluded groups: GroupB

Technical Requirements

ADatum must meet the following technical requirements:
Users in GroupA must be able to deploy new computers.



Administrative effort must be minimized.

HOTSPOT (Drag and Drop is not supported)

For each of the following statements, select Yes if the statement is true. Otherwise, select No.

Note: Each correct selection is worth one point.

Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:




Box 1: No
User1 is a Cloud device administrator.

Local administrative privileges are required when enrolling an already configured Windows 10 device in Intune.

Cloud Device Administrator
Users in this role can enable, disable, and delete devices in Microsoft Entra and read Windows 10 BitLocker keys (if present) in the Azure portal. The role does not grant permissions to manage any other properties on the device.

Note: The Windows 10 devices are joined to Microsoft Entra and enrolled in Microsoft Intune.

Box 2: Yes
User2 is a Microsoft Entra joined device local administrator.

Microsoft Entra Joined Device Local Administrator
This role is available for assignment only as an additional local administrator in Device settings. Users with this role become local machine administrators on all Windows 10 devices that are joined to Azure Active Directory. They do not have the ability to manage devices objects in Azure Active Directory.

Box 3: No
User3 is a Global reader.

Global Reader
Users in this role can read settings and administrative information across Microsoft 365 services but can't take management actions.


Reference:

https://docs.microsoft.com/en-us/troubleshoot/mem/intune/no-permission-to-enroll-windows-devices https://learn.microsoft.com/en-us/azure/active-directory/roles/permissions-reference




Case study

Overview

ADatum Corporation is a consulting company that has a main office in Montreal and branch offices in Seattle and New York.

ADatum has a Microsoft 365 E5 subscription.

Environment

Network Environment

The network contains an on-premises Active Directory domain named adatum.com. The domain contains the servers shown in the following table.



ADatum has a hybrid Microsoft Entra tenant named adatum.com.

Users and Groups

The adatum.com tenant contains the users shown in the following table.



All users are assigned a Microsoft 365 license and an Enterprise Mobility + Security E3 license.

Enterprise State Roaming is enabled for Group1 and GroupA.

Group1 and Group2 have a Membership type of Assigned.

Devices

ADatum has the Windows 10 devices shown in the following table.



The Windows 10 devices are joined to Microsoft Entra and enrolled in Microsoft Intune.

The Windows 10 devices are configured as shown in the following table.



All the Microsoft Entra joined devices have an executable file named C:\AppA.exe and a folder named D:
\Folder1.

Microsoft Intune Configuration

Microsoft Intune has the compliance policies shown in the following table.





The Automatic Enrollment settings have the following configurations:

MDM user scope: GroupA



MAM user scope: GroupB



You have an Endpoint protection configuration profile that has the following Controlled folder access settings:

Name: Protection1



Folder protection: Enable



List of apps that have access to protected folders: C:\*\AppA.exe



List of additional folders that need to be protected: D:\Folder1



Assignments:



- Included groups: Group2, GroupB

Windows Autopilot Configuration

ADatum has a Windows Autopilot deployment profile configured as shown in the following exhibit.



Currently, there are no devices deployed by using Windows Autopilot.

The Intune connector for Active Directory is installed on Server1.

Requirements

Planned Changes

ADatum plans to implement the following changes:

Purchase a new Windows 10 device named Device6 and enroll the device in Intune



New computers will be deployed by using Windows Autopilot and will be hybrid Microsoft Entra joined.



Deployed a network boundary configuration profile that will have the following settings:



- Name: Boundary1
- Network boundary: 192.168.1.0/24
- Scope tags: Tag1
- Assignments:
* Included groups: Group1, Group2
Deploy two VPN configuration profiles named Connection1 and Connection2 that will have the following



settings:
- Name: Connection1
- Connection name: VPN1
- Connection type: L2TP
- Assignments:
* Included groups: Group1, Group2, GroupA
* Excluded groups: --
- Name: Connection2
- Connection name: VPN2
- Connection type: IKEv2
- Assignments:
* Included groups: GroupA
* Excluded groups: GroupB

Technical Requirements

ADatum must meet the following technical requirements:
Users in GroupA must be able to deploy new computers.



Administrative effort must be minimized.

You need to ensure that computer objects can be created as part of the Windows Autopilot deployment. The solution must meet the technical requirements.

To what should you grant the right to create the computer objects?

  1. Server1
  2. DC1
  3. GroupA
  4. Server2

Answer(s): A

Explanation:

Scenario:
The Intune connector for Active Directory is installed on Server1.
Contoso must meet the following technical requirements:
Users in GroupA must be able to deploy new computers.
Administrative effort must be minimized.
Note: To be clear, the entire domain join process will work without any direct connection to the on-premise network and domain controllers. The computer object is created on-premises through the Intune Connector for Active Directory triggered by the Windows Autopilot and Intune.


Reference:

https://blog.matrixpost.net/set-up-windows-autopilot-production-environment-part-2/




Case study

Overview

ADatum Corporation is a consulting company that has a main office in Montreal and branch offices in Seattle and New York.

ADatum has a Microsoft 365 E5 subscription.

Environment

Network Environment

The network contains an on-premises Active Directory domain named adatum.com. The domain contains the servers shown in the following table.



ADatum has a hybrid Microsoft Entra tenant named adatum.com.

Users and Groups

The adatum.com tenant contains the users shown in the following table.



All users are assigned a Microsoft 365 license and an Enterprise Mobility + Security E3 license.

Enterprise State Roaming is enabled for Group1 and GroupA.

Group1 and Group2 have a Membership type of Assigned.

Devices

ADatum has the Windows 10 devices shown in the following table.



The Windows 10 devices are joined to Microsoft Entra and enrolled in Microsoft Intune.

The Windows 10 devices are configured as shown in the following table.



All the Microsoft Entra joined devices have an executable file named C:\AppA.exe and a folder named D:
\Folder1.

Microsoft Intune Configuration

Microsoft Intune has the compliance policies shown in the following table.





The Automatic Enrollment settings have the following configurations:

MDM user scope: GroupA



MAM user scope: GroupB



You have an Endpoint protection configuration profile that has the following Controlled folder access settings:

Name: Protection1



Folder protection: Enable



List of apps that have access to protected folders: C:\*\AppA.exe



List of additional folders that need to be protected: D:\Folder1



Assignments:



- Included groups: Group2, GroupB

Windows Autopilot Configuration

ADatum has a Windows Autopilot deployment profile configured as shown in the following exhibit.



Currently, there are no devices deployed by using Windows Autopilot.

The Intune connector for Active Directory is installed on Server1.

Requirements

Planned Changes

ADatum plans to implement the following changes:

Purchase a new Windows 10 device named Device6 and enroll the device in Intune



New computers will be deployed by using Windows Autopilot and will be hybrid Microsoft Entra joined.



Deployed a network boundary configuration profile that will have the following settings:



- Name: Boundary1
- Network boundary: 192.168.1.0/24
- Scope tags: Tag1
- Assignments:
* Included groups: Group1, Group2
Deploy two VPN configuration profiles named Connection1 and Connection2 that will have the following



settings:
- Name: Connection1
- Connection name: VPN1
- Connection type: L2TP
- Assignments:
* Included groups: Group1, Group2, GroupA
* Excluded groups: --
- Name: Connection2
- Connection name: VPN2
- Connection type: IKEv2
- Assignments:
* Included groups: GroupA
* Excluded groups: GroupB

Technical Requirements

ADatum must meet the following technical requirements:
Users in GroupA must be able to deploy new computers.



Administrative effort must be minimized.

Which user can enroll Device6 in Intune?

  1. User4 and User1 only
  2. User4 and User2 only
  3. User4, User1, and User2 only
  4. User1, User2, User3, and User4

Answer(s): A



You have a Microsoft 365 E5 subscription. The subscription contains 25 computers that run Windows 11 and are enrolled in Microsoft Intune.

You need to onboard the devices to Microsoft Defender for Endpoint.

What should you create in the Microsoft Intune admin center?

  1. an attack surface reduction (ASR) policy
  2. a security baseline
  3. an endpoint detection and response (EDR) policy
  4. an account protection policy
  5. an antivirus policy

Answer(s): C

Explanation:

Onboard Windows devices to Defender for Endpoint using Intune Enable Microsoft Defender for Endpoint in Intune
The first step you take is to set up the service-to-service connection between Intune and Microsoft Defender for Endpoint. Set up requires administrative access to both the Microsoft Defender Security Center, and to Intune.
Onboard Windows devices
(After you connect Intune and Microsoft Defender for Endpoint, Intune receives an onboarding configuration package from Microsoft Defender for Endpoint. You use a device configuration profile for Microsoft Defender for Endpoint to deploy the package to your Windows devices.
The configuration package configures devices to communicate with Microsoft Defender for Endpoint services to scan files and detect threats. The device also reports its risk level to Microsoft Defender for Endpoint based on your compliance policies.
After onboarding a device using the configuration package, you don't need to do it again.) You can also onboard devices using:
*-> Endpoint detection and response (EDR) policy. Intune EDR policy is part of endpoint security in Intune. Use EDR policies to configure device security without the overhead of the larger body of settings found in device configuration profiles. You can also use EDR policy with tenant attached devices, which are devices you manage with Configuration Manager.


Reference:

https://learn.microsoft.com/en-us/mem/intune/protect/advanced-threat-protection-configure#enable-microsoft- defender-for-endpoint-in-intune



Your company uses Microsoft Intune to manage devices.

You need to ensure that only Android devices that use Android work profiles can enroll in Intune.

Which two configurations should you perform in the device enrollment restrictions? Each correct answer presents part of the solution.

Note: Each correct selection is worth one point.

  1. From Platform Settings, set Android device administrator Personally Owned to Block.
  2. From Platform Settings, set Android Enterprise (work profile) to Allow.
  3. From Platform Settings, set Android device administrator Personally Owned to Allow.
  4. From Platform Settings, set Android device administrator to Block.

Answer(s): B,D

Explanation:

Set up enrollment of Android Enterprise personally-owned work profile devices Set up enrollment for bring-your-own-device (BYOD) and personal device scenarios using the Android Enterprise personally-owned work profile management solution. During enrollment, a work profile is created on the device to house work apps and work data. The work profile can be managed by Microsoft Intune policies.
Personal apps and data stay separate in another part of the device and remain unaffected by Intune.
Set up enrollment
Complete these steps to set up enrollment for Android Enterprise devices in BYOD scenarios.
1. Sign in to the Microsoft Intune admin center.
2. Go to Devices > Enrollment device platform restrictions to set up enrollment restrictions. By default, Android Enterprise work profile is marked as allowed for personal devices enrolling in Intune. You can allow or block enrollment in device platform restrictions. Your options:
Block: Personal devices that enroll will use the Android device administrator management solution, unless device administrator enrollment is also blocked.
Allow (set by default): Personal devices that support the work profile management solution will enroll with a work profile. Android devices that don't support Android Enterprise are enrolled using the Android device administrator solution, unless device administrator enrollment is blocked.
Any device that supports Android Enterprise personal work profiles also supports the Android device administrator management solution, so if you don't want Android device administrator to be a part of enrollments, make sure to block the platform.


Reference:

https://learn.microsoft.com/en-us/mem/intune/enrollment/android-work-profile-enroll



HOTSPOT (Drag and Drop is not supported)

You have 100 Windows 11 devices enrolled in Microsoft Intune.

You need to configure the devices to retrieve Windows updates from the internet and from other computers on a local network.

Which Delivery Optimization setting should you configure, and which type of Intune object should you create? To answer, select the appropriate options in the answer area.

Note: Each correct selection is worth one point.

Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:




Box 1: Download mode
Delivery Optimization settings for Windows devices in Intune

Delivery Optimization
* Download mode
Download mode dictates which download sources clients are allowed to use when downloading Windows updates in addition to Windows Update servers.
* Etc.

Box 2: A configuration profile
With Intune, use Delivery Optimization settings for your Windows devices to reduce bandwidth consumption when those devices download applications and updates. Configure Delivery Optimization as part of your device cs.


Reference:

https://learn.microsoft.com/en-us/windows/deployment/do/waas-delivery-optimization-reference https://learn.microsoft.com/en-us/mem/intune/configuration/delivery-optimization-windows



Page 1 of 53

Share your comments for Microsoft MD-102 exam with other users:

AI Tutor Explanation 4/29/2026 5:25:25 AM

Question 1:
  • Correct answer: C. Extract the hardware ID information of each computer to a CSV file and upload the file from the Microsoft Intune admin center.

  • Why this is correct
Durban, South Africa


AI Tutor Explanation 4/29/2026 5:23:14 AM

Question 5:
  • Correct answer: A. User4 and User1 only

  • Why this is correct:
- The Automatic Enrollment setting in Intune has MDM user scope: GroupA. Only users in GroupA can enroll devices via MDM auto-enrollment. - Device6 will be enrolled via Windows Autopilot and Intune, so enrollment is allowed only for users in GroupA. - Based on the group memberships in the scenario, User4 and User1 are in GroupA, while User2 and User3 are not. Therefore only User4 and User1 can enroll Device6.
  • Quick tip for the exam:
- Remember: MDM user scope determines who can auto-enroll devices; MAM scope controls app protection enrollment. When a new Autopilot device is enrolled, the signing-in user must be in the MDM scope.
Durban, South Africa


AI Tutor Explanation 4/29/2026 5:17:10 AM

Why this is correct
  • Correct answer: C. Extract the hardware ID information of each computer to a CSV file and upload the file from the Microsoft Intune admin center.

  • Why this is correct:
- Windows Autopilot requires devices to be registered by their hardware IDs (hash) before Autopilot can deploy Windows 10 Enterprise. - Collect the hardware IDs from the new Phoenix machines, save them in a CSV, and upload that CSV in the Intune/Windows Autopilot area. This maps each device to an Autopilot deployment profile. - After registration, you can assign Autopilot profiles (Windows 10 Enterprise, etc.). Other options (serial number CSV, generalizing, or Mobility settings) are not the initial Autopilot registration steps.
Durban, South Africa


AI Tutor 👋 I’m here to help!