Manage applications →hardMultiple ChoiceObjective-mapped

MD-102 Manage applications Practice Question

Exhibit

Refer to the exhibit. 
{
  "displayName": "Microsoft 365 Apps for Windows 10",
  "appVersion": "16.0.14026.20246",
  "installCommand": "setup.exe /configure configuration.xml",
  "uninstallCommand": "setup.exe /configure uninstall.xml",
  "detectionRules": [
    {
      "@odata.type": "#microsoft.graph.win32LobAppRegistryDetection",
      "check32BitOn64System": false,
      "keyPath": "HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Office\\16.0\\Common\\InstallRoot",
      "valueName": "Path",
      "detectionType": "exists"
    }
  ]
}

Refer to the exhibit. You are deploying Microsoft 365 Apps via Intune Win32 app packaging. The detection rule checks for the registry key existence. After installation, Intune reports the app as not detected. What is the most likely reason?

⚠ Common exam trap

It's easy for candidates to assume registry detection is straightforward and overlook the 32-bit vs. 64-bit registry redirection, leading them to incorrectly blame the key path or the detection type instead of the context mismatch.

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 runs in 32-bit context and does not see the 64-bit registry key

Intune Win32 app detection rules run in a 32-bit context by default on 64-bit systems. This means the detection script or rule checks the 32-bit registry view (Wow6432Node) rather than the 64-bit registry view. If the app created the registry key in the 64-bit path (e.g., HKLM\Software\Microsoft\Office), the 32-bit detection will not see it, causing a false 'not detected' state.

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' is not supported for registry detection
Why it's wrong here
'Exists' is a valid detection type.
✗
The registry key path is incorrect for a 64-bit system
Why it's wrong here
The path is correct for 64-bit Office.
✗
The app did not create the registry key during installation
Why it's wrong here
Office creates this key.
✓
The detection runs in 32-bit context and does not see the 64-bit registry key
Why this is correct
32-bit detection redirected to WOW6432Node, but check32BitOn64System is false.

Go deeper

MD-102 Manage applications Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question