Study guide

11.2 Hands-On Lab Checklist and Command Review

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

11.2 Hands-On Lab Checklist and Command Review

Key Takeaways Explain This Topic AI

Hands-on review should cover portal paths, Azure CLI, PowerShell, and Bicep or ARM interpretation.

Build checklists around complete administrator workflows rather than isolated commands.

Practice troubleshooting evidence: effective routes, effective security rules, metrics, logs, backup jobs, and deployment errors.

Know when a portal action is best for inspection and when CLI, PowerShell, or IaC is better for repeatability.

Labs may appear in the exam experience, but Microsoft can remove them and does not publish a fixed lab list.

Last updated: May 2026

Hands-on work that survives exam pressure

AZ-104 is an administrator exam, so the final lab checklist should look like work an Azure administrator actually performs. Build, change, validate, and troubleshoot resources. Do not reduce lab practice to clicking through resource creation once. A good checklist forces you to answer three questions: what setting solves the requirement, what side effect does it create, and what evidence proves it worked.

Microsoft says role-based exams can include multiple-choice, build list, case studies, drag/drop, hot area, labs, mark and review, and other UI interactions shown in the exam sandbox. Labs may be present, and Microsoft can remove them at any time. That means hands-on practice is still essential, but you should not assume your exam will contain a specific lab count or a published lab catalog.

Workflow Practice task Validation evidence

RBAC Assign a built-in role at resource group scope Access check, role assignment list, denied action outside scope

Policy Assign a policy and remediate existing resources Compliance state and remediation task result

Storage Configure Blob soft delete, versioning, lifecycle, and SAS Container settings, generated SAS scope, test access

  • VM Deploy a VM with disk, NSG, Bastion, and backup VM status, effective rules, backup job status
  • Networking Configure peering, UDR, DNS, and private endpoint Connection test, effective routes, DNS resolution

Monitoring Create metric and log alerts with action groups Fired alert, action group notification, query result

Identity and governance checklist

Create users and groups in Microsoft Entra ID, invite an external user, and assign access through a group instead of a direct user assignment. Practice assigning Reader, Contributor, User Access Administrator, Storage Blob Data Contributor, and Virtual Machine Contributor at different scopes. Then remove a role and confirm that the principal loses the action. For governance, apply tags, create a budget, configure a cost alert, review Advisor recommendations, assign a policy, create an exemption only when the scenario supports it, and test a resource lock.

  • Useful command review: az role assignment create --assignee <principalId> --role "Reader" --scope <scope>
  • az policy assignment create --name require-tag --policy <policyDefinitionId> --scope <scope>
  • az group update --name rg-prod --set tags.Environment=Prod tags.Owner=Ops

The command itself is not enough. Know the scope format, the difference between control-plane RBAC and data-plane roles, and the lock behavior. RBAC grants permissions, but a lock can still block management actions. Policy evaluates compliance and can deny or modify deployments depending on the effect.

Storage checklist

Create a storage account with the correct redundancy for the scenario. Configure a Blob container, upload data with AzCopy, set access tiers, enable soft delete and versioning, create a lifecycle rule, and generate a SAS with minimal permissions and a short expiry. Configure Azure Files and identity-based access if the scenario requires SMB access controlled through identity. Practice storage firewall rules, selected networks, trusted Microsoft services, service endpoints, and private endpoints. az storage account create --name <name> --resource-group <rg> --location <region> --sku Standard_LRS

  • az storage container create --name logs --account-name <account> --auth-mode login
  • azcopy copy ./logs "https://<account>.blob.core.windows.net/logs?<sas>" --recursive

Storage questions often hide the real issue in the access path. A SAS can grant permission, but it does not automatically bypass a storage firewall. An account key can be powerful, but a requirement for least privilege may point toward a SAS, stored access policy, managed identity, or Azure RBAC data role.

Compute checklist

Deploy a VM from the portal and from a template. Change VM size, attach a data disk, enable encryption at host when required, configure availability zones or availability sets, and test Bastion access. Create a VM Scale Set and observe scaling behavior. For platform compute, create an App Service plan, deploy a web app, configure TLS and custom DNS, create a deployment slot, swap slots, and configure backup. For containers, push an image to Azure Container Registry and run it through Azure Container Instances or Azure Container Apps. az deployment group create --resource-group <rg> --template-file main.bicep --parameters main.bicepparam

az vm resize --resource-group <rg> --name vm1 --size Standard_D4s_v5

az acr build --registry <acrName> --image web:v1 .

Template review is a high-value final exercise. Read parameters, variables, resource dependencies, copy loops, outputs, and scope. If the task says modify the template, know whether the change belongs in the resource body, a parameter, a module, or the deployment command.

Networking and monitoring checklist

Create a VNet, subnets, NSGs, ASGs, route tables, public IPs, load balancers, private endpoints, and DNS zones. Peer VNets and test whether traffic flows as expected. Use effective security rules and effective routes before guessing. For monitoring, create diagnostic settings, send logs to a Log Analytics workspace, write a simple KQL query, configure metric and log alerts, attach an action group, and suppress noise with an alert processing rule when appropriate. az network nic list-effective-nsg --resource-group <rg> --name <nic>

  • az network nic show-effective-route-table --resource-group <rg> --name <nic>
  • az monitor metrics list --resource <resourceId> --metric "Percentage CPU"

Close every lab with cleanup and reflection. Delete test resources, confirm backup vault retention decisions before deletion, and record one command or portal path you had to look up. The goal is not to memorize every parameter. The goal is to recognize the command family, the required scope, and the evidence that proves the administrator decision was correct.