MS-102 Deploy and manage a Microsoft 365 tenant Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Create a script that runs daily to sync department values and assign licenses using PowerShell.

  Why it's wrong here

  While scripted automation appears to solve the problem, a custom PowerShell job is operationally fragile: it requires secure stored credentials, scheduled execution, and continuous maintenance to handle error conditions like throttling or license exhaustion. Any delay or script failure leaves users without correct assignments, and it bypasses native Entra ID lifecycle features. Group-based licensing removes this dependency by making Entra ID itself evaluate membership and apply licenses.

• ✓

  Configure group-based licensing using Microsoft Entra dynamic groups with rules based on the department attribute.

  Why this is correct

  Dynamic groups in Microsoft Entra ID evaluate membership using a rule on the department attribute, so users are automatically added or removed as their department changes. When combined with group-based licensing, a license is provisioned to every member of the group automatically, and it is removed when a user leaves the group. This approach is the recommended Microsoft solution because it scales to thousands of users without manual steps or custom code, and it integrates with Entra ID's inherent license management.

• ✗

  Use Azure AD Connect to filter objects and assign licenses during sync.

  Why it's wrong here

  Azure AD Connect is an identity synchronization tool, not a license assignment engine; it copies user, group, and device attributes from on-premises Active Directory to Entra ID, but it has no ability to apply Microsoft 365 licenses. Filtering objects during sync simply limits which identities are replicated, and licenses still must be assigned by Entra ID licensing or PowerShell separately. Relying on the sync pipeline for licensing would misunderstand the separation between identity provisioning and license entitlement.

• ✗

  Manually assign licenses to each user in the Microsoft 365 admin center.

  Why it's wrong here

  Manually assigning licenses user-by-user in the Microsoft 365 admin center is impractical for 500 accounts and guarantees a high risk of errors, including missed users, incorrect license plans, and inconsistent coverage. It also requires a human to revisit assignments every time a user changes department or leaves the organization, making the process inherently unscalable and non-automated. Group-based licensing with dynamic membership is the appropriate automated alternative.

Go deeper

Related to this question