Microsoft MD-102 Windows Configuration Profiles ADMX And Group Policy Analytics Practice Test

 

Skills 2.2 • 25 original questions

This Microsoft MD-102 Endpoint Administrator practice test focuses on windows configuration profiles admx and group policy analytics through original scenario-based questions aligned to the skills measured as of July 24, 2026. Use the full ExamSnap MD-102 collection for broader practice across all current skill areas. For broader exam preparation, review the Microsoft MD-102 Exam Dumps page.

Instructions: Select the best answer for each question. Review the explanation after answering; each distractor includes a reason it is not the best choice for that scenario.

Question 1

During a operations review at Alpine Ski House, the Intune administrator must move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings. Which action most directly satisfies the requirement? The affected devices are in the kiosk cohort, rollout wave 1.

1. Use the supported Intune profile type for specialty devices such as Teams Rooms, HoloLens 2, or Zebra endpoints
2. Create and assign a macOS device configuration profile in Intune
3. Create and assign an Android device configuration profile in Intune
4. Create and assign an iOS/iPadOS device configuration profile in Intune
5. Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Correct answer: E

Why: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Option review:

A: Specialty devices require platform-appropriate management profiles rather than assuming standard Windows desktop settings apply unchanged. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

B: macOS configuration profiles deliver supported settings and restrictions to managed Mac computers. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

C: Android configuration profiles apply platform-specific settings such as device restrictions, connectivity, and managed device behavior. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

D: iOS/iPadOS configuration profiles deliver Apple mobile settings such as restrictions, connectivity, certificates, and device features. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

E: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Learning point: Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Question 2

Wide World Importers is revising endpoint operations for a BYOD program. Administrators need to move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings. Which implementation should the Microsoft 365 administrator select for the new-hire cohort, rollout wave 2?

1. Create and assign a macOS device configuration profile in Intune
2. Use the supported Intune profile type for specialty devices such as Teams Rooms, HoloLens 2, or Zebra endpoints
3. Create and assign an Android device configuration profile in Intune
4. Create and assign an iOS/iPadOS device configuration profile in Intune
5. Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Correct answer: E

Why: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Option review:

A: macOS configuration profiles deliver supported settings and restrictions to managed Mac computers. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

B: Specialty devices require platform-appropriate management profiles rather than assuming standard Windows desktop settings apply unchanged. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

C: Android configuration profiles apply platform-specific settings such as device restrictions, connectivity, and managed device behavior. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

D: iOS/iPadOS configuration profiles deliver Apple mobile settings such as restrictions, connectivity, certificates, and device features. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

E: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Learning point: Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Question 3

A ticket escalated to the endpoint administrator at Northwind Traders states one non-negotiable goal: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings. Which choice is the strongest fit for the contractor cohort, rollout wave 3?

1. Create and assign a macOS device configuration profile in Intune
2. Use the supported Intune profile type for specialty devices such as Teams Rooms, HoloLens 2, or Zebra endpoints
3. Use assignment filters or enrollment time grouping to target profiles more precisely at assignment time
4. Create and assign an Android device configuration profile in Intune
5. Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Correct answer: E

Why: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Option review:

A: macOS configuration profiles deliver supported settings and restrictions to managed Mac computers. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

B: Specialty devices require platform-appropriate management profiles rather than assuming standard Windows desktop settings apply unchanged. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

C: Assignment filters and enrollment-time grouping refine policy targeting based on device properties or enrollment context without maintaining many static groups. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

D: Android configuration profiles apply platform-specific settings such as device restrictions, connectivity, and managed device behavior. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

E: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Learning point: Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Question 4

For the lab-device cohort, rollout wave 4 at Tailspin Toys, a application modernization can proceed only if the team can move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings. What should the endpoint administrator configure?

1. Create and assign a macOS device configuration profile in Intune
2. Create and assign an iOS/iPadOS device configuration profile in Intune
3. Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy
4. Use assignment filters or enrollment time grouping to target profiles more precisely at assignment time
5. Create and assign an Android device configuration profile in Intune

Correct answer: C

Why: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Option review:

A: macOS configuration profiles deliver supported settings and restrictions to managed Mac computers. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

B: iOS/iPadOS configuration profiles deliver Apple mobile settings such as restrictions, connectivity, certificates, and device features. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

C: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

