MD-102 domain - 23% of the exam

Prepare Infrastructure for Devices

Prepare Infrastructure for Devices is 23% of the MD-102 exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

68
Practice questions
3
Objectives
17
Medium
51
Hard

Where people go wrong

  • Swapping scope (groups) and scope tags

    The wrong answers swap the two halves of an Intune role assignment. They treat a scope tag as a way to target a profile or as a source of permissions, and treat scope (groups) as a filter on which objects appear in the console. Scope (groups) selects the users and devices an administrator may act on. Scope tags select the objects the administrator can see, and an untagged object counts as carrying the Default scope tag. Tagging a profile never changes which devices receive it.

    See it in a sample question
  • Treating Microsoft Entra join as Intune enrolment

    The wrong answers credit enrolment to the wrong event: a completed join, the Autopilot deployment profile, an Autopilot import, a compliance evaluation or a profile assignment. A join creates a device identity in the tenant only. Enrolment into Microsoft Intune is a separate step carried out by automatic enrolment, and it applies only when the MDM user scope covers the signed-in user and that user is licensed for Intune. A laptop outside that scope stays joined but unmanaged, so it receives no policy.

    See it in a sample question
  • Placing an enrolment control at the wrong stage

    The wrong answers pair an enrolment decision with a control from a different stage. A compliance policy or a configuration profile is offered as the way to refuse a handset at enrolment, and a device type restriction is expected to reach devices that have already enrolled. A device type restriction is evaluated once, while the device asks to enrol, against its platform and ownership. Handsets already enrolled are untouched, and Android device administrator is a platform that can be blocked separately from the work profile.

    See it in a sample question
  • Mixing user and device objects in a dynamic group

    The wrong answers build a group that spans both kinds of object: a device rule that reads the department of the device's owner, a user group offered in place of tagged hardware, or one dynamic group meant to hold the laptops and their users. A dynamic group is created for either user membership or device membership, and every clause in its rule is evaluated against that one object type. Device rules use device attributes such as the operating system, the join type or the Autopilot group tag, so laptops and their users need two groups.

    See it in a sample question
  • Expecting a corporate device identifier to provision

    The wrong answers give a corporate device identifier more reach than it has. It is offered as the way to enrol a reset handset again, to widen what Intune manages, or to bind a handset to an enrolment profile. The identifier only records the handset as corporate owned when it enrols. Provisioning comes from elsewhere: the registration held in Samsung Knox Mobile Enrollment restarts enrolment after a reset, and the token from a corporate owned dedicated enrolment profile, scanned or typed during setup, selects that profile.

    See it in a sample question

Objectives in this domain

What to study

The official documents this domain's practice questions cite most.

Sample questions from this domain

Free samplePrepare Infrastructure for Deviceshard

An Intune role assignment is created from the Help Desk Operator built-in role. The assignment lists the group HelpdeskAdmins as its members, a group named PerthDevices as its scope (groups), and the Default scope tag. What does the scope (groups) part of that assignment determine?

  • AWhich users and devices the assigned administrators are permitted to apply those permissions to. Correct
  • BWhich administrator accounts receive the permissions that the Help Desk Operator role carries.
  • CWhich Intune objects, such as configuration profiles and apps, the assigned administrators can see.
  • DWhich remote device actions, such as restart and sync, the assigned administrators are able to run.
An Intune role assignment separates who holds the role, which users and devices it reaches, and which objects the admin can see. An Intune role assignment is made of three independent parts: members, who hold the role; permissions, drawn from the role definition, which decide the actions; and scope (groups), which decides the users and devices those actions may target. Scope tags are a fourth, separate control that governs which Intune objects the administrator can view.

Why A is correct: Correct. The scope (groups) of a role assignment is the population of users and devices the assignment reaches, so the helpdesk can act only on members of PerthDevices.

Why B is wrong: Tempting because members and scope both name Microsoft Entra ID groups, so the two fields look interchangeable. The administrators who receive the permissions are the members of the assignment, which here is HelpdeskAdmins, not the scope.

Why C is wrong: Tempting because visibility really is restricted in Intune role-based access control, but that job belongs to scope tags. An administrator sees an object when a scope tag on the object matches a scope tag on the assignment.

Why D is wrong: Tempting because the helpdesk experience is built from remote actions, but the set of allowed actions comes from the permissions in the role definition. The scope decides the targets of those actions, not the actions themselves.

