Microsoft MD-102 Practice Test 30 - Prepaway
Practice Exams:

Pass Microsoft MD-102 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers!

30 Days Free Updates, Instant Download!

Verified By Experts
Premium Bundle
$29.98
$79.99 $109.97

MD-102 Premium Bundle


  • Premium File 463 Questions & Answers. Last update: Nov 12, 2026
  • Training Course 84 Lectures
  • Study Guide 512 Pages

Microsoft MD-102 Practice Test 30

Question 290

A meeting-room appliance fails its intended configuration because an ordinary Windows laptop configuration template was applied to it. Which TWO shortcuts conflict with the stated management requirements?

  1. Push every desktop security baseline to the meeting appliance without considering its validated support matrix.
  2. Meeting-room devices receive only supported meeting configuration while ordinary laptops remain unaffected.
  3. Inspect enrollment type, device model, Teams Rooms policy support, assignment filters, and management reports.
  4. Choose policies supported for the Teams Rooms device platform and scope them to verified specialty devices.
  5. Assign room-device kiosk settings to all corporate laptops merely because their operating systems are related.

Explanation

Correct Answer

A:

“Push every desktop security baseline to the meeting appliance without considering its validated support matrix” would violate the requirement. The appropriate control instead is to choose policies supported for the Teams Rooms device platform and scope them to verified specialty devices.

E:

“Assign room-device kiosk settings to all corporate laptops merely because their operating systems are related” would violate the requirement.

Incorrect Answers

B:

Meeting-room devices receive only supported meeting configuration while ordinary laptops remain unaffected. This is a bounded acceptance test of the intended outcome, not an unsafe production shortcut.

C:

“Inspect enrollment type, device model, Teams Rooms policy support, assignment filters, and management reports” is the relevant troubleshooting evidence, not a reason to bypass safeguards.

D:

“Choose policies supported for the Teams Rooms device platform and scope them to verified specialty devices” is the controlled implementation, not an unsafe workaround. Confirm that meeting-room devices receive only supported meeting configuration while ordinary laptops remain unaffected.

Question 291

An industrial HoloLens 2 fleet requires controlled updates and remote management but administrators choose an Android enrollment policy. What is the most appropriate supported endpoint management change?

  1. Use supported HoloLens 2 Intune device management settings and assign policies based on its Windows Holographic platform.
  2. Use a reviewed eligible device scope and exclusions before executing the supported bulk restart action.
  3. Register HoloLens 2 as Android Enterprise dedicated hardware and assume its device configuration policy will apply.
  4. Flash an unsupported consumer Windows image onto headset hardware to reuse laptop management profiles.

Explanation

Correct Answer

A:

An industrial HoloLens 2 fleet requires controlled updates and remote management but administrators choose an Android enrollment policy. Use supported HoloLens 2 Intune device management settings and assign policies based on its Windows Holographic platform. Specialty Windows Holographic management differs from Android Enterprise policy targeting despite shared MDM concepts. A test HoloLens reports correct managed device state and applies supported restrictions or updates.

Incorrect Answers

B:

It would not produce the required result: A test HoloLens reports correct managed device state and applies supported restrictions or updates.

C:

“Register HoloLens 2 as Android Enterprise dedicated hardware and assume its device configuration policy will apply” would not meet the requirement. Specialty Windows Holographic management differs from Android Enterprise policy targeting despite shared MDM concepts. Instead, use supported HoloLens 2 Intune device management settings and assign policies based on its Windows Holographic platform.

D:

“Flash an unsupported consumer Windows image onto headset hardware to reuse laptop management profiles” does not implement the control that the facts call for. Specialty Windows Holographic management differs from Android Enterprise policy targeting despite shared MDM concepts. Instead, use supported HoloLens 2 Intune device management settings and assign policies based on its Windows Holographic platform.

Question 292

An industrial HoloLens 2 fleet requires controlled updates and remote management but administrators choose an Android enrollment policy. Which evidence most directly isolates the endpoint issue?

  1. Inspect pre-provisioning status, device-targeted app assignments, reseal step, and final user Enrollment Status Page.
  2. Inspect Windows Holographic device classification, enrollment, policy support, assignments, and compliance telemetry.
  3. Inspect bulk action audience, included groups, excluded devices, maintenance window, and operation results.
  4. Inspect imported ADMX status, assigned setting, policy registry evidence, browser policy page, and client MDM logs.

Explanation

Correct Answer

B:

An industrial HoloLens 2 fleet requires controlled updates and remote management but administrators choose an Android enrollment policy. Inspect Windows Holographic device classification, enrollment, policy support, assignments, and compliance telemetry. Specialty Windows Holographic management differs from Android Enterprise policy targeting despite shared MDM concepts. A test HoloLens reports correct managed device state and applies supported restrictions or updates.