D: Assignment filters and enrollment-time grouping refine policy targeting based on device properties or enrollment context without maintaining many static groups. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

E: Android configuration profiles apply platform-specific settings such as device restrictions, connectivity, and managed device behavior. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Learning point: Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Question 5

The endpoint architecture review at Alpine Ski House focuses on this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings. Which Microsoft management action is most appropriate for the pilot ring, rollout wave 5?

1. Use assignment filters or enrollment time grouping to target profiles more precisely at assignment time
2. Create and assign a macOS device configuration profile in Intune
3. Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy
4. Create and assign an Android device configuration profile in Intune
5. Use the supported Intune profile type for specialty devices such as Teams Rooms, HoloLens 2, or Zebra endpoints

Correct answer: C

Why: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Option review:

A: Assignment filters and enrollment-time grouping refine policy targeting based on device properties or enrollment context without maintaining many static groups. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

B: macOS configuration profiles deliver supported settings and restrictions to managed Mac computers. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

C: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

D: Android configuration profiles apply platform-specific settings such as device restrictions, connectivity, and managed device behavior. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

E: Specialty devices require platform-appropriate management profiles rather than assuming standard Windows desktop settings apply unchanged. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Learning point: Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Question 6

A change advisory board at Wide World Importers asks how to move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings during a device refresh. Which proposed action should the security administrator approve for the production ring, rollout wave 6?

1. Use the supported Intune profile type for specialty devices such as Teams Rooms, HoloLens 2, or Zebra endpoints
2. Create and assign an iOS/iPadOS device configuration profile in Intune
3. Create and assign a macOS device configuration profile in Intune
4. Use assignment filters or enrollment time grouping to target profiles more precisely at assignment time
5. Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Correct answer: E

Why: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Option review:

A: Specialty devices require platform-appropriate management profiles rather than assuming standard Windows desktop settings apply unchanged. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

B: iOS/iPadOS configuration profiles deliver Apple mobile settings such as restrictions, connectivity, certificates, and device features. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

C: macOS configuration profiles deliver supported settings and restrictions to managed Mac computers. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

D: Assignment filters and enrollment-time grouping refine policy targeting based on device properties or enrollment context without maintaining many static groups. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

E: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Learning point: Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Question 7

Northwind Traders has already ruled out manual per-device administration. For the executive-device cohort, rollout wave 7, the remaining requirement is to move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings. Which choice best addresses it?

1. Create and assign an iOS/iPadOS device configuration profile in Intune
2. Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy
3. Use the supported Intune profile type for specialty devices such as Teams Rooms, HoloLens 2, or Zebra endpoints
4. Create and assign a macOS device configuration profile in Intune
5. Create and assign an Android device configuration profile in Intune

Correct answer: B

Why: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Option review:

A: iOS/iPadOS configuration profiles deliver Apple mobile settings such as restrictions, connectivity, certificates, and device features. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

B: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

C: Specialty devices require platform-appropriate management profiles rather than assuming standard Windows desktop settings apply unchanged. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

D: macOS configuration profiles deliver supported settings and restrictions to managed Mac computers. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

E: Android configuration profiles apply platform-specific settings such as device restrictions, connectivity, and managed device behavior. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Learning point: Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Question 8

During post-pilot review at Tailspin Toys, the Microsoft 365 administrator identifies a gap: the organization still needs to move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings. Which action should be added before the remote-user cohort, rollout wave 8 moves to production?

1. Create and assign an iOS/iPadOS device configuration profile in Intune
2. Use the supported Intune profile type for specialty devices such as Teams Rooms, HoloLens 2, or Zebra endpoints
3. Use assignment filters or enrollment time grouping to target profiles more precisely at assignment time
4. Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy
5. Create and assign an Android device configuration profile in Intune

Correct answer: D

Why: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Option review:

A: iOS/iPadOS configuration profiles deliver Apple mobile settings such as restrictions, connectivity, certificates, and device features. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

B: Specialty devices require platform-appropriate management profiles rather than assuming standard Windows desktop settings apply unchanged. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

C: Assignment filters and enrollment-time grouping refine policy targeting based on device properties or enrollment context without maintaining many static groups. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

D: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

E: Android configuration profiles apply platform-specific settings such as device restrictions, connectivity, and managed device behavior. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Learning point: Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Question 9

The endpoint administrator at Alpine Ski House is comparing several cloud-management options for a remote-work deployment. Which one directly enables the team to move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings for the shared-device cohort, rollout wave 9?

1. Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy
2. Use the supported Intune profile type for specialty devices such as Teams Rooms, HoloLens 2, or Zebra endpoints
3. Create and assign an iOS/iPadOS device configuration profile in Intune
4. Create and assign a macOS device configuration profile in Intune
5. Use assignment filters or enrollment time grouping to target profiles more precisely at assignment time

Correct answer: A

Why: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Option review:

A: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

B: Specialty devices require platform-appropriate management profiles rather than assuming standard Windows desktop settings apply unchanged. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

C: iOS/iPadOS configuration profiles deliver Apple mobile settings such as restrictions, connectivity, certificates, and device features. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

D: macOS configuration profiles deliver supported settings and restrictions to managed Mac computers. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

E: Assignment filters and enrollment-time grouping refine policy targeting based on device properties or enrollment context without maintaining many static groups. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Learning point: Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Question 10

A security and operations workshop at Wide World Importers defines the desired outcome as follows: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings. Which implementation should be chosen for the field-device cohort, rollout wave 10?

1. Use the supported Intune profile type for specialty devices such as Teams Rooms, HoloLens 2, or Zebra endpoints
2. Create and assign an iOS/iPadOS device configuration profile in Intune
3. Create and assign a macOS device configuration profile in Intune
4. Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy
5. Create and assign an Android device configuration profile in Intune

Correct answer: D

Why: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Option review:

A: Specialty devices require platform-appropriate management profiles rather than assuming standard Windows desktop settings apply unchanged. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

B: iOS/iPadOS configuration profiles deliver Apple mobile settings such as restrictions, connectivity, certificates, and device features. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

C: macOS configuration profiles deliver supported settings and restrictions to managed Mac computers. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

D: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

E: Android configuration profiles apply platform-specific settings such as device restrictions, connectivity, and managed device behavior. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Learning point: Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Question 11

Which action best matches this technical purpose for the developer cohort, rollout wave 11: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs.

1. Use assignment filters or enrollment time grouping to target profiles more precisely at assignment time
2. Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy
3. Use the supported Intune profile type for specialty devices such as Teams Rooms, HoloLens 2, or Zebra endpoints
4. Create and assign an Android device configuration profile in Intune
5. Create and assign an iOS/iPadOS device configuration profile in Intune

Correct answer: B

Why: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs..

Option review:

A: Assignment filters and enrollment-time grouping refine policy targeting based on device properties or enrollment context without maintaining many static groups. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs..

B: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs..

C: Specialty devices require platform-appropriate management profiles rather than assuming standard Windows desktop settings apply unchanged. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs..

D: Android configuration profiles apply platform-specific settings such as device restrictions, connectivity, and managed device behavior. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs..

E: iOS/iPadOS configuration profiles deliver Apple mobile settings such as restrictions, connectivity, certificates, and device features. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs..

Learning point: Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Question 12

An administrator at Tailspin Toys describes the needed capability this way: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. Which option should be associated with that requirement for the frontline-user cohort, rollout wave 12?

1. Create and assign an iOS/iPadOS device configuration profile in Intune
2. Create and assign a macOS device configuration profile in Intune
3. Use assignment filters or enrollment time grouping to target profiles more precisely at assignment time
4. Use the supported Intune profile type for specialty devices such as Teams Rooms, HoloLens 2, or Zebra endpoints
5. Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Correct answer: E

Why: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs..

Option review:

A: iOS/iPadOS configuration profiles deliver Apple mobile settings such as restrictions, connectivity, certificates, and device features. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs..

B: macOS configuration profiles deliver supported settings and restrictions to managed Mac computers. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs..

C: Assignment filters and enrollment-time grouping refine policy targeting based on device properties or enrollment context without maintaining many static groups. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs..

D: Specialty devices require platform-appropriate management profiles rather than assuming standard Windows desktop settings apply unchanged. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs..

E: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs..

Learning point: Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Question 13

During a design validation for the kiosk cohort, rollout wave 13, Alpine Ski House documents the following behavior: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. Which endpoint-management feature or action is being described?

1. Create and assign a macOS device configuration profile in Intune
2. Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy
3. Create and assign an iOS/iPadOS device configuration profile in Intune
4. Use the supported Intune profile type for specialty devices such as Teams Rooms, HoloLens 2, or Zebra endpoints
5. Create and assign an Android device configuration profile in Intune

