Courseiva
Manage Azure Identities and GovernancemediumMultiple SelectObjective-mapped

AZ-104 Manage Azure Identities and Governance Practice Question

Finance, HR, and Engineering each use separate subscriptions. The compliance team wants a simple hierarchy that lets them apply governance to groups of subscriptions and produce resource ownership reports by department and environment. Which two features should the administrator use? Select two.

⚠ Common exam trap

A common mix-up: candidates confuse resource locks with management groups for organizational control, or think availability sets or private endpoints can serve as grouping mechanisms for governance, when they are designed for entirely different purposes (high availability and network security, respectively).

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Management groups to organize the subscriptions into a hierarchy.

Management groups (A) are correct because they allow you to organize multiple subscriptions into a hierarchical structure for applying governance policies and role-based access control at scale. This directly supports the compliance team's need to apply governance to groups of subscriptions and produce resource ownership reports by department and environment.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Management groups to organize the subscriptions into a hierarchy.

    Why this is correct

    Management groups are designed to organize subscriptions above the subscription level. They provide the hierarchy needed to apply governance consistently across sets of subscriptions.

  • Tags on resources to record department and environment values.

    Why this is correct

    Tags are the right mechanism for storing ownership metadata on resources. They support reporting and filtering by business attributes such as department and environment.

  • Resource locks to group subscriptions by business unit.

    Why it's wrong here

    Resource locks protect resources from deletion or modification; they do not organize subscriptions or store ownership metadata. They solve a protection problem, not a reporting problem.

    When this WOULD be correct

    A question asks: 'An administrator needs to prevent critical resources in a production subscription from being deleted. Which feature should be used?' Resource locks (e.g., CanNotDelete) would be correct to protect specific resources.

  • Availability sets to group applications by department.

    Why it's wrong here

    Availability sets are a compute resiliency feature, not a governance or organizational tool. They have nothing to do with subscription hierarchy or ownership reporting.

    When this WOULD be correct

    A question asks: 'Which feature ensures that at least one VM remains available during planned or unplanned maintenance?' Availability sets would be the correct answer.

  • Private endpoints to separate Finance from HR.

    Why it's wrong here

    Private endpoints control network access to specific services. They do not provide subscription grouping or resource ownership metadata for governance reporting.

    When this WOULD be correct

    An administrator needs to ensure that Finance and HR departments access their respective Azure SQL databases privately and securely without exposing them to the public internet. Using private endpoints for each database would be correct.

Option-by-option analysis

Why each answer is right or wrong

Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The AZ-104 exam frequently reuses these exact scenarios with slightly different constraints.

Management groups to organize the subscriptions into a hierarchy.Correct answer

Why this is correct

Management groups are designed to organize subscriptions above the subscription level. They provide the hierarchy needed to apply governance consistently across sets of subscriptions.

Resource locks to group subscriptions by business unit.Wrong answer — click to see why

Why this is wrong here

Resource locks prevent accidental deletion or modification of resources but do not group subscriptions or support hierarchical governance; they operate at the resource or resource group level, not across subscriptions.

★ When this WOULD be the correct answer

A question asks: 'An administrator needs to prevent critical resources in a production subscription from being deleted. Which feature should be used?' Resource locks (e.g., CanNotDelete) would be correct to protect specific resources.

Why candidates choose this

Candidates may confuse 'resource locks' with 'management groups' because both involve grouping or controlling resources, but locks are for protection, not organization or governance hierarchy.

Availability sets to group applications by department.Wrong answer — click to see why

Why this is wrong here

Availability sets are used to ensure high availability of virtual machines by distributing them across fault domains, not for grouping applications by department or for governance and reporting purposes.

★ When this WOULD be the correct answer

A question asks: 'Which feature ensures that at least one VM remains available during planned or unplanned maintenance?' Availability sets would be the correct answer.

Why candidates choose this

Candidates may confuse the grouping concept of availability sets with organizational grouping, thinking they can logically group applications by department, but availability sets are strictly for VM redundancy.

Private endpoints to separate Finance from HR.Wrong answer — click to see why

Why this is wrong here

Private endpoints are used to securely connect to Azure services over a private IP address, not to separate subscriptions or create governance hierarchies. They do not help organize subscriptions or produce resource ownership reports.

★ When this WOULD be the correct answer

An administrator needs to ensure that Finance and HR departments access their respective Azure SQL databases privately and securely without exposing them to the public internet. Using private endpoints for each database would be correct.

Why candidates choose this

Candidates may think private endpoints can isolate resources between departments, confusing network isolation with organizational governance and reporting needs.

Analysis generated from the official AZ-104blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”

Quick reference

Access Control Model Comparison

ModelAcronymWho Controls Access?Best For
Discretionary Access ControlDACResource ownerSmall teams, file shares
Mandatory Access ControlMACSystem / security labelsClassified govt / military
Role-Based Access ControlRBACAdministrator (via roles)Enterprise environments
Attribute-Based Access ControlABACPolicy engine (user + resource attributes)Fine-grained, dynamic policies
Rule-Based Access ControlRuBACSystem rules / ACLsFirewall rules, network ACLs

About these practice questions

This AZ-104 question is part of Courseiva's 1,049-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This AZ-104 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-104 exam.