AZ-305 domain - 27% of the exam

Design Identity, Governance, and Monitoring Solutions

Design Identity, Governance, and Monitoring Solutions is 27% of the AZ-305 exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

70
Practice questions
3
Objectives
46
Medium
24
Hard

Where people go wrong

  • 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 question
  • Placing 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 question
  • Mismatching 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 question
  • Treating 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 question
  • Adding 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

Objectives in this domain

Sample questions from this domain

Free sampleDesign Identity, Governance, and Monitoring Solutionsmedium

An architect believes that a subscription Owner role assignment always wins over any deny assignment scoped to a resource group inside that subscription. A deny assignment on a resource group is overridden by an Owner role assignment at the subscription scope. Is this statement correct?

  • AYes
  • BNo Correct
Deny assignments outrank role assignments, including Owner. The Azure RBAC evaluation flow checks deny assignments first; if a deny assignment applies, access is blocked. Higher-scope role assignments, including Owner at the subscription, do not override a deny assignment on a child scope.

Why A is wrong: Treating Owner as universally winning is the standard misconception. Deny assignments are guardrails that intentionally outrank allow assignments to protect critical resources.

Why B is correct: Correct. The Azure RBAC evaluation flow checks deny assignments first; if a deny assignment applies, access is blocked.

Free sampleDesign Identity, Governance, and Monitoring Solutionsmedium

An architect proposes Conditional Access as the primary defence against a credential-stuffing attack that occurs before any password is evaluated. Recommend the most accurate position to take in the design review.

  • AConditional Access intercepts all unauthenticated requests at the network edge before any credentials are evaluated.
  • BConditional Access enforces after first-factor authentication and is not a frontline DoS or pre-auth defence. Correct
  • CConditional Access policies are evaluated only when explicit user assignment matches; they ignore signals during a credential-stuffing storm.
  • DConditional Access acts as the first line of defence and replaces the need for Smart Lockout on Microsoft Entra ID.
Conditional Access runs after first-factor sign-in, not before. Microsoft is explicit that Conditional Access policies are enforced after first-factor authentication is completed. The engine is not the frontline defence for scenarios like denial-of-service attacks, though it can consume signals from those events.

Why A is wrong: The engine runs after first-factor sign-in completes; it never sees an unauthenticated stuffing attempt because no first-factor token has been issued yet.

Why B is correct: Correct. Microsoft is explicit that Conditional Access policies are enforced after first-factor authentication is completed.

Why C is wrong: Policies still consume risk and identity signals even during attacks, but they cannot block a request that never produced a valid first-factor token.

Why D is wrong: Smart Lockout and password protection sit ahead of Conditional Access; the engine assumes the password has already been validated.

Free sampleDesign Identity, Governance, and Monitoring Solutionsmedium

An operations team needs alerting on a custom Log Analytics table that captures security audit records: each individual row must trigger a notification within roughly a minute of arrival, with no aggregation over a time window. The team has rejected the traditional aggregated query option because it cannot evaluate rows one-by-one in near real time. Which Azure Monitor alert rule type is the documented best fit?

  • AMetric alert with dynamic thresholds over a 5-minute window
  • BSimple log search alert evaluating each row individually Correct
  • CActivity log alert filtered to administrative events
  • DStandard log search alert with a 5-minute aggregated query
When you need near real-time evaluation of each row in a Log Analytics query, the simple log search alert is the documented fit. The Azure Monitor alerts overview specifies that simple log search alerts allow users to evaluate each row of a Log Analytics query individually rather than aggregating rows over a window. The documentation positions this type as the faster, near real-time alternative to the standard log search alert when the requirement is per-event detection on a custom table. Standard log search alerts aggregate rows over a defined period, which the scenario explicitly rejects. Metric alerts and activity log alerts cannot evaluate custom log rows in a Log Analytics table.

Why A is wrong: Metric alerts evaluate platform or custom metrics at a resource level and cannot evaluate individual rows in a Log Analytics table.

Why B is correct: Correct. The Azure Monitor alerts overview specifies that simple log search alerts allow users to evaluate each row of a Log Analytics query individually rather than aggregating rows over a window.

Why C is wrong: Activity log alerts fire on Azure control-plane events such as resource deletions, not on records inside a custom log table.

Why D is wrong: A standard log search alert aggregates rows over a window, which the scenario explicitly rejects because it cannot detect individual events.

Free sampleDesign Identity, Governance, and Monitoring Solutionsmedium

A platform team plans to attach one system-assigned managed identity to two virtual machines to consolidate RBAC assignments. A system-assigned managed identity can be associated with more than one Azure resource so multiple VMs can share a single identity. Is this statement correct?

  • AYes
  • BNo Correct
System-assigned managed identities are one per resource; sharing requires user-assigned. System-assigned managed identities can only be associated with a single Azure resource and share its life cycle. To share an identity across multiple Azure resources, the documented pattern is a user-assigned managed identity.

Why A is wrong: Treating system-assigned as shareable is a common shortcut that fails at deployment time; the assignment is bound to a single parent resource and cannot be attached to a second.

Why B is correct: Correct. System-assigned managed identities can only be associated with a single Azure resource and share its life cycle.

Free sampleDesign Identity, Governance, and Monitoring Solutionsmedium

An architect is designing the Log Analytics topology for a workload that runs entirely in one Microsoft Entra tenant and one Azure region with no regulated data residency. Operations and security teams share ownership and want WAF Operational Excellence pillar OE:07 satisfied with the least management overhead. Which workspace design should you recommend?

  • AProvision one shared Log Analytics workspace and use table-level RBAC where needed. Correct
  • BProvision a dedicated workspace per resource type and federate queries across them.
  • CProvision a workspace per subscription so billing splits cleanly between platform and workload owners.
  • DProvision separate workspaces for operational and security data in different regions for resilience.
Start with one Log Analytics workspace; only split when a documented design criterion forces it. The Log Analytics workspace design guidance states the design should always start with a single workspace and add more only when a documented driver (regulatory region, billing split, retention divergence, tenant boundary) applies. None of those drivers are present here, so the lowest-overhead WAF-aligned answer is a single workspace with table-level RBAC where ownership boundaries need enforcement.

Why A is correct: Correct. The Log Analytics workspace design guidance states the design should always start with a single workspace and add more only when a documented driver (regulatory region, billing split, retention divergence, tenant boundary) applies.

Why B is wrong: Per-resource-type workspaces explode operational overhead and complicate cross-table joins without satisfying any of the documented design criteria.

Why C is wrong: Split billing is a valid driver only when separate billing parties exist; the scenario describes one workload with no billing split.

Why D is wrong: Multi-region resilience is a separate design driver and adds egress and management cost when the workload runs in a single region without that requirement.

Other domains in this exam

See also the AZ-305 cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by Microsoft. Original, blueprint-aligned practice material only.