Study guide
10.1 Domain Weight Triage and Study Prioritization
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
10.1 Domain Weight Triage and Study Prioritization
Key Takeaways Explain This Topic AI
AZ-104 time allocation should follow the April 17, 2026 skills weights, with identity/governance and compute receiving the largest combined share.
Integrated cases usually test the boundary between domains rather than isolated definitions.
A triage pass should classify each scenario by failing control plane, data plane, network path, and monitoring evidence.
Microsoft Learn access can help with targeted lookup, but it does not add exam time and excludes some areas.
Study prioritization should combine weighted coverage, local practice weaknesses, and remediation playbooks.
Last updated: May 2026
Start with the real weight of the exam
The current AZ-104 skills outline dated April 17, 2026 splits the exam into five domains. Manage Azure identities and governance is 20-25 percent. Deploy and manage Azure compute resources is also 20-25 percent. Implement and manage storage is 15-20 percent. Implement and manage virtual networking is 15-20 percent. Monitor and maintain Azure resources is 10-15 percent.
That distribution should shape your study time. It should not make you ignore monitoring because monitoring is lower weight. In an administrator exam, monitoring is often the evidence layer for every other domain. A VM boot issue, storage throttling issue, private endpoint DNS issue, backup failure, and policy denial can all surface through logs, metrics, alerts, activity logs, or resource health.
Use this practical weighting table when planning your final review.
Domain Official weight Study priority What integrated cases often look like
Identity and governance 20-25% Very high RBAC scope, locks, policy denial, user/group access, subscription organization
- Compute 20-25% Very high VM, scale set, App Service, container, Bicep, disk, zone, sizing, deployment failure
- Storage 15-20% High SAS, access keys, firewall, private endpoint, lifecycle, redundancy, Azure Files auth
Networking 15-20% High NSG, route, peering, DNS, load balancer, private endpoint, Bastion, connectivity failure
Monitor and maintain 10-15% High for troubleshooting Metrics, logs, alerts, action groups, Network Watcher, backup, Site Recovery
Build a triage pass before solving
Many wrong AZ-104 answers happen because the candidate fixes the first plausible thing instead of identifying the layer that failed. Before picking a remediation, classify the scenario.
Ask four questions. First, is the problem control plane or data plane? A user unable to create a VM is control plane. A workload unable to read blobs is data plane. Second, is the failure identity, network, configuration, quota, policy, or health? Third, what evidence would prove it? Fourth, what is the least privileged or least disruptive change that meets the requirement?
Example: a user can open a storage account but cannot read blobs. That is usually data-plane authorization, not Reader at the storage account management scope. The likely remediation is a data role such as Storage Blob Data Reader at the right scope, assuming network rules also allow access. If the same user cannot see the storage account at all, management-plane Reader may be missing.
Example: a VM cannot reach a private storage endpoint. Do not start by regenerating access keys. Validate DNS resolution for the storage account name, the private DNS zone link, subnet route behavior, NSG rules, and storage firewall settings. Authentication can be correct while the packet path is broken.
Scenario tree for exam triage
Use this tree during practice:
Read the business requirement first: least privilege, no public access, minimize downtime, lowest cost, retain data, or automate repeatably.
Identify the affected resource type: user, group, subscription, storage account, VM, app, VNet, load balancer, vault, alert, or template.
Identify the failed operation: deploy, connect, authenticate, authorize, scale, move, back up, restore, monitor, or resolve name.
Map the failed operation to the likely tool: Azure portal, Azure CLI, PowerShell, ARM/Bicep, Network Watcher, Activity log, metrics, logs, or backup jobs.
Pick the smallest change that fixes the actual failure without weakening security.
This approach matters because AZ-104 scenarios often combine facts. A question might mention a VM, a storage account, a private endpoint, an NSG, and a managed identity. The answer is not automatically compute or storage. The clue is the failed operation. If the VM receives TCP timeouts to the storage endpoint, network path and DNS are leading suspects. If it receives authorization errors after connecting, identity and data-plane roles are leading suspects.
Time budgeting and Microsoft Learn discipline
The assessment time is 100 minutes for the exam form without labs, with 120 minutes seat duration for role-based exams without labs. Exams that may contain labs can have longer exam and seat duration, and Microsoft does not publish a fixed list of exams with labs. Question count is typically 40-60, but it can vary. Passing is 700 or greater.
Role-based exams can provide Microsoft Learn access, but no extra time is added. Treat it as a lookup tool for narrow uncertainty, not as an open research session. Learn access is restricted to learn.microsoft.com and excludes areas such as Q&A, Practice Assessments, and profile. If you spend six minutes searching for a role name you should have studied, you may lose two easier questions later.
Use Learn lookup only after you reduce the question to one missing fact. Good lookup target: which App Service tier supports a required feature, or which storage redundancy option supports a stated failover behavior. Poor lookup target: learning private endpoints from scratch during the exam.
Final-week study allocation
If you have ten focused study hours left, assign roughly two hours to identity and governance, two hours to compute, ninety minutes to storage, ninety minutes to networking, one hour to monitor and maintain, and two hours to mixed case labs. That last block is not optional. It teaches you to detect cross-domain failures quickly.
Use the local practice bank distribution as a second signal, not as the official exam blueprint. If your local missed questions cluster in networking and monitoring, spend more time there even if identity and compute have higher official weights. A mature study plan is weighted by both exam coverage and personal error rate.
Close each practice session with a remediation note. Write the symptom, the evidence, the actual root cause, and the smallest correct fix. For example: Symptom: App Service cannot pull image. Evidence: startup logs show unauthorized to ACR. Root cause: managed identity lacks AcrPull. Fix: assign AcrPull at registry scope and configure app registry identity. This habit turns practice questions into administrator muscle memory.