Free samplePrepare Infrastructure for Devicesmedium

A Windows 11 laptop is joined to Microsoft Entra ID by a member of staff signing in with a work account during the out-of-box experience. The device object appears in Microsoft Entra ID, but the laptop does not appear in the Microsoft Intune admin center and receives no policy. Which statement explains that outcome?

  • AJoining creates a device identity in the tenant only, and Intune management begins when the tenant's automatic enrolment configuration covers the signed-in user and that user is licensed for Intune. Correct
  • BThe device cannot appear in Microsoft Intune until a compliance policy has evaluated it and reported the device as compliant to the tenant.
  • CThe device has to be imported into Windows Autopilot as a registered device before Microsoft Intune is able to enrol it and deliver any policy.
  • DAssigning a device configuration profile to a group that contains the new device object is what starts its enrolment into Microsoft Intune.
Microsoft Entra join creates a device identity; Intune management is a separate step that depends on automatic enrolment scope and licensing. Microsoft Entra join and mobile device management enrolment are two distinct operations. The join establishes the device object and the device's trust with the tenant, which is what Conditional Access can evaluate. Management by Microsoft Intune follows only when the tenant's automatic enrolment configuration brings the signing-in user into scope and that user carries a licence permitting enrolment, so a joined but unenrolled device is a normal intermediate state rather than a fault.

Why A is correct: Correct, because the join operation creates the device object and the trust relationship with the tenant, while mobile device management is a separate step driven by the tenant's automatic enrolment scope and the user's licence.

Why B is wrong: Tempting because compliance state is the first thing many administrators look at on a device record, but a compliance policy can only evaluate a device that Intune already manages, so compliance is a consequence of enrolment rather than a condition of it.

Why C is wrong: Tempting because Autopilot is the usual provisioning route for new corporate hardware, but Autopilot is a provisioning experience layered on top of join and enrolment and is not a prerequisite for either.

Why D is wrong: Tempting because assignment is how policy reaches devices, but an assignment can only be delivered to a device that is already enrolled, so it cannot be the trigger for enrolment itself.

Free samplePrepare Infrastructure for Deviceshard

An administrator creates a device type restriction that blocks personally owned Android Enterprise work profile enrolment and gives it the highest priority. Personally owned Android handsets that were enrolled a month earlier still appear in the Microsoft Intune admin center and still receive their assigned policies. What does this behaviour tell you about how a device type restriction works?

  • AThe restriction is evaluated at enrolment and again at every policy check-in, so the handsets that enrolled a month earlier will drop out of management at their next check-in.
  • BThe restriction takes effect once the built in All Users restriction is deleted, because that default restriction outranks any custom restriction whatever priority it has been given.
  • CThe restriction is evaluated while a device is asking to enrol, so it decides which devices are allowed to join management and has no bearing on devices that finished enrolling earlier. Correct
  • DThe restriction marks the handsets that enrolled a month earlier as noncompliant, and a Conditional Access policy that requires a compliant device is what ends their access to resources.
An enrolment restriction is a gate on the enrolment request, so it never re-evaluates or removes a device that is already enrolled. Enrolment restrictions are enforced by the enrolment service at the moment a device presents its platform, version and ownership, and the verdict is spent there. Nothing about the restriction is written to the enrolled device or checked again afterwards, so tightening a restriction shapes future enrolments only. Dealing with devices that predate the change is a separate action, such as retiring them.

Why A is wrong: Tempting because most Intune policy really is re-evaluated on a check-in cycle, which invites the assumption that a restriction behaves the same way. Enrolment restrictions are not delivered to a managed device and take no part in the check-in conversation, so no later evaluation happens.

Why B is wrong: Tempting because the built in restriction does apply to everyone and cannot be deleted, which makes it feel dominant. It sits at the lowest priority instead, so a custom restriction assigned to a group is evaluated ahead of it.

Why C is correct: Correct. An enrolment restriction is a gate on the enrolment request itself, evaluated once against the platform and ownership the device presents, which is why devices already past that gate are untouched.

Why D is wrong: Tempting because it describes the real report and block sequence between a compliance policy and Conditional Access. An enrolment restriction produces no compliance state at all, so nothing is passed to Conditional Access here.

Free samplePrepare Infrastructure for Devicesmedium

