Study guide

3.7 Governance and Cost Case Lab

AZ-104 Microsoft Azure Administrator Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Orientation and Microsoft Learn Source Control

1.1 Current AZ-104 Exam Facts 1.2 Administrator Role and Candidate Profile 1.3 Skills Outline and Weighted Study Map 1.4 Exam Duration, Question Types, Labs, and Learn Access 1.5 Scoring, Retakes, Renewal, and Account Choice 1.6 Using the Practice Bank, Labs, and Error Log

2 Chapter 2: Identity, RBAC, and Governance Foundations

2.1 Microsoft Entra Users, Groups, and Properties 2.2 Licenses, External Users, and SSPR 2.3 Azure RBAC Built-In Roles and Scopes 2.4 Role Assignment Interpretation and Deny Effects 2.5 Management Groups, Subscriptions, and Resource Groups 2.6 Azure Policy, Locks, Tags, and Governance Controls 2.7 Identity and Governance Case Lab

3 Chapter 3: Subscriptions, Policy, Costs, and Resource Organization

3.1 Subscription Design and Management Groups 3.2 Resource Groups, Lifecycle, and Move Operations 3.3 Tagging Strategy and Cost Allocation 3.4 Budgets, Alerts, and Azure Advisor Cost Recommendations 3.5 Policy, Initiative, Assignment, and Remediation 3.6 Resource Locks, RBAC, Policy, and Tags Combined 3.7 Governance and Cost Case Lab

4 Chapter 4: Storage Accounts, Access, and Data Protection

4.1 Storage Account Design, Redundancy, and Encryption 4.2 Storage Firewalls, Private Access, and Network Rules 4.3 SAS Tokens, Stored Access Policies, and Access Keys 4.4 Identity-Based Access for Azure Files 4.5 Blob Tiers, Lifecycle, Soft Delete, and Versioning 4.6 Azure Files, Snapshots, File Sync, and AzCopy 4.7 Storage Case Lab

5 Chapter 5: Compute, Virtual Machines, Scale Sets, and Bicep

5.1 ARM Templates, Bicep, and Deployment Workflow 5.2 Create, Configure, and Manage Virtual Machines 5.3 VM Disks, Sizes, Encryption, and Host Settings 5.4 Availability Zones, Sets, and VM Scale Sets 5.5 Move VMs Across Resource Groups, Subscriptions, and Regions 5.6 Backup, Restore, and Operational Maintenance for VMs 5.7 VM Compute Case Lab

6 Chapter 6: Containers, App Service, and Platform Compute

6.1 Azure Container Registry and Image Workflow 6.2 Azure Container Instances and Container Apps 6.3 Container Sizing, Scaling, and Environment Choices 6.4 App Service Plan, Apps, and Runtime Configuration 6.5 App Service Certificates, TLS, Custom Domains, and Networking 6.6 App Service Backups, Deployment Slots, and Scaling 6.7 Platform Compute Case Lab

7 Chapter 7: Virtual Networking, Routing, and Secure Access

7.1 VNet, Subnet, and Address Space Design 7.2 VNet Peering and Cross-Network Connectivity 7.3 Public IP Addresses and NAT Patterns 7.4 User-Defined Routes and Effective Routes 7.5 NSGs, ASGs, and Effective Security Rules 7.6 Azure Bastion, Service Endpoints, and Private Endpoints 7.7 Secure Networking Case Lab

8 Chapter 8: Name Resolution, Load Balancing, and Connectivity Troubleshooting

8.1 Azure DNS, Private DNS, and Name Resolution 8.2 Public and Internal Load Balancer Design 8.3 Backend Pools, Health Probes, and Load Balancing Rules 8.4 Load Balancing Troubleshooting Workflow 8.5 Network Watcher: IP Flow, Next Hop, and Connection Troubleshoot 8.6 Hybrid Connectivity, VPN, ExpressRoute, and DNS Considerations 8.7 Connectivity Troubleshooting Case Lab

9 Chapter 9: Monitoring, Alerting, Backup, and Site Recovery

