Courseiva
Manage applicationsmediumMultiple ChoiceObjective-mapped

MD-102 Manage applications Practice Question

Exhibit

{
  "@odata.type": "#microsoft.graph.win32LobApp",
  "installExperience": {
    "runAsAccount": "user"
  },
  "detectionRules": [
    {
      "@odata.type": "#microsoft.graph.win32LobAppRegistryDetection",
      "check32BitOn64System": false,
      "keyPath": "HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\{12345678-1234-1234-1234-123456789012}",
      "valueName": "DisplayName",
      "detectionType": "exists"
    }
  ]
}

Refer to the exhibit. You are reviewing a Win32 app deployment configuration in Microsoft Intune. The detection rule checks for a registry key under HKLM. The app is set to install in user context. A user reports that the app appears as 'Installed' for some users but not others on the same device. What is the most likely cause?

⚠ Common exam trap

The trap here is that candidates often focus on detection rule syntax (e.g., 'exists' vs. 'value') or 32-bit/64-bit registry redirection, but the real issue is the fundamental mismatch between the installation context (user) and the detection registry hive (HKLM), which is a common oversight in multi-user environments.

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 detection rule uses HKLM but the app installs per user, so the key may not exist for all users.

The detection rule is configured to check for a registry key under HKLM (HKEY_LOCAL_MACHINE), but the app is set to install in user context. When a Win32 app is deployed per user, the installation runs in the user's context and writes to HKCU (HKEY_CURRENT_USER) or user-specific locations, not HKLM. Therefore, the HKLM key may exist only for the user who installed the app (or for system-level installations), causing the detection rule to fail for other users on the same device, making the app appear as 'Installed' for some but not others.

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 detection type 'exists' should be 'value' to check the DisplayName.

    Why it's wrong here

    Exists checks key presence, not value.

  • The install experience should be 'system' to write to HKLM.

    Why it's wrong here

    System context may write to HKLM, but detection rule is separate.

  • The detection rule uses HKLM but the app installs per user, so the key may not exist for all users.

    Why this is correct

    User-context install may write to HKCU, not HKLM.

  • The 'check32BitOn64System' flag is set to false, causing detection to fail on 64-bit systems.

    Why it's wrong here

    This flag is for 32-bit apps on 64-bit OS; not relevant here.

Go deeper

Related to this question

About these practice questions

Courseiva writes every MD-102 question from scratch — 942 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.