Courseiva

MD-102 Prepare infrastructure for devices Practice Question

Exhibit

{
  "@odata.type": "#microsoft.graph.windows10EnrollmentCompletionPageConfigurationPolicy",
  "id": "00000000-0000-0000-0000-000000000000",
  "displayName": "ESP for Autopilot",
  "description": "Required apps must install",
  "showInstallationProgress": true,
  "blockDeviceSetupRetryByUser": true,
  "allowDeviceResetOnInstallFailure": false,
  "trackInstallProgressForAutopilotOnly": true,
  "selectedMobileAppIds": [
    "App1",
    "App2"
  ]
}

Refer to the exhibit. You have assigned the above Enrollment Status Page (ESP) policy to a Windows Autopilot deployment. A user reports that the provisioning process hangs on 'Installing apps' and never completes. What is the most likely cause?

⚠ Common exam trap

Many candidates assume the ESP hangs due to a network issue or user error, but Microsoft explicitly designs the ESP to block on required app failures, making this the primary troubleshooting focus for 'Installing apps' hangs.

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

✓

One of the required apps failed to install.

The Enrollment Status Page (ESP) policy tracks the installation of required apps during Autopilot provisioning. If a required app fails to install, the ESP will hang on 'Installing apps' indefinitely because it waits for all required apps to succeed before proceeding. This is the most common cause of a stuck ESP at the app phase.

Answer analysis

Option-by-option breakdown

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

  • ✗

    The ESP policy is configured to track progress for Autopilot only, but the device is not using Autopilot.

    Why it's wrong here

    If ESP tracked Autopilot only and the device were not Autopilot-enrolled, the page would not appear at all, so it could not stall on 'Installing apps'. It is tempting because ESP scope settings genuinely determine whether the page is displayed during provisioning.

  • ✓

    One of the required apps failed to install.

    Why this is correct

    The Enrollment Status Page blocks the desktop until every targeted required app installs successfully. If any required app fails, ESP retries and stalls on 'Installing apps' indefinitely, preventing provisioning completion. Blocking apps, not available apps, cause this hang.

  • ✗

    The user attempted to retry the setup and it was blocked.

    Why it's wrong here

    A blocked retry would surface an explicit retry-denied message, not an indefinite hang on 'Installing apps'. It is tempting because ESP does expose retry controls, and blocking retries is a genuine configuration used to force devices back through full provisioning.

  • ✗

    The device reset on failure is enabled, causing a reset loop.

    Why it's wrong here

    Device reset on failure restarts a failed deployment rather than leaving it hanging on 'Installing apps'; it triggers only after an error, not during a stalled app install. It is tempting because reset-on-failure is a real ESP setting used to recover failed Autopilot deployments automatically.

Go deeper

Related to this question

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.