Correct answer: B

Why: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs..

Option review:

A: macOS configuration profiles deliver supported settings and restrictions to managed Mac computers. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs..

B: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs..

C: iOS/iPadOS configuration profiles deliver Apple mobile settings such as restrictions, connectivity, certificates, and device features. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs..

D: Specialty devices require platform-appropriate management profiles rather than assuming standard Windows desktop settings apply unchanged. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs..

E: Android configuration profiles apply platform-specific settings such as device restrictions, connectivity, and managed device behavior. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs..

Learning point: Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Question 14

The Microsoft 365 administrator must identify the Microsoft endpoint-management capability that provides this function for the new-hire cohort, rollout wave 14: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. Which choice is correct?

1. Use the supported Intune profile type for specialty devices such as Teams Rooms, HoloLens 2, or Zebra endpoints
2. Create and assign an iOS/iPadOS device configuration profile in Intune
3. Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy
4. Use assignment filters or enrollment time grouping to target profiles more precisely at assignment time
5. Create and assign a macOS device configuration profile in Intune

Correct answer: C

Why: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs..

Option review:

A: Specialty devices require platform-appropriate management profiles rather than assuming standard Windows desktop settings apply unchanged. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs..

B: iOS/iPadOS configuration profiles deliver Apple mobile settings such as restrictions, connectivity, certificates, and device features. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs..

C: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs..

D: Assignment filters and enrollment-time grouping refine policy targeting based on device properties or enrollment context without maintaining many static groups. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs..

E: macOS configuration profiles deliver supported settings and restrictions to managed Mac computers. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs..

Learning point: Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Question 15

A runbook for the contractor cohort, rollout wave 15 contains this description: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. Which implementation belongs in that runbook?

1. Create and assign a macOS device configuration profile in Intune
2. Create and assign an Android device configuration profile in Intune
3. Create and assign an iOS/iPadOS device configuration profile in Intune
4. Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy
5. Use assignment filters or enrollment time grouping to target profiles more precisely at assignment time

Correct answer: D

Why: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs..

Option review:

A: macOS configuration profiles deliver supported settings and restrictions to managed Mac computers. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs..

B: Android configuration profiles apply platform-specific settings such as device restrictions, connectivity, and managed device behavior. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs..

C: iOS/iPadOS configuration profiles deliver Apple mobile settings such as restrictions, connectivity, certificates, and device features. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs..

D: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs..

E: Assignment filters and enrollment-time grouping refine policy targeting based on device properties or enrollment context without maintaining many static groups. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs..

Learning point: Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Question 16

Tailspin Toys is troubleshooting a device refresh. Evidence shows that the decisive requirement is to move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings. Which action should the service desk lead investigate first for the lab-device cohort, rollout wave 16?

1. Create and assign a macOS device configuration profile in Intune
2. Create and assign an Android device configuration profile in Intune
3. Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy
4. Use the supported Intune profile type for specialty devices such as Teams Rooms, HoloLens 2, or Zebra endpoints
5. Create and assign an iOS/iPadOS device configuration profile in Intune

Correct answer: C

Why: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Option review:

A: macOS configuration profiles deliver supported settings and restrictions to managed Mac computers. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

B: Android configuration profiles apply platform-specific settings such as device restrictions, connectivity, and managed device behavior. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

C: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

D: Specialty devices require platform-appropriate management profiles rather than assuming standard Windows desktop settings apply unchanged. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

E: iOS/iPadOS configuration profiles deliver Apple mobile settings such as restrictions, connectivity, certificates, and device features. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Learning point: Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Question 17

After eliminating network and licensing causes, the desktop engineer at Alpine Ski House determines that success depends on the ability to move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings. Which endpoint-management action should be checked next for the pilot ring, rollout wave 17?

1. Create and assign a macOS device configuration profile in Intune
2. Use assignment filters or enrollment time grouping to target profiles more precisely at assignment time
3. Use the supported Intune profile type for specialty devices such as Teams Rooms, HoloLens 2, or Zebra endpoints
4. Create and assign an Android device configuration profile in Intune
5. Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Correct answer: E

Why: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Option review:

A: macOS configuration profiles deliver supported settings and restrictions to managed Mac computers. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

B: Assignment filters and enrollment-time grouping refine policy targeting based on device properties or enrollment context without maintaining many static groups. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

