Letting a powerful role outrank a deny or a policy
The wrong answers let a strong role or a closer scope beat a guardrail. A subscription Owner is treated as winning over a deny assignment or as immune to Azure Policy, and a permissive child policy assignment as overriding a parent deny. Azure Resource Manager checks deny assignments first and blocks access before role evaluation completes. Azure Policy still blocks a non-compliant create or update whatever role the caller holds. Because Policy is an explicit deny system, a child scope is released from a parent deny through an exclusion or exemption.
See it in a sample questionPlacing Conditional Access before authentication
The wrong answers put Conditional Access in front of sign-in, as a defence against credential stuffing or denial-of-service at the public sign-in surface. Conditional Access policies are enforced only after first-factor authentication is completed, so the engine never sees an attempt that has not produced a first-factor token. Smart Lockout, password protection and edge throttling are the controls that sit ahead of it.
See it in a sample questionMismatching alert rule type to how it evaluates
The wrong answers pick an alert rule type that evaluates differently from the requirement. Metric alerts read metric streams, activity log alerts fire on control-plane events, and a traditional log search alert aggregates rows over a window, so none evaluates a single log row almost in real time; a simple log search alert does. State splits the same way: activity log alerts are stateless and fire each time the condition is met, while metric alerts and stateful log search alerts fire once and stay fired until the condition clears.
See it in a sample questionTreating a system-assigned identity as shareable
The wrong answers treat a system-assigned managed identity as something several resources can share, or give every virtual machine in a fleet its own. A system-assigned identity is bound to a single parent resource and shares its life cycle, so it cannot be attached to a second resource and goes when its parent does. A user-assigned managed identity has an independent life cycle and can be shared, which suits resources that are recycled while permissions should persist.
See it in a sample questionAdding Log Analytics workspaces without a driver
The wrong answers add workspaces with no documented driver: one per resource type, one per volume band, or a split to win a discount. Workspace design starts with a single workspace, because the amount of data in a workspace does not impose performance limitations. Further workspaces are justified by separate billing, different retention for the same table, or a tenant boundary. Commitment tiers start at 100 GB per day, so splitting at 9 GB per day unlocks nothing.
See it in a sample question