Exam MD-102 topic 1 question 135 discussion

As MDM Automatic Enrollment is already configured the Provisioning Package can be used to configure the Wi-Fi connection on workgroup devices before the enrollment.

Provisioning Package fulfils both requirements. You can automatically connect devices to corp WIFI and join to Entra which will enroll devices into Intune.

A. a provisioning package. Provisioning packages allow you to apply settings and configurations to Windows devices, including connecting to wireless networks and enrolling in Intune, without the need for Active Directory or Azure AD. This is particularly useful for devices in a workgroup environment.

question, you have 100 existing devices enrolled that need to a connection to wifi, AND enroll 100 new devices. Why would you not use the configured auto enrollment with a device configuration profile? i dont know if the provisioning package can be used on existing devices. And it would mean if i understand it correctly that you need to manuel click the provisioning package either on online folder or usb to install for 200 devices. While the device configuration policy is applied automatically after assigned?

A is correct https://learn.microsoft.com/en-us/mem/intune/enrollment/windows-bulk-enroll C is allready active

A is correct.

https://learn.microsoft.com/en-us/mem/intune/enrollment/windows-bulk-enroll "" Join new Windows devices to Microsoft Entra ID and Intune. To bulk enroll devices for your Microsoft Entra tenant, you create a provisioning package with the Windows Configuration Designer (WCD) app. Applying the provisioning package to corporate-owned devices joins the devices to your Microsoft Entra tenant and enrolls them for Intune management. Once the package is applied, it's ready for your Microsoft Entra users to sign in. ""

A the way

Should be A

A is correct

voting for A - provisioning package, as this will deliver VPN or whatever configuration is needed no GPO here as devices are in workplace auto enrollment is said its already enabled device config profile is after enrollment

A agreed.

Should be A

The answer appears to be A due to the fact that the MDM autoenrollment is already configured.