9.1 Azure Monitor Metrics, Logs, and Diagnostic Settings 9.2 Log Analytics, KQL, and Operational Queries 9.3 Alert Rules, Action Groups, and Alert Processing Rules 9.4 VM, Storage, and Network Insights 9.5 Recovery Services Vault, Backup Vault, and Backup Policies 9.6 Azure Site Recovery, Failover, and Replication 9.7 Monitoring and Recovery Case Lab

10 Chapter 10: AZ-104 Integration and Troubleshooting Case Labs

10.1 Domain Weight Triage and Study Prioritization 10.2 Identity, Storage, and Compute Integrated Cases 10.3 Networking, Monitoring, and Security Integrated Cases 10.4 Migration, Move, Backup, and Recovery Cases 10.5 Permissions, Network, and Storage Troubleshooting Chain 10.6 Microsoft Learn Lookup Strategy Under Time Pressure 10.7 Full-Domain Case Lab

11 Chapter 11: Final Review, Exam Experience, Renewal, and Career Path

11.1 Final Two-Week Study Plan 11.2 Hands-On Lab Checklist and Command Review 11.3 Exam Day, Pearson VUE, Breaks, and Learn Access 11.4 Retake Plan, Score Report, and Weak-Domain Repair 11.5 Renewal Assessment and Annual Certification Maintenance 11.6 After AZ-104: AZ-305, AZ-400, SC-500, and Job Paths

3.7 Governance and Cost Case Lab

Key Takeaways Explain This Topic AI

Case labs require translating business requirements into Azure scopes and controls before choosing portal or command steps.

A complete governance design uses management groups, subscriptions, resource groups, RBAC, Policy, tags, budgets, Advisor, and locks together.

Troubleshooting governance failures starts with the error source: RBAC, Policy, locks, provider registration, quota, region, or dependency.

The exam rewards least-privilege and least-scope answers that still meet all stated requirements.

Last updated: May 2026

Case background

Contoso is moving three workloads to Azure: a public web application, an internal finance application, and a developer sandbox. The cloud platform team owns network connectivity, monitoring, and governance. Application teams own their own compute and storage inside approved boundaries. Finance needs monthly cost visibility by application and cost center. Security requires production resources to stay in approved regions, deny public IPs except for the web edge, and prevent accidental deletion of production resource groups.

  • The proposed hierarchy is: Tenant root group
  • |-- mg-platform
  • | |-- sub-connectivity-prod
  • | `-- sub-management-prod
  • |-- mg-prod
  • | |-- sub-web-prod
  • | `-- sub-finance-prod
  • `-- mg-nonprod
  • `-- sub-sandbox-dev

This hierarchy works because it separates stable governance needs. Platform subscriptions host shared network and monitoring assets. Production subscriptions receive stricter policy and budget oversight. Sandbox receives looser resource rules but tighter spending controls. The hierarchy does not mirror every team name, which keeps governance stable as teams change.

Step 1: Select scopes

Start by mapping each requirement to a scope. Approved production regions should be assigned at mg-prod because both production subscriptions need the same allowed locations. Sandbox may have a different policy at mg-nonprod . Platform rules may be assigned at mg-platform . If only the finance application needs a special data classification rule, assign it at sub-finance-prod or its resource group, depending on how broad the rule should be.

  • Requirement Scope Control
  • Production only in approved regions mg-prod Azure Policy deny
  • Sandbox monthly spend warning sub-sandbox-dev Budget
  • Cost by application Resource groups and resources Tags plus Cost Management
  • Finance app delete protection Finance production resource groups CanNotDelete lock
  • Network team manages hub VNet rg-network-hub in platform subscription RBAC
  • Identify idle VMs Subscription or management group view Azure Advisor

The exam often hides the answer in words such as all current and future production subscriptions . That phrase points to a management group assignment. Words such as only this application point toward resource group or subscription scope.

Step 2: Build the resource organization

Create resource groups around lifecycle boundaries. For sub-web-prod , use rg-web-prod , plus dependencies such as rg-web-network-prod only if the network lifecycle is separate. For sub-finance-prod , use rg-finance-app-prod , rg-finance-data-prod , and maybe rg-finance-monitoring-prod if monitoring assets are not centralized. In the platform management subscription, keep shared Log Analytics and action groups away from application resource groups.

Apply required tags at resource group creation: az group create --name rg-finance-app-prod --location eastus --tags Environment=Prod Application=Finance CostCenter=FIN-100 Owner=team-finance Criticality=Tier1

az group create --name rg-web-prod --location eastus --tags Environment=Prod Application=Web CostCenter=MKT-200 Owner=team-web Criticality=Tier1

Then enforce tag consistency with Policy. Use a deny policy to block creation when required tags are missing at resource group scope, and a modify or inherit policy to add tags to resources when practical. Use remediation for existing resources.

Step 3: Configure governance

Assign an initiative named something like Contoso production baseline to mg-prod . Include allowed locations, required tags, deny public IPs except where excluded, require diagnostic settings, and audit insecure storage configuration. Parameterize allowed regions and tag names. For the web edge exception, avoid weakening the baseline for all production. Use an exemption for the approved web edge resource group or design the policy condition to allow public IPs only when an approved tag or resource group is present.

Assign RBAC with least privilege. The network team can be Network Contributor on the hub network resource group. The monitoring team can be Monitoring Contributor on the management subscription or monitoring resource group. Application teams can be Contributor on their own application resource groups, but not Owner at the subscription unless there is a clear administrative need. Billing readers or cost management roles can be assigned for finance reporting as required by the account type.

Add locks to production resource groups that should not be deleted accidentally: az lock create --name lock-rg-finance-prod --lock-type CanNotDelete --resource-group rg-finance-app-prod

az lock create --name lock-rg-web-prod --lock-type CanNotDelete --resource-group rg-web-prod

Use ReadOnly locks sparingly. They can block legitimate management operations such as scaling, diagnostics changes, or backup adjustments. For active production environments, CanNotDelete usually addresses accidental deletion while allowing controlled changes.

Step 4: Configure cost operations

Create monthly budgets at production subscription scopes and a stricter sandbox budget. Configure thresholds such as 70 percent forecasted, 90 percent actual, and 100 percent actual. Add action groups if notifications must integrate with ticketing or automation. Use Cost Management views grouped by Application , CostCenter , and Environment . Review untagged cost regularly because untagged spend usually means the deployment process or policy assignment needs correction.

Use Azure Advisor weekly or during cost reviews. Investigate underutilized VMs, unattached disks, idle public IP addresses, App Service plan utilization, and reservation or savings opportunities. Do not apply recommendations blindly. Check owner, performance history, business cycles, and reliability requirements.

Step 5: Troubleshoot lab failures

Failure 1: The finance team cannot deploy a VM in North Europe. Check policy first if the production baseline allows only East US and West US 2. Contributor access does not bypass deny policy. The fix is to deploy in an allowed region or request a policy change or exemption.

Failure 2: The web team cannot delete a test public IP in the production web resource group. Check locks. A resource group CanNotDelete lock blocks deletion of child resources. The fix is controlled lock removal, deletion, and lock reapplication if approved.

Failure 3: Cost reports show unallocated spending. Check tag consistency and timing. Tags may be missing on charge-generating resources, spelled inconsistently, or applied after usage occurred. Use Policy remediation and template corrections.

Failure 4: A deployment fails with a provider namespace error. Check resource provider registration in the subscription. Register the provider or use a deployment path that registers it, assuming permissions allow registration.

Exam-readiness checklist

For every governance case, ask six questions before picking an answer. What scope is required? Who needs permission? What configuration must be allowed or denied? What metadata is needed for reporting? What should notify people? What must be protected from deletion or change? This forces you to choose the Azure feature that matches the requirement instead of selecting a familiar tool.

The best AZ-104 answer is usually the smallest scope that satisfies the requirement. Use management groups for broad inherited governance, subscriptions for billing and quota boundaries, resource groups for lifecycle, RBAC for permissions, Policy for configuration compliance, tags for classification, budgets for spend alerts, Advisor for optimization, and locks for deletion or write protection.