A warehouse fleet of Windows 11 laptops is registered with Windows Autopilot, and every one of those hardware records carries the group tag Warehouse. A device configuration profile must reach exactly those laptops once they are provisioned, and no administrator may maintain the membership by hand. Which approach produces a group whose membership resolves to those laptops?

  • ACreate an assigned security group and add each laptop to it after provisioning, working from the serial number list that the hardware supplier provides with every delivery.
  • BCreate a dynamic device group whose membership rule matches the Autopilot group tag, which is carried on the Microsoft Entra device object as an order identifier held among the device's physical identifiers. Correct
  • CCreate a dynamic device group whose membership rule matches the device display name against a Warehouse prefix, relying on the device name template in the Autopilot deployment profile.
  • DCreate a dynamic user group whose membership rule matches the department recorded against the people who work in the warehouse, then assign the device configuration profile to that group.
An Autopilot group tag is stored on the Microsoft Entra device object, so a dynamic device membership rule can resolve to tagged hardware without manual upkeep. Autopilot registration writes the group tag onto the resulting Microsoft Entra device object as an order identifier within the device's physical identifiers. A dynamic device group evaluates its rule against device object properties, so a rule matching that value takes in every laptop registered with the tag and drops any device whose registration changes, which is what removes the manual maintenance the requirement forbids. A device display name or a user attribute is not the tag and does not track it.

Why A is wrong: This does produce the right membership and is tempting because the supplier list is accurate on the day it arrives, but the membership is maintained by an administrator adding members, which the requirement rules out.

Why B is correct: Correct, because the group tag is written onto the device object during Autopilot registration, so a device membership rule matching that value resolves to the tagged laptops and is re-evaluated by the directory without an administrator touching it.

Why C is wrong: A name template is a plausible hook because it is configured on the same profile, but the name is a cosmetic property that can be changed on the device and is not the group tag, so the membership would not reliably track the tagged hardware.

Why D is wrong: Targeting the workers looks equivalent because they are the people using the laptops, but a user group resolves to user objects and follows the person to any device they sign in to, so it does not identify the tagged hardware.

Free samplePrepare Infrastructure for Deviceshard

One corporate Samsung handset was enrolled in Microsoft Intune as a fully managed device through Samsung Knox Mobile Enrollment. A second handset in the same tenant was enrolled by its owner, who installed the Company Portal app and enrolled it as a personally owned work profile device. Both handsets are wiped back to factory settings. Which statement describes the difference in what happens next on the two handsets?

  • AThe Knox registered handset is pushed into enrolment again during setup because its registration is held by the service rather than on the handset, while the personally owned handset stays unmanaged until its owner opens the Company Portal. Correct
  • BBoth handsets run their original enrolment again with nobody touching them, because the enrolment profile is written to a device partition that a factory reset is built to leave alone.
  • CNeither handset enrols again until somebody starts it, because a factory reset deletes the record in Intune and the registration held by the service that provisioned the handset.
  • DThe Knox registered handset enrols again once an administrator uploads its serial number as a corporate device identifier, while the personally owned handset resumes from the Intune record it already had.
Registration based corporate enrolment survives a factory reset because the hardware is known off the device; user driven enrolment does not. Knox Mobile Enrollment binds an enrolment configuration to a hardware identifier held in the Knox portal, so any reset handset that reaches the network during setup is matched and provisioned again without help. A personally owned work profile enrolment is started by a person on the device and recorded nowhere that can reach a freshly wiped handset, so it stays unmanaged until the owner repeats the enrolment.

Why A is correct: Correct. Knox Mobile Enrollment keys the profile to the hardware identity in the portal, so a reset handset is recognised at setup and provisioned again, whereas a user driven work profile enrolment leaves nothing outside the device that could restart it.

Why B is wrong: Tempting because a reset really does preserve firmware and some vendor partitions. Enrolment state lives in the user data that a reset clears, so a repeat enrolment depends on an off device registration rather than on anything surviving on the handset.

Why C is wrong: Tempting because a wiped handset does stop checking in and its record can look abandoned. A reset performed on the device cannot reach into the Knox portal or the Intune record, so the registration that provisioned the handset is still in place.

Why D is wrong: Tempting because corporate device identifiers are a genuine way to classify hardware before it enrols. They declare ownership rather than provision a device, and the Knox registration already covers this handset, so no upload is required.

Other domains in this exam

See also the MD-102 cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by Microsoft. Original, blueprint-aligned practice material only.