Manage and maintain devices →hardMultiple ChoiceObjective-mapped

MD-102 Manage and maintain devices Practice Question

Exhibit

{
  "@odata.type": "#microsoft.graph.windows10CustomConfiguration",
  "id": "00000000-0000-0000-0000-000000000000",
  "displayName": "Custom OMA-URI Policy",
  "omaSettings": [
    {
      "@odata.type": "#microsoft.graph.omaSettingString",
      "displayName": "Disable Telemetry",
      "omaUri": "./Vendor/MSFT/Policy/Config/System/AllowTelemetry",
      "value": "0"
    },
    {
      "@odata.type": "#microsoft.graph.omaSettingInteger",
      "displayName": "Max Inactivity Timeout",
      "omaUri": "./Vendor/MSFT/Policy/Config/DeviceLock/DeviceLockMaxInactivityTimeAllow",
      "value": "300"
    }
  ]
}

Refer to the exhibit. You create a custom configuration profile in Intune for Windows 10 devices. The profile is assigned to a test device, but the telemetry setting is not applied. The device is managed and compliant. What is the most likely reason?

⚠ Common exam trap

It's easy for candidates to assume any OMA-URI value will be accepted regardless of data type, or they overlook the version requirement, leading them to incorrectly blame the OMA-URI path or compliance status instead of the value format or OS version.

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 AllowTelemetry policy value must be an integer, not a string, or the device needs a Windows 10 version that supports this setting.

The AllowTelemetry setting in a custom OMA-URI profile requires the value to be an integer (0–3) and the device must be running Windows 10 version 1703 or later. If the value is entered as a string (e.g., "2" instead of 2), Intune will not apply the policy, and the device will silently ignore the configuration. Additionally, older Windows 10 builds do not support this OMA-URI path and will fail to process it.

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 is not compliant with the baseline policy.
Why it's wrong here
The stem says the device is compliant.
✗
The OMA-URI path for AllowTelemetry is incorrect.
Why it's wrong here
The path ./Vendor/MSFT/Policy/Config/System/AllowTelemetry is correct for Windows 10.
✓
The AllowTelemetry policy value must be an integer, not a string, or the device needs a Windows 10 version that supports this setting.
Why this is correct
AllowTelemetry expects an integer (0-3); OMA-URI string type may cause failure. Also, some settings require specific builds.
✗
The custom profile conflicts with a built-in policy that sets telemetry to full.
Why it's wrong here
Custom profiles apply after built-in policies, but the exhibit shows a custom profile that should overwrite.

Go deeper

MD-102 Manage and maintain devices Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question