Judging a role by its name instead of its permissions
The wrong answers pick a role because its name sounds right. Owner is chosen for full resource management, although it also assigns roles in Azure RBAC, so Contributor is the role that cannot. Storage Blob Data Owner is treated as a role-assigning role because of the word Owner, and it is also the broadest choice for a read-only reporting app, where Storage Blob Data Reader is the least-privilege fit.
See it in a sample questionTreating dynamic membership groups as editable by hand
The wrong answers give a dynamic membership group the flexibility of an assigned one. They add a member manually, although membership is computed from the rule, and they put users and devices in a single rule, although a rule covers one object type. They also blame licensing or expression limits when the portal rule builder refuses a device rule. The builder is user-based only, so device rules go in the text box.
See it in a sample questionMisjudging what a management lock blocks
The wrong answers treat a lock as narrower or more negotiable than it is. They expect the other four resources in a group to be deleted while one Delete lock holds, or a child CanNotDelete lock to override a ReadOnly lock inherited from the group. The most restrictive lock in the chain wins, and a Delete lock blocks the whole group delete. Locks cover control plane operations only, so deleting a blob through a data plane request still succeeds.
See it in a sample questionConfusing what each Azure Policy effect does
The wrong answers attach the wrong behaviour to an effect. Audit is offered where a request must be blocked, and deny where a missing tag must be added. Append is offered where a deployment must be stopped, and addOrReplace where an existing tag value must be kept. Audit and deny are also offered for remediation. Deny blocks the create or update request, modify changes the resource, and a remediation task can bring existing resources into compliance only under deployIfNotExists or modify.
See it in a sample questionAssuming self-service password reset covers every user
The wrong answers extend self-service password reset to users it does not reach. Microsoft Entra ID Free supports only cloud-only password change, not reset of a forgotten password. Microsoft accounts granted guest access, such as Outlook.com addresses, cannot use SSPR. A hybrid user whose password is managed on-premises, with SSPR writeback not deployed, is asked to contact an administrator rather than getting a reset.
See it in a sample question