Picking an adjacent role instead of the narrowest fit
The wrong answers pick a role that sounds adjacent: User Administrator for a domain change, Helpdesk Administrator for service requests, Global Administrator for billing, Authentication Administrator for password resets. Each either lacks the permission or grants far more than the task. The correct answers name the narrowest documented role: Domain Name Administrator for domains, Service Support Administrator for service health and requests, Billing Administrator for purchases, Helpdesk Administrator for non-admin password resets.
See it in a sample questionTreating group-based licensing like direct assignment
The wrong answers have licences flowing through nested groups, let an admin edit an inherited E5 licence on the user page, or use Set-MgUserLicense to fix inherited state. Group-based licensing reaches only the immediate first-level user members of a group. Inherited licences can be modified only at the group level, and Invoke-MgLicenseUser reprocesses the affected users after a violation is resolved, while Set-MgUserLicense changes direct assignments.
See it in a sample questionAssuming one RBAC model governs every portal
The wrong answers place a permission in the wrong role system. Data Loss Prevention and Insider Risk Management experiences in the Defender portal are governed by Microsoft Purview RBAC, not Defender unified RBAC. Compliance Administrator, Global Reader and Security Reader do not provide access to manage Defender unified RBAC; Security Administrator is the minimum Entra role. Exchange Online PowerShell keeps using Exchange Online roles, which unified RBAC does not affect.
See it in a sample questionTying a PIM activation to the sign-in session
The wrong answers link a PIM activation to the session or to a short timer: permissions persist until the user signs out, sign-out acts as a deactivation trigger, or the role reverts after one minute. Activation is time-bound to the duration chosen at activation, up to the maximum administrators configure, and the assignment is removed when that time expires. A role assignment also cannot be deactivated within five minutes after activation.
See it in a sample questionConfusing eligible and active PIM assignments
The wrong answers misstate what separates eligible from active PIM assignments. Options give an eligible assignment fewer permissions, make every active assignment permanent, or pick a permanent or active setting for an on-demand need. Both give the same access, but an eligible assignment requires an action such as MFA, justification or approval before the role can be used. For a three-week contractor who must activate with justification, time-bound eligible fits. Permanent eligible never expires, and time-bound active gives standing privileges for the whole window.
See it in a sample question