Courseiva
Manage applications →mediumMultiple Choice

MD-102 Manage applications Practice Question

Exhibit

{
  "displayName": "Win32 App Deployment",
  "installExperience": "system",
  "deviceRestartBehavior": "suppress",
  "returnCodes": [
    {"returnCode": 0, "type": "success"},
    {"returnCode": 1641, "type": "success"},
    {"returnCode": 3010, "type": "softReboot"}
  ]
}

Refer to the exhibit. An Intune administrator configured a Win32 app with the settings shown. What is the expected behavior when the app installation exits with return code 3010?

⚠ Common exam trap

Many candidates confuse return code 3010 with a failure code, assuming any non-zero exit code means the installation failed, but Intune specifically treats 3010 as a success with a pending reboot, not an error.

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

✓

The device may restart after installation outside of active hours

Return code 3010 is a standard Windows Installer code indicating a reboot is required. In Intune, a Win32 app that exits with 3010 is treated as a successful installation, but the device may be restarted outside of active hours to apply changes. This behavior aligns with the 'Device restart behavior' setting configured in the app's properties, which defers the restart to a maintenance window.

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 device restarts immediately

    Why it's wrong here

    Return code 3010 signals a soft reboot required, so Intune reports the install as a success pending restart rather than restarting the device immediately. It is tempting because 3010 is associated with restarts, and a forced restart would be correct if the app's return code handling were configured to treat 3010 as a hard reboot.

  • ✗

    The installation is marked as failed

    Why it's wrong here

    Return code 3010 signals a successful install requiring a restart, so Intune treats it as success when configured as a soft-reboot code. Marking failure applies to codes outside the configured success range, such as 1603, which indicates a genuine installation error.

  • ✓

    The device may restart after installation outside of active hours

    Why this is correct

    Return code 3010 signals a soft reboot requirement, so Intune flags the app as installed but pending restart. The device then restarts outside configured active hours, honouring the stem's constraint that users must not be interrupted during working time. Hard reboot codes such as 1641 trigger an immediate restart instead.

  • ✗

    The app is not installed

    Why it's wrong here

    3010 is treated as success with a pending soft reboot, so Intune marks the Win32 app as installed; only a non-configured failure code such as 1603 leaves it uninstalled. It is tempting to read any non-zero code as failure, but 3010 sits in the success range alongside 0 and 1641.

About these practice questions

Courseiva writes every MD-102 question from scratch — 556 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.