Incorrect Answers

A:

This evidence primarily tests autopilot pre-provisioning for remote worker apps; it would not isolate the actual failure boundary in this scenario. The targeted checks are: Inspect Windows Holographic device classification, enrollment, policy support, assignments, and compliance telemetry.

C:

This evidence primarily tests bulk restart action with critical-device exclusions; it would not isolate the actual failure boundary in this scenario. The targeted checks are: Inspect Windows Holographic device classification, enrollment, policy support, assignments, and compliance telemetry.

D:

This evidence primarily tests admx-backed settings catalog browser preference; it would not isolate the actual failure boundary in this scenario. The targeted checks are: Inspect Windows Holographic device classification, enrollment, policy support, assignments, and compliance telemetry.

Question 293

An industrial HoloLens 2 fleet requires controlled updates and remote management but administrators choose an Android enrollment policy. What measured result confirms the endpoint deployment now works?

  1. A new Cloud PC provisions in the approved region and passes the intended connectivity and user access tests.
  2. Meeting-room devices receive only supported meeting configuration while ordinary laptops remain unaffected.
  3. A test Cloud PC created from the refreshed image includes approved baseline apps and the expected Windows version.
  4. A test HoloLens reports correct managed device state and applies supported restrictions or updates.

Explanation

Correct Answer

D:

Specialty Windows Holographic management differs from Android Enterprise policy targeting despite shared MDM concepts. A test HoloLens reports correct managed device state and applies supported restrictions or updates.

Incorrect Answers

A:

This could validate windows 365 provisioning policy regional placement, but it does not prove the specific requirement has been met. Instead measure: A test HoloLens reports correct managed device state and applies supported restrictions or updates.

B:

“Meeting-room devices receive only supported meeting configuration while ordinary laptops remain unaffected” alone does not establish all the required behavior. A test HoloLens reports correct managed device state and applies supported restrictions or updates.

C:

This could validate windows 365 custom image maintenance, but it does not prove the specific requirement has been met. Instead measure: A test HoloLens reports correct managed device state and applies supported restrictions or updates.

Question 294

An industrial HoloLens 2 fleet requires controlled updates and remote management but administrators choose an Android enrollment policy. Which underlying Intune or Windows behavior is most relevant here?

  1. A sync requests management communication but cannot grant policy assignments absent from the device's audience.
  2. Specialty Windows Holographic management differs from Android Enterprise policy targeting despite shared MDM concepts.
  3. Defender intelligence signatures can be updated independently of destructive operating system reinstallation.
  4. Specialty devices can have unique platform management and support boundaries not shared with general Windows endpoints.

Explanation

Correct Answer

B:

Specialty Windows Holographic management differs from Android Enterprise policy targeting despite shared MDM concepts. Use supported HoloLens 2 Intune device management settings and assign policies based on its Windows Holographic platform. The decisive evidence is that a test HoloLens reports correct managed device state and applies supported restrictions or updates.

Incorrect Answers

A:

This concerns device sync versus policy assignment delay, which is a different mechanism than the one causing the stated symptom. The principle that applies here is: Specialty Windows Holographic management differs from Android Enterprise policy targeting despite shared MDM concepts.

C:

“Defender intelligence signatures can be updated independently of destructive operating system reinstallation” does not fully explain the decisive technical boundary in this case. Specialty Windows Holographic management differs from Android Enterprise policy targeting despite shared MDM concepts.

D:

This concerns teams rooms specialty device policy targeting, which is a different mechanism than the one causing the stated symptom. The principle that applies here is: Specialty Windows Holographic management differs from Android Enterprise policy targeting despite shared MDM concepts.

Question 295

An industrial HoloLens 2 fleet requires controlled updates and remote management but administrators choose an Android enrollment policy. Which TWO unsafe endpoint management actions should be rejected?

  1. Flash an unsupported consumer Windows image onto headset hardware to reuse laptop management profiles.
  2. A test HoloLens reports correct managed device state and applies supported restrictions or updates.
  3. Use supported HoloLens 2 Intune device management settings and assign policies based on its Windows Holographic platform.
  4. Register HoloLens 2 as Android Enterprise dedicated hardware and assume its device configuration policy will apply.
  5. Inspect Windows Holographic device classification, enrollment, policy support, assignments, and compliance telemetry.

Explanation

Correct Answer

A:

“Flash an unsupported consumer Windows image onto headset hardware to reuse laptop management profiles” would violate the requirement. Specialty Windows Holographic management differs from Android Enterprise policy targeting despite shared MDM concepts.

D:

“Register HoloLens 2 as Android Enterprise dedicated hardware and assume its device configuration policy will apply” would violate the requirement. Specialty Windows Holographic management differs from Android Enterprise policy targeting despite shared MDM concepts.

