Courseiva

MD-102 Prepare infrastructure for devices Practice Question

Which TWO actions can you perform using Windows Autopilot in Microsoft Intune?

⚠ Common exam trap

A common mix-up: candidates confuse Windows Autopilot's OOBE customization capabilities with broader device management features like security baselines or third-party app deployment, which are handled by Intune policies after enrollment, not during the Autopilot provisioning phase.

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

✓

Convert existing devices to Autopilot by uploading hardware hash

Option B is correct because Windows Autopilot supports registering existing devices by collecting their hardware hash (via the Get-WindowsAutoPilotInfo script or similar) and uploading it as a CSV to Intune, which creates an Autopilot device record so the device can be reset and reprovisioned through the Autopilot flow. Option D is correct because Autopilot's core purpose is to define and customize the out-of-box experience (OOBE) using deployment profiles, including settings like the privacy prompts, user account type, language/region, and whether the user is a standard user or local admin. Option A is not an Autopilot action; security baselines are enforced through Intune configuration profiles/policies, not through Autopilot itself. Option C is not specific to Autopilot; third-party applications are deployed via Intune app deployment (Win32 apps, MSI, Microsoft Store apps, etc.), which can be assigned to Autopilot-enrolled devices but is not an Autopilot capability. Option E is not an Autopilot function; BIOS/UEFI settings are typically configured through vendor tools (e.g., Dell Command | Configure, HP Client Management Script Library) or Intune's OEM-specific configuration, not Autopilot.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    Enforce security baselines on devices

    Why it's wrong here

    Security baselines are assigned through Intune configuration profiles, not through Autopilot, which handles device enrolment, provisioning and profile delivery during out-of-box setup. It is tempting because Autopilot and Intune share the same portal and both touch device configuration, but baseline enforcement is a separate Intune workload applied after enrolment completes.

  • ✓

    Convert existing devices to Autopilot by uploading hardware hash

    Why this is correct

    Uploading a hardware hash registers an existing device with the Autopilot deployment service, enabling it to be reset and reprovisioned through the Autopilot out-of-box experience. This satisfies the stem's requirement for a supported Autopilot action in Microsoft Intune, converting already-deployed hardware into Autopilot-managed devices without manual imaging.

  • ✗

    Deploy third-party applications automatically

    Why it's wrong here

    Third-party application deployment is performed by Intune app policies or Win32 app assignments, not by Autopilot, which enrols and provisions the device and can trigger required app installation only via those separate assignments. It is tempting because Autopilot's enrolment status page shows app progress, but the deployment mechanism is Intune app management.

  • ✓

    Customize the out-of-box experience (OOBE) for users

    Why this is correct

    Windows Autopilot's deployment profiles let you configure the out-of-box experience settings, including hiding EULA and privacy pages, setting the user account type, and pre-configuring region and keyboard. This directly satisfies the requirement to customise OOBE, ensuring devices reach the desktop with minimal user interaction during provisioning.

  • ✗

    Configure BIOS settings remotely

    Why it's wrong here

    BIOS settings are configured through vendor management tools or Intune firmware configuration interfaces, not through Autopilot, which orchestrates the Windows out-of-box experience and enrolment. It is tempting because Autopilot can apply device-targeted profiles during provisioning, but firmware-level configuration sits outside the Autopilot deployment pipeline itself.

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 →

How Courseiva writes practice questions · Editorial policy

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.