C: Specialty devices require platform-appropriate management profiles rather than assuming standard Windows desktop settings apply unchanged. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

D: Android configuration profiles apply platform-specific settings such as device restrictions, connectivity, and managed device behavior. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

E: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Learning point: Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Question 18

A service-desk escalation during a compliance initiative has been narrowed to one management requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings. Which configuration is the most relevant starting point for the production ring, rollout wave 18?

1. Create and assign a macOS device configuration profile in Intune
2. Use assignment filters or enrollment time grouping to target profiles more precisely at assignment time
3. Use the supported Intune profile type for specialty devices such as Teams Rooms, HoloLens 2, or Zebra endpoints
4. Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy
5. Create and assign an Android device configuration profile in Intune

Correct answer: D

Why: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Option review:

A: macOS configuration profiles deliver supported settings and restrictions to managed Mac computers. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

B: Assignment filters and enrollment-time grouping refine policy targeting based on device properties or enrollment context without maintaining many static groups. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

C: Specialty devices require platform-appropriate management profiles rather than assuming standard Windows desktop settings apply unchanged. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

D: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

E: Android configuration profiles apply platform-specific settings such as device restrictions, connectivity, and managed device behavior. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Learning point: Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Question 19

The failure pattern at Northwind Traders affects the executive-device cohort, rollout wave 19. Before making unrelated policy changes, the Intune administrator needs a solution that will move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings. Which action is most directly relevant?

1. Create and assign an Android device configuration profile in Intune
2. Use assignment filters or enrollment time grouping to target profiles more precisely at assignment time
3. Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy
4. Use the supported Intune profile type for specialty devices such as Teams Rooms, HoloLens 2, or Zebra endpoints
5. Create and assign an iOS/iPadOS device configuration profile in Intune

Correct answer: C

Why: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Option review:

A: Android configuration profiles apply platform-specific settings such as device restrictions, connectivity, and managed device behavior. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

B: Assignment filters and enrollment-time grouping refine policy targeting based on device properties or enrollment context without maintaining many static groups. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

C: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

D: Specialty devices require platform-appropriate management profiles rather than assuming standard Windows desktop settings apply unchanged. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

E: iOS/iPadOS configuration profiles deliver Apple mobile settings such as restrictions, connectivity, certificates, and device features. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Learning point: Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Question 20

While investigating a tenant consolidation, Tailspin Toys confirms the environment must move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings. Which Microsoft endpoint-management capability should be validated for the remote-user cohort, rollout wave 20?

1. Use assignment filters or enrollment time grouping to target profiles more precisely at assignment time
2. Create and assign a macOS device configuration profile in Intune
3. Create and assign an iOS/iPadOS device configuration profile in Intune
4. Create and assign an Android device configuration profile in Intune
5. Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Correct answer: E

Why: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Option review:

A: Assignment filters and enrollment-time grouping refine policy targeting based on device properties or enrollment context without maintaining many static groups. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

B: macOS configuration profiles deliver supported settings and restrictions to managed Mac computers. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

C: iOS/iPadOS configuration profiles deliver Apple mobile settings such as restrictions, connectivity, certificates, and device features. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

D: Android configuration profiles apply platform-specific settings such as device restrictions, connectivity, and managed device behavior. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

E: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Learning point: Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Question 21

Two teams at Alpine Ski House propose different approaches for the shared-device cohort, rollout wave 21. The selection criterion is simple: the chosen approach must move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings. Which option should win the technical comparison?

1. Use assignment filters or enrollment time grouping to target profiles more precisely at assignment time
2. Create and assign an iOS/iPadOS device configuration profile in Intune
3. Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy
4. Create and assign a macOS device configuration profile in Intune
5. Create and assign an Android device configuration profile in Intune

Correct answer: C

Why: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Option review:

A: Assignment filters and enrollment-time grouping refine policy targeting based on device properties or enrollment context without maintaining many static groups. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

B: iOS/iPadOS configuration profiles deliver Apple mobile settings such as restrictions, connectivity, certificates, and device features. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

C: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

D: macOS configuration profiles deliver supported settings and restrictions to managed Mac computers. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

E: Android configuration profiles apply platform-specific settings such as device restrictions, connectivity, and managed device behavior. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Learning point: Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Question 22

For the field-device cohort, rollout wave 22, Wide World Importers wants the least indirect solution to this goal: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings. Which action aligns most closely with that requirement?

1. Create and assign a macOS device configuration profile in Intune
2. Use assignment filters or enrollment time grouping to target profiles more precisely at assignment time
3. Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy
4. Create and assign an Android device configuration profile in Intune
5. Create and assign an iOS/iPadOS device configuration profile in Intune

Correct answer: C

Why: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Option review:

A: macOS configuration profiles deliver supported settings and restrictions to managed Mac computers. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

B: Assignment filters and enrollment-time grouping refine policy targeting based on device properties or enrollment context without maintaining many static groups. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

C: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

D: Android configuration profiles apply platform-specific settings such as device restrictions, connectivity, and managed device behavior. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

E: iOS/iPadOS configuration profiles deliver Apple mobile settings such as restrictions, connectivity, certificates, and device features. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Learning point: Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Question 23

A modernization plan at Northwind Traders includes a security hardening project. The desktop engineer is asked to choose the control that specifically helps the organization move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings. Which choice fits best for the developer cohort, rollout wave 23?

1. Use assignment filters or enrollment time grouping to target profiles more precisely at assignment time
2. Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy
3. Create and assign a macOS device configuration profile in Intune
4. Create and assign an Android device configuration profile in Intune
5. Create and assign an iOS/iPadOS device configuration profile in Intune

Correct answer: B

Why: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Option review:

A: Assignment filters and enrollment-time grouping refine policy targeting based on device properties or enrollment context without maintaining many static groups. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

B: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

C: macOS configuration profiles deliver supported settings and restrictions to managed Mac computers. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

D: Android configuration profiles apply platform-specific settings such as device restrictions, connectivity, and managed device behavior. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

E: iOS/iPadOS configuration profiles deliver Apple mobile settings such as restrictions, connectivity, certificates, and device features. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Learning point: Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Question 24

The frontline-user cohort, rollout wave 24 is moving into a controlled rollout at Tailspin Toys. Which action should be included when the stated management objective is to move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings?

1. Create and assign an Android device configuration profile in Intune
2. Use assignment filters or enrollment time grouping to target profiles more precisely at assignment time
3. Create and assign an iOS/iPadOS device configuration profile in Intune
4. Create and assign a macOS device configuration profile in Intune
5. Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Correct answer: E

Why: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Option review:

A: Android configuration profiles apply platform-specific settings such as device restrictions, connectivity, and managed device behavior. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

B: Assignment filters and enrollment-time grouping refine policy targeting based on device properties or enrollment context without maintaining many static groups. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

C: iOS/iPadOS configuration profiles deliver Apple mobile settings such as restrictions, connectivity, certificates, and device features. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

D: macOS configuration profiles deliver supported settings and restrictions to managed Mac computers. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

E: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Learning point: Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Question 25

Alpine Ski House is replacing an ad hoc process during a Windows 11 rollout. The replacement must reliably move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings. Which endpoint-management approach should the Intune administrator implement for the kiosk cohort, rollout wave 25?

1. Use the supported Intune profile type for specialty devices such as Teams Rooms, HoloLens 2, or Zebra endpoints
2. Create and assign an Android device configuration profile in Intune
3. Use assignment filters or enrollment time grouping to target profiles more precisely at assignment time
4. Create and assign an iOS/iPadOS device configuration profile in Intune
5. Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy

Correct answer: E

Why: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Option review:

A: Specialty devices require platform-appropriate management profiles rather than assuming standard Windows desktop settings apply unchanged. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

B: Android configuration profiles apply platform-specific settings such as device restrictions, connectivity, and managed device behavior. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

C: Assignment filters and enrollment-time grouping refine policy targeting based on device properties or enrollment context without maintaining many static groups. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

D: iOS/iPadOS configuration profiles deliver Apple mobile settings such as restrictions, connectivity, certificates, and device features. It can be valid in another endpoint-management scenario, but it does not most directly address this requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

E: Windows configuration profiles deliver modern device settings; imported ADMX expands policy coverage and Group Policy analytics helps assess migration from on-premises GPOs. This directly addresses the requirement: move Windows configuration from legacy Group Policy toward Intune while supporting required ADMX-backed settings.

Learning point: Create Windows configuration profiles in Intune, using Settings Catalog, imported ADMX where required, and Group Policy analytics to translate legacy policy