Incorrect Answers

B:

A test HoloLens reports correct managed device state and applies supported restrictions or updates. This is a bounded acceptance test of the intended outcome, not an unsafe production shortcut.

C:

“Use supported HoloLens 2 Intune device management settings and assign policies based on its Windows Holographic platform” is the controlled implementation, not an unsafe workaround. Specialty Windows Holographic management differs from Android Enterprise policy targeting despite shared MDM concepts.

E:

“Inspect Windows Holographic device classification, enrollment, policy support, assignments, and compliance telemetry” is the relevant troubleshooting evidence, not a reason to bypass safeguards. Specialty Windows Holographic management differs from Android Enterprise policy targeting despite shared MDM concepts. Confirm that a test HoloLens reports correct managed device state and applies supported restrictions or updates.

Question 296

Warehouses manage Zebra scanners but standard Android controls cannot set one vendor-specific scanner wedge preference. Which Intune or Entra configuration best solves the endpoint requirement?

  1. Edit unknown system configuration files using a one-time user script and declare the devices centrally managed.
  2. Apply a standard iOS restriction profile and assume Zebra scanners interpret its keys identically.
  3. Correct profile targeting first and then invoke sync to prompt eligible device evaluation.
  4. Use approved Zebra OEMConfig or supported managed configuration with compatible app and firmware support.

Explanation

Correct Answer

D:

Warehouses manage Zebra scanners but standard Android controls cannot set one vendor-specific scanner wedge preference. Use approved Zebra OEMConfig or supported managed configuration with compatible app and firmware support. OEMConfig exposes manufacturer-specific Android device controls through sanctioned interfaces rather than undocumented global policy keys. A pilot scanner reports the required wedge behavior and continues to accept ordinary managed app policies.

Incorrect Answers

A:

“Edit unknown system configuration files using a one-time user script and declare the devices centrally managed” does not implement the control that the facts call for. OEMConfig exposes manufacturer-specific Android device controls through sanctioned interfaces rather than undocumented global policy keys. Instead, use approved Zebra OEMConfig or supported managed configuration with compatible app and firmware support.

B:

“Apply a standard iOS restriction profile and assume Zebra scanners interpret its keys identically” would not meet the requirement. OEMConfig exposes manufacturer-specific Android device controls through sanctioned interfaces rather than undocumented global policy keys. Instead, use approved Zebra OEMConfig or supported managed configuration with compatible app and firmware support.

C:

It would not produce the required result: A pilot scanner reports the required wedge behavior and continues to accept ordinary managed app policies.

Question 297

Warehouses manage Zebra scanners but standard Android controls cannot set one vendor-specific scanner wedge preference. What should the administrator inspect to diagnose this behavior?

  1. Inspect Zebra management app, OEMConfig schema, device firmware, app deployment, and policy status.
  2. Inspect backup policy, user Entra identity, eligible settings, restore event logs, and app reinstallation status.
  3. Inspect enrollment model, Managed Google Play approval, assigned kiosk profile, device check-in, and restrictions.
  4. Inspect device reliability reports, anomalous battery trends, firmware versions, cohort filters, and remediation results.

Explanation

Correct Answer

A:

Warehouses manage Zebra scanners but standard Android controls cannot set one vendor-specific scanner wedge preference. Inspect Zebra management app, OEMConfig schema, device firmware, app deployment, and policy status. OEMConfig exposes manufacturer-specific Android device controls through sanctioned interfaces rather than undocumented global policy keys. A pilot scanner reports the required wedge behavior and continues to accept ordinary managed app policies.

Incorrect Answers

B:

This evidence primarily tests windows backup user-state restoration; it would not isolate the actual failure boundary in this scenario. The targeted checks are: Inspect Zebra management app, OEMConfig schema, device firmware, app deployment, and policy status.

C:

This evidence primarily tests android device configuration for dedicated mode; it would not isolate the actual failure boundary in this scenario. The targeted checks are: Inspect Zebra management app, OEMConfig schema, device firmware, app deployment, and policy status.

D:

This evidence primarily tests intune advanced analytics abnormal battery drain; it would not isolate the actual failure boundary in this scenario. The targeted checks are: Inspect Zebra management app, OEMConfig schema, device firmware, app deployment, and policy status.

Question 298

Warehouses manage Zebra scanners but standard Android controls cannot set one vendor-specific scanner wedge preference. Which acceptance criterion validates the chosen endpoint management solution?

  1. A pre-provisioned laptop reaches employee-ready state quickly while user-specific policy still completes after sign-in.
  2. An approved pilot support event produces attributable helper identity and permitted session metadata without unnecessary personal disclosure.
  3. A pilot device reports the intended setting successfully and no longer shows conflicting setting evaluations.
  4. A pilot scanner reports the required wedge behavior and continues to accept ordinary managed app policies.

Explanation

Correct Answer

D:

OEMConfig exposes manufacturer-specific Android device controls through sanctioned interfaces rather than undocumented global policy keys. A pilot scanner reports the required wedge behavior and continues to accept ordinary managed app policies.

Incorrect Answers

A:

“A pre-provisioned laptop reaches employee-ready state quickly while user-specific policy still completes after sign-in” alone does not establish all the required behavior. A pilot scanner reports the required wedge behavior and continues to accept ordinary managed app policies.

B:

“An approved pilot support event produces attributable helper identity and permitted session metadata without unnecessary personal disclosure” alone does not establish all the required behavior. A pilot scanner reports the required wedge behavior and continues to accept ordinary managed app policies. OEMConfig exposes manufacturer-specific Android device controls through sanctioned interfaces rather than undocumented global policy keys.

C:

Instead measure: A pilot scanner reports the required wedge behavior and continues to accept ordinary managed app policies.

Question 299

Warehouses manage Zebra scanners but standard Android controls cannot set one vendor-specific scanner wedge preference. Which Microsoft endpoint management principle explains the decision?

  1. Dedicated Android corporate mode and personally owned work profiles expose different device-level policy capabilities.
  2. Defender intelligence signatures can be updated independently of destructive operating system reinstallation.
  3. Windows 365 image selection affects initial Cloud PC state; image changes do not necessarily patch already provisioned PCs.
  4. OEMConfig exposes manufacturer-specific Android device controls through sanctioned interfaces rather than undocumented global policy keys.

Explanation

Correct Answer

D:

OEMConfig exposes manufacturer-specific Android device controls through sanctioned interfaces rather than undocumented global policy keys. Use approved Zebra OEMConfig or supported managed configuration with compatible app and firmware support. The decisive evidence is that a pilot scanner reports the required wedge behavior and continues to accept ordinary managed app policies.

Incorrect Answers

A:

This concerns android device configuration for dedicated mode, which is a different mechanism than the one causing the stated symptom. The principle that applies here is: OEMConfig exposes manufacturer-specific Android device controls through sanctioned interfaces rather than undocumented global policy keys.

B:

“Defender intelligence signatures can be updated independently of destructive operating system reinstallation” does not fully explain the decisive technical boundary in this case. OEMConfig exposes manufacturer-specific Android device controls through sanctioned interfaces rather than undocumented global policy keys.

C:

This concerns windows 365 custom image maintenance, which is a different mechanism than the one causing the stated symptom. The principle that applies here is: OEMConfig exposes manufacturer-specific Android device controls through sanctioned interfaces rather than undocumented global policy keys.

Question 300

Warehouses manage Zebra scanners but standard Android controls cannot set one vendor-specific scanner wedge preference. Select TWO choices that would create avoidable endpoint security or reliability risk.

  1. A pilot scanner reports the required wedge behavior and continues to accept ordinary managed app policies.
  2. Use approved Zebra OEMConfig or supported managed configuration with compatible app and firmware support.
  3. Apply a standard iOS restriction profile and assume Zebra scanners interpret its keys identically.
  4. Inspect Zebra management app, OEMConfig schema, device firmware, app deployment, and policy status.
  5. Edit unknown system configuration files using a one-time user script and declare the devices centrally managed.

Explanation

Correct Answer

C:

“Apply a standard iOS restriction profile and assume Zebra scanners interpret its keys identically” would violate the requirement. OEMConfig exposes manufacturer-specific Android device controls through sanctioned interfaces rather than undocumented global policy keys.

E:

“Edit unknown system configuration files using a one-time user script and declare the devices centrally managed” would violate the requirement. OEMConfig exposes manufacturer-specific Android device controls through sanctioned interfaces rather than undocumented global policy keys.

Incorrect Answers

A:

A pilot scanner reports the required wedge behavior and continues to accept ordinary managed app policies. This is a bounded acceptance test of the intended outcome, not an unsafe production shortcut.

B:

“Use approved Zebra OEMConfig or supported managed configuration with compatible app and firmware support” is the controlled implementation, not an unsafe workaround. OEMConfig exposes manufacturer-specific Android device controls through sanctioned interfaces rather than undocumented global policy keys. Confirm that a pilot scanner reports the required wedge behavior and continues to accept ordinary managed app policies.

D:

“Inspect Zebra management app, OEMConfig schema, device firmware, app deployment, and policy status” is the relevant troubleshooting evidence, not a reason to bypass safeguards. OEMConfig exposes manufacturer-specific Android device controls through sanctioned interfaces rather than undocumented global policy keys. Confirm that a pilot scanner reports the required wedge behavior and continues to accept ordinary managed app policies.

Endpoint Administrator (MD-102) Practice Tests