Show the 15 questions and explanations
An administrator wants to create a group they can assign the Helpdesk Administrator role to, and they want the group's membership to populate automatically using a dynamic rule based on job title. In the group creation blade, when they set "Microsoft Entra roles can be assigned to the group" to Yes, the dynamic membership option becomes unavailable. Why can these two settings not be combined?
Correct answer: A. Role-assignable groups must use Assigned membership; dynamic membership is blocked by design so that editing an attribute cannot silently add someone to a privileged role.
Only groups created with the isAssignableToRole property set to true can be assigned Microsoft Entra roles, and that property is immutable. A core restriction of role-assignable groups is that their membership type must be Assigned and cannot be dynamic. Microsoft designed it this way to prevent elevation of privilege: if dynamic membership were allowed, anyone who could modify the attributes referenced in the rule could add an account to the group and thereby grant it the assigned role. Creating a role-assignable group also requires at least the Privileged Role Administrator role.
Why the other options are wrong:
- B. Dynamic membership requires a Microsoft Entra ID P2 license, which the tenant does not have. The blocker is not a P2 requirement. Dynamic membership needs P1, and role-assignable groups are available with P1 or P2. The conflict is a design restriction, not a licensing gap.
- C. The Helpdesk Administrator role cannot be assigned to any group, only to individual users. Helpdesk Administrator can be assigned to a role-assignable group; assigning roles to groups is a supported and recommended pattern. The restriction is only that such a group must be Assigned, not dynamic.
- D. Role assignment requires a Microsoft 365 group, and Microsoft 365 groups do not support dynamic membership. Both security and Microsoft 365 groups can be made role-assignable. The membership type, not the group type, is what must be Assigned.
Memory hook: Role-assignable means Assigned-only. Dynamic plus a role would turn an attribute edit into a privilege backdoor, so it is forbidden.
Microsoft Learn: Groups concept
An administrator uses group-based licensing to assign Microsoft 365 E5 to a parent security group named All-Staff. All-Staff contains a nested child group, Contractors, whose members belong only through that child group. After processing, direct members of All-Staff receive licenses but the contractors do not. Separately, several users who had no Usage location set still received their licenses. Which statement correctly explains both behaviors?
Correct answer: C. Group-based licensing does not support nested groups, so only first-level (direct) members of the licensed group are assigned licenses; and under group-based licensing, users without a Usage location inherit the tenant's location
Group-based licensing does not support nested groups. If you assign licenses to a group that contains other groups, only the first-level (direct) user members are licensed; members who belong only through a nested child group are not. Separately, although a direct per-user license assignment fails without a Usage location, under group-based licensing any user without a location inherits the tenant's location, so licensing still succeeds for those users.
Why the other options are wrong:
- A. Group-based licensing cascades to all nested members automatically; the contractors failed only because the tenant ran out of licenses Licensing does not cascade to nested members under any condition. The contractors were skipped because they are nested-only members, not because of a license shortage.
- B. Nested group members are licensed after a 24-hour delay, and Usage location is never relevant to group-based licensing There is no delayed cascade to nested members; nested-only members are simply not licensed at all. Usage location is also relevant, since users inherit the tenant location under group-based licensing.
- D. The parent must be a Microsoft 365 group for nested licensing to cascade, and Usage location must be set manually or the assignment fails Group type does not enable a nested cascade; nested groups are unsupported for licensing regardless of whether the parent is a security or Microsoft 365 group. And for group-based licensing the location is inherited from the tenant, not required to be set manually.
Memory hook: Group-based licensing is flat: only direct members get licensed, never nested. No Usage location? Group-based licensing borrows the tenant's location.
Microsoft Learn: Concept group based licensing
An organization currently has only Microsoft Entra ID Free. The security team wants to create a custom role that grants a narrow set of permissions (for example, managing app registration credentials) and assign it to three engineers. What licensing applies to this plan?
Correct answer: C. Microsoft Entra ID P1 is required for each user assigned a custom role; built-in roles remain free.
Using built-in Microsoft Entra roles is free, but custom roles require a Microsoft Entra ID P1 license for every user who holds a custom role assignment. Microsoft Learn's licensing page states this directly, and the custom-role creation prerequisites list a P1 or P2 license plus the Privileged Role Administrator role. So the three engineers assigned the custom role each need P1 coverage; the organization cannot do this on Free alone.
Why the other options are wrong:
- A. Custom roles are free just like built-in roles, so no premium license is required. Only built-in roles are free. The moment you assign a custom role, each assignee requires a P1 license, so this plan is not free.
- B. The Microsoft Entra ID Governance add-on is required to create any custom role. The Governance add-on is not required for custom RBAC roles. A P1 license (already the minimum tier above Free) plus Privileged Role Administrator is sufficient.
- D. Microsoft Entra ID P2 is required because custom roles are a governance feature. Custom roles require P1, not P2. P2 adds Identity Protection and PIM, but it is not what gates the creation or assignment of a custom directory role.
Memory hook: Built-in roles are free. Custom roles cost P1 for every assignee.
Microsoft Learn: Fundamentals: Licensing
A company must guarantee that Helpdesk Administrators and even tenant-level Global Administrators cannot reset the passwords of C-level executive accounts or read their BitLocker keys, without stripping those admins of their tenant-wide roles. Only a small, explicitly designated set of administrators should be able to manage the executive accounts. Which Microsoft Entra capability meets this requirement?
Correct answer: B. A restricted management administrative unit containing the executive accounts, with a role scoped to that unit assigned only to the designated administrators
A restricted management administrative unit protects specific objects so that only administrators explicitly assigned a role at the scope of that unit can modify them. Even tenant-level Global Administrators and Privileged Role Administrators are blocked from modifying the objects unless they scope themselves to the unit, which is an auditable event. Placing the executive accounts in a restricted management administrative unit and assigning the trusted administrators a role (for example, Authentication Administrator) at that scope meets the requirement without removing anyone's tenant-wide roles.
Why the other options are wrong:
- A. A dynamic membership group of executives combined with a Conditional Access policy that blocks password reset Conditional Access governs sign-in access conditions, not which administrators may perform a password reset on an object. It cannot enforce this admin-scoping requirement.
- C. A regular administrative unit containing the executive accounts, with Helpdesk Administrator scoped to it A regular (non-restricted) administrative unit narrows a scoped admin's reach, but it does not block tenant-level administrators. A Global Administrator, or a Helpdesk Administrator with tenant scope, could still reset the executives' passwords. Only a restricted management administrative unit blocks tenant-level admins.
- D. Assigning the executives the Privileged Role Administrator role so only they can manage their own accounts Privileged Role Administrator manages role assignments tenant-wide and does not restrict who can manage the executives' accounts. Assigning it to executives is both incorrect for the goal and a privilege-escalation risk.
Memory hook: Block even Global Admins from touching sensitive accounts, without removing their roles = Restricted Management AU. A regular AU does not stop tenant-level admins.
Microsoft Learn: Admin units restricted management
An administrator reviews the Identity Secure Score in Microsoft Entra ID and finds the recommendation 'Require MFA for administrative roles' shows a low score. The administrator implements MFA for all administrator accounts. How frequently does the Identity Secure Score recalculate, and where does the score appear relative to the overall Microsoft Secure Score?
Correct answer: C. The score recalculates every 24 hours and represents the identity category of the Microsoft Secure Score
The Identity Secure Score evaluates your security configuration every 24 hours and computes a new score based on how closely your settings align with Microsoft's recommendations. The score is available in the Microsoft Entra admin center under Identity Secure Score and also under Recommendations. It directly corresponds to the identity category within the Microsoft Secure Score, which has five categories: Identity, Data, Devices, Infrastructure, and Apps. Improvements to the Identity Secure Score improve the identity component of the overall Microsoft Secure Score.
Why the other options are wrong:
- A. The score recalculates weekly and is only accessible via the Microsoft Defender XDR portal The Identity Secure Score recalculates every 24 hours, not weekly. While the Microsoft Defender XDR portal shows the full Microsoft Secure Score and its history, the Identity Secure Score is primarily accessible in the Microsoft Entra admin center.
- B. The score recalculates every 30 minutes and is separate from the Microsoft Secure Score The Identity Secure Score does not recalculate every 30 minutes. The documented recalculation interval is every 24 hours. It is not separate from the Microsoft Secure Score - it is the identity portion of that score.
- D. The score recalculates in real time and replaces the Microsoft Secure Score for identity workloads The score does not recalculate in real time. Changes to security configuration take up to 24 hours to reflect in the score. It does not replace the Microsoft Secure Score; it feeds into the identity category of it.
Memory hook: Identity Secure Score = daily report card for identity security. It feeds the identity column of the Microsoft Secure Score table.
Microsoft Learn: Concept identity secure score
A licensing operations team must be able to assign and remove Microsoft 365 licenses for users, but they should not be able to create or delete users, reset passwords, or purchase subscriptions. Following least privilege, which Microsoft Entra role should you assign?
Correct answer: D. License Administrator
License Administrator is the least-privileged role for assigning and removing user and group licenses. Microsoft Learn's least-privileged-roles-by-task reference lists License Administrator as the minimum role for both "Assign license" and "Revoke license." It grants the ability to manage license assignments (and read license configuration) without the broader user-management or purchasing powers that other roles carry, which fits the requirement exactly.
Why the other options are wrong:
- A. User Administrator User Administrator can assign licenses, but it can also create and delete users and reset passwords for non-admins, which exceeds what this team needs. It is listed only as an additional (higher-privilege) role for the licensing task, not the least-privileged one.
- B. Billing Administrator Billing Administrator manages purchases and subscriptions (try or buy a subscription) but is not the role used to assign or remove per-user license seats.
- C. Global Administrator Global Administrator has full control of the entire tenant, far more than required, and violates least privilege for a licensing-only function.
Memory hook: Just licenses and nothing else = License Administrator. User Admin is a bigger hammer than the task needs.
Microsoft Learn: Delegate by task
To reduce casual directory browsing, an administrator sets 'Restrict access to the Microsoft Entra admin center' to Yes for non-admin users. A security reviewer asks whether this reliably prevents those users from reading directory data. What is the correct understanding of this setting?
Correct answer: C. No, it only adds friction by hiding common admin center pages; Microsoft states it is not a security measure and it does not block programmatic access to directory data via Microsoft Graph, PowerShell, or other tools
'Restrict access to the Microsoft Entra admin center' only limits access to a set of commonly visited admin center pages for non-admin users. Microsoft is explicit that this is not a security measure: it does not block programmatic access to Microsoft Entra data via PowerShell, the Microsoft Graph API, or other tools, and many pages remain reachable through direct links. For real enforcement, Microsoft recommends a Conditional Access policy targeting the Windows Azure Service Management API.
Why the other options are wrong:
- A. It requires Microsoft Entra ID P2 and applies only to guest users It has no P2 dependency and is not guest-specific. It is a member-user default that governs admin center portal access only.
- B. Yes, it is a security boundary that blocks all directory reads by non-admin users It is not a security boundary. Microsoft states directly that the setting is not a security measure and that it does not protect directory data; it only adds friction to portal browsing.
- D. It blocks non-admins from the admin center and automatically revokes their existing Microsoft Graph tokens The setting does not touch tokens or Graph access at all. It only limits which admin center pages non-admins can load in the portal UI.
Memory hook: Restricting the admin center hides the portal, not the data. Graph and PowerShell still read the directory. Microsoft says it is not a security control.
Microsoft Learn: Users default permissions
During a reorganization, an administrator changes an Azure subscription's associated Microsoft Entra directory (tenant) from Tenant A to Tenant B. Which statement best describes the result of this change?
Correct answer: D. Azure RBAC role assignments on the subscription are lost, because a subscription can trust only one tenant at a time; the user accounts themselves are not moved.
Every Azure subscription has a trust relationship with exactly one Microsoft Entra tenant at a time (though one tenant can be trusted by many subscriptions). Changing the subscription's directory changes which tenant supplies identities for Azure RBAC. Microsoft Learn warns that when a subscription is associated with a different directory, users who had access through Azure role assignments lose that access, and classic administrators lose access too. It does not move user accounts between tenants; it only re-points which identity store Azure checks for that subscription.
Why the other options are wrong:
- A. Nothing changes for access, because Azure role assignments follow the subscription to whichever directory it trusts. Role assignments do not follow the subscription. Because the trusted directory changed, existing Azure RBAC assignments that referenced principals in the old tenant are lost.
- B. The subscription now trusts both Tenant A and Tenant B simultaneously for authentication. A subscription can trust only a single tenant at any given time. It cannot simultaneously trust two directories.
- C. All user accounts in Tenant A are moved into Tenant B along with the subscription. Directory objects such as user accounts do not move when you change a subscription's trusted tenant. Only the trust (which directory authorizes access) changes.
Memory hook: A subscription trusts exactly one tenant. Re-point it and the Azure RBAC assignments fall off. Identities do not move.
Microsoft Learn: How subscriptions associated directory
An organization set Guest invite settings to 'Only users assigned to specific admin roles can invite guest users.' A project lead who holds no administrator role now needs to invite external partners as B2B guests, but must not receive any broader directory privileges. Which role should you assign?
Correct answer: D. Guest Inviter
The Guest Inviter role gives an individual user the ability to invite B2B guests without assigning a higher-privilege administrator role. Users with the Guest Inviter role can invite guests even when 'Only users assigned to specific admin roles can invite guest users' is selected. It carries no other directory-management permissions, so it exactly meets the least-privilege requirement.
Why the other options are wrong:
- A. Global Administrator Global Administrator is the most privileged role in the tenant. Assigning it merely to invite guests grossly over-provisions the project lead.
- B. External Identity Provider Administrator External Identity Provider Administrator manages the configuration of external identity providers and federation (such as SAML/social IdPs). It is not the role for granting a single user the ability to send guest invitations.
- C. User Administrator User Administrator can invite guests, but it also creates and manages users and resets non-admin passwords. That is far more than the ability to invite guests, so it violates least privilege.
Memory hook: Invite guests and nothing else = Guest Inviter. It works even when only specific admin roles may invite.
Microsoft Learn: External collaboration settings configure
A cloud engineer holds the Microsoft Entra User Administrator role. They can manage users and groups in the Entra admin center, but in the Azure portal they cannot start, stop, or resize the virtual machines in a resource group. What correctly explains this and the appropriate fix?
Correct answer: C. Microsoft Entra roles and Azure RBAC are separate systems: Entra roles govern directory resources, not Azure resources. To manage the VMs, assign an Azure RBAC role such as Virtual Machine Contributor at the appropriate scope (management group, subscription, resource group, or resource)
Microsoft Entra roles and Azure RBAC are independent authorization systems. Microsoft Entra roles control access to directory resources (users, groups, applications) through Microsoft Graph, while Azure RBAC controls access to Azure resources (VMs, storage) through Azure Resource Manager. Entra role permissions can't be used in Azure and vice versa. To let the engineer manage the VMs, assign an Azure RBAC role like Virtual Machine Contributor; Azure RBAC scope can be a management group, subscription, resource group, or individual resource.
Why the other options are wrong:
- A. Azure RBAC roles can be assigned only at the subscription level, so resource-group-scoped VM management is not possible Azure RBAC scope can be set at multiple levels, including management group, subscription, resource group, and individual resource, not only the subscription.
- B. The engineer needs the Microsoft Entra Global Administrator role, which automatically grants full control of all Azure resources Global Administrator is an Entra role and, by default, does not grant access to Azure resources because the two planes are separate. A Global Administrator can elevate to User Access Administrator at root scope, but that is a deliberate extra step, not automatic full control.
- D. Assign the User Access Administrator Microsoft Entra role, which bridges directory and Azure resource permissions User Access Administrator is an Azure RBAC role, not a Microsoft Entra directory role, and it manages user access to Azure resources. It does not bridge the two systems as an Entra role, and it would not be the natural role for managing VM power state.
Memory hook: Entra roles = directory; Azure RBAC = Azure resources. To touch VMs, assign an Azure role (e.g., VM Contributor) at MG/sub/RG/resource scope.
Microsoft Learn: RBAC and directory admin roles
An administrator adds a security group to an administrative unit and assigns a User Administrator scoped to that unit. A support technician in that role needs to reset the password of a user who is a member of the group. The user object itself has NOT been added directly to the administrative unit. What is the result when the technician attempts the password reset?
Correct answer: A. The password reset fails because adding a group to an administrative unit does not add the group members to the unit
Adding a group to an administrative unit brings the group object itself into the management scope of the administrative unit, but it does not bring the group's members into scope. A User Administrator scoped to the administrative unit can manage the group's properties and membership, but cannot manage individual user properties or reset passwords for group members unless those users are also directly added as members of the administrative unit.
Why the other options are wrong:
- B. The password reset succeeds because group membership implies administrative unit membership Group membership does not imply administrative unit membership for users. The Microsoft Learn documentation explicitly states that individual users must be directly added as administrative unit members for scoped user management to apply.
- C. The password reset fails only if the user is also a member of another administrative unit Membership in other administrative units does not affect this outcome. The issue is that the user is not a member of this specific administrative unit, regardless of any other unit memberships.
- D. The password reset succeeds if the group is a dynamic group Whether the group is dynamic or static does not change this behavior. Dynamic membership controls how users enter or exit the group, not whether they are scoped within the administrative unit.
Memory hook: A group in an AU is like parking a bus in a lot. You control the bus, not the passengers individually.
Microsoft Learn: Administrative units
A collaboration lead wants end users to create and own their own security groups from the My Groups portal, and to let group owners approve or deny join requests, without granting users any admin role. In Microsoft Entra group settings, which change is needed, and what license is required for the request-to-join and approval behavior?
Correct answer: B. Set 'Users can create security groups' to Yes; a Microsoft Entra ID P1 or P2 license is required for users to request to join a group and for owners to approve or deny those requests
Setting the tenant option 'Users can create security groups' to Yes lets non-admin users create and own security groups (including from the My Groups portal). However, a Microsoft Entra ID P1 or P2 license is required for users to request to join a security or Microsoft 365 group and for owners to approve or deny those membership requests. Without P1/P2, users can still manage groups they own but cannot use the join-request/approval flow.
Why the other options are wrong:
- A. Assign every user the Groups Administrator role so they can self-manage groups Groups Administrator is a privileged directory role. The correct approach for self-service is the tenant group setting, not handing every user an administrative role.
- C. Nothing can be done, because self-service group management is available only for mail-enabled security groups and distribution lists Self-service group management is available only for security groups and Microsoft 365 groups. It is not available for mail-enabled security groups or distribution lists, so the premise is reversed.
- D. Set 'Users can create security groups' to Yes; the request-to-join and owner approval behavior is included in Microsoft Entra ID Free The request-to-join and owner approve/deny flow specifically requires a P1 or P2 license. It is not part of Microsoft Entra ID Free.
Memory hook: 'Users can create security groups = Yes' enables self-service; the join-request + owner-approval flow needs P1/P2.
Microsoft Learn: Groups self service management
To pre-stage onboarding, you want a dynamic membership group that automatically contains users whose employment start date falls within the next 7 days, so licenses and access provision before Day 1. Which membership rule works?
Correct answer: D. (user.employeeHireDate -ge system.now) -and (user.employeeHireDate -le system.now -plus p7d)
employeeHireDate is the date/time property that supports comparison against the system.now keyword using -ge/-le together with the -plus <duration> operator, where the duration is ISO 8601 (for example p7d = 7 days). Bounding the value between system.now and system.now -plus p7d, and joining the two expressions with the hyphenated -and logical operator, selects users whose hire date falls within the next seven days.
Why the other options are wrong:
- A. (user.startDate -le system.add(7)) user.startDate is not a supported property and system.add(7) is not a valid function or syntax in dynamic membership rules.
- B. (user.employeeHireDate -ge now() -7) now() and arithmetic such as '-7' are not valid dynamic-rule syntax; the keyword is system.now used with the -plus <ISO 8601 duration> operator.
- C. (user.createdDateTime -ge system.now -plus p7d) createdDateTime is the object-creation timestamp, not the hire date, and it can't hold a future value, so this never selects upcoming hires.
Memory hook: Future hires = employeeHireDate between system.now and system.now -plus p7d, joined with -and.
Microsoft Learn: Groups dynamic membership
Fabrikam and Contoso configure a mutual B2B direct connect trust. A Contoso Teams shared channel owner adds a Fabrikam user to a shared channel. What is true about how that Fabrikam user is represented and managed in Contoso?
Correct answer: A. No user object is created in Contoso's directory; the external user is managed within Teams by the shared channel owner.
B2B direct connect users don't have a presence (no user object) in the resource organization's Entra directory. They access only the shared channel using their home-tenant credentials and are managed inside the Teams client by the shared channel owner. B2B collaboration guests, by contrast, do get a user object.
Why the other options are wrong:
- B. A member user object is created in Contoso and consumes a Contoso license. Wrong: no member object is created and no Contoso license is consumed.
- C. The user is added to Contoso's directory as a contact object. Wrong: no contact object is created either. There is no Contoso directory object at all.
- D. A guest (B2B collaboration) user object is created in Contoso's directory and appears under Users. Wrong: that describes B2B collaboration (which creates a guest object), not B2B direct connect.
Memory hook: Direct connect = no object in your directory (managed in Teams); guests get objects, direct-connect users don't.
Microsoft Learn: B2B direct connect overview
A marketing coordinator must update the corporate sign-in page background image and banner logo for the tenant. Company policy requires least privilege: the coordinator must not be able to manage users, groups, or any other directory configuration. Which Microsoft Entra role should you assign?
Correct answer: B. Organizational Branding Administrator
The Organizational Branding Administrator role is the minimum role required to customize company branding, including the sign-in page background, logos, header, footer, and sign-in page text. It grants only branding-management permission and nothing else in the directory, which makes it the correct least-privilege choice for delegating sign-in page customization to a marketing team.
Why the other options are wrong:
- A. Application Administrator Application Administrator manages enterprise applications and app registrations. It does not grant permission to configure company branding.
- C. Global Administrator Global Administrator can configure branding but has full control of the entire tenant, far more than needed. Microsoft flags Global Administrator as highly privileged and reserved for emergency scenarios, so using it here violates least privilege.
- D. User Administrator User Administrator manages users and some groups but cannot configure company branding, and it also grants unrelated user-management powers the coordinator should not have.
Memory hook: Sign-in page look and feel = Organizational Branding Administrator. It does branding and nothing else.
Microsoft Learn: Customize branding