Courseiva
Manage applications →hardMultiple Choice

MD-102 Manage applications Practice Question

An administrator deploys a Win32 app via Intune with detection rule 'File exists: C:\Program Files\MyApp\app.exe'. The app is reported as installed, but users cannot launch it. The file exists but is corrupted. How should the administrator modify the detection rule to ensure the app is correctly detected and re-installed if corrupted?

⚠ Common exam trap

Watch out — candidates often assume 'File exists' or 'File version comparison' are sufficient for detection, overlooking that these rules do not validate file integrity, which is a common misconception in Intune app deployment scenarios.

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

✓

Use a custom detection script that validates the file hash or signature

A custom detection script can verify the file's integrity by checking its hash or digital signature, ensuring that even if the file exists, it is not corrupted. Intune's built-in detection rules only check for file existence or version, not file integrity. By using a script that validates the hash, the administrator can force a reinstall when the file is corrupted, as the detection will fail.

Answer analysis

Option-by-option breakdown

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

  • ✗

    Remove the detection rule so Intune always re-installs the app

    Why it's wrong here

    Removing the detection rule makes Intune treat the app as never installed, triggering repeated reinstall attempts on every evaluation cycle rather than detecting corruption. It is tempting as a forced-reinstall mechanism, but detection rules exist precisely to report state; script-based detection comparing file hash is the intended method.

  • ✗

    Add a registry detection rule for the app's uninstall key

    Why it's wrong here

    A registry uninstall key is written at install time and persists unchanged when app.exe is corrupted, so Intune still reports the app as installed. It is tempting because registry keys suit apps lacking reliable file artefacts, but here the file exists and the requirement is validating its integrity.

  • ✓

    Use a custom detection script that validates the file hash or signature

    Why this is correct

    A file-exists rule only confirms presence, so a corrupted app.exe still reports as installed and Intune never remediates it. A custom detection script validating the file hash or signature detects corruption, causing Intune to treat the app as non-compliant and reinstall it.

  • ✗

    Change detection rule to 'File version comparison' and set minimum version

    Why it's wrong here

    Version comparison reads the file's version resource, which remains intact and unchanged when the binary is corrupted, so detection still reports success. It is tempting because version rules correctly handle outdated installs, but the stem requires detecting corruption, which needs a hash or script-based check.

About these practice questions

One of 556 original MD-102 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.