Study guide
11.4 Retake Plan, Score Report, and Weak-Domain Repair
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.4 Retake Plan, Score Report, and Weak-Domain Repair
Key Takeaways Explain This Topic AI
A score of 700 or greater is required to pass AZ-104, but the score report should be used as a repair map rather than a judgment of ability.
After a first failed attempt, Microsoft requires a 24-hour wait before retaking.
After subsequent failed attempts, a 14-day waiting period applies, up to five attempts within 12 months from the first attempt.
A passed exam cannot be retaken unless the certification has expired.
Retake preparation should rebuild weak workflows and missed requirement reading, not just repeat the same practice questions.
Last updated: May 2026
Turning a non-pass into a repair plan
AZ-104 uses a passing score of 700 or greater. Do not translate that into a simple percentage and do not compare yourself to a claimed public pass rate. Microsoft does not publish a public AZ-104 pass-rate percentage. If you do not pass, the useful output is not a label. The useful output is the score report, your memory of difficult scenarios, and the timing pressure you felt during the delivered exam.
Start the same day while the experience is still fresh. Write down the domains that felt hardest, the item types that slowed you down, and the requirements you remember misreading. Do not copy exam content or violate exam rules. Record categories instead: RBAC scope, storage firewall, VM scale, App Service slot, private endpoint DNS, effective routes, backup policy, alert rule, or Bicep dependency.
Signal What it may mean Repair action
Low identity and governance RBAC, policy, locks, tags, or cost scope confusion Rebuild access and governance labs at multiple scopes.
Low storage Mixed access, network, SAS, lifecycle, or protection gaps Practice end-to-end storage access and recovery scenarios.
Low compute VM, App Service, container, or template decision gaps Deploy and modify resources by portal, CLI, and Bicep.
Low networking Route, NSG, DNS, peering, endpoint, or load balancer gaps Use Network Watcher and effective rule evidence.
Low monitoring Alert, log, backup, restore, or failover confusion Configure signals and recovery workflows by hand.
Official retake timing
Microsoft retake policy is specific. If you do not pass the first time, you must wait 24 hours before retaking. A 14-day waiting period applies between all subsequent attempts, up to five attempts. You may not take a given exam more than five times within a 12-month period from the first attempt. A passed exam cannot be retaken unless the certification has expired. Retake fees apply when applicable.
This timing should shape your plan. A 24-hour minimum does not mean a retake the next day is wise. If your result was barely below 700 and you know the cause was pacing or one domain, a short repair cycle may be enough. If several domains were weak, schedule farther out and use the waiting period productively. A rushed retake often repeats the same failure pattern with a new fee.
The weak-domain repair loop
Use a four-step loop: diagnose, rebuild, prove, and retest. Diagnose with the score report and your notes. Rebuild with hands-on tasks, not only reading. Prove the fix with validation evidence. Retest with mixed timed questions. Repeat until missed questions are mostly edge cases rather than core workflows.
For identity and governance, rebuild from principal to scope. Create a user or group, assign a role at subscription, resource group, and resource scope, then test what changes. Apply a policy and observe deny or audit behavior. Add a lock and confirm that RBAC does not override it. Create budgets and cost alerts so cost management is not just a vocabulary topic.
For storage, rebuild from client to data. Decide whether the client uses account key, SAS, managed identity, Microsoft Entra authentication, or Azure RBAC data roles. Then decide whether the network path uses public access, selected networks, service endpoint, or private endpoint. Finally decide the protection layer: soft delete, versioning, snapshots, lifecycle management, redundancy, or backup where applicable.
For compute, rebuild from deployment to operation. Read a Bicep file, deploy it, inspect dependencies, resize a VM, attach a disk, configure availability, test Bastion, configure an App Service plan, create a deployment slot, swap it, and configure backup. If containers were weak, push to Azure Container Registry and compare Azure Container Instances with Azure Container Apps.
For networking, rebuild from packet path. Name the source, destination, subnet, NIC, NSG, route table, DNS name, endpoint type, and load balancer rule. Use effective security rules and effective routes to prove your answer. If you cannot explain why peering is not automatically transitive or why private endpoint DNS matters, repair that before retesting.
For monitoring and maintenance, rebuild from signal to response. Configure diagnostic settings, send logs to a workspace, write a simple KQL query, create a metric alert, create a log alert, attach an action group, and use alert processing rules when the scenario asks for suppression. Then practice backup policy, restore, vault selection, reports, alerts, and Site Recovery decision points.
Retake schedule examples
For a near pass with one weak domain, use three days: one day of focused rebuild, one day of mixed practice, and one day of light review and exam logistics. For a broad miss, use 10-14 days: two days for identity and governance, two for compute, two for storage and networking, one for monitoring and backup, then timed mixed sets and review. Match the schedule to the failure pattern, not to emotion.
During retake preparation, do not memorize only the same missed practice questions. That creates recognition without transfer. Instead, write variations. If the missed question involved a SAS token, create a version that changes network rules. If it involved an NSG, add a route table. If it involved backup, add soft delete or restore constraints.
A retake is not a restart. It is a targeted maintenance cycle on your own skill set. Respect the official waiting periods, pay attention to the score report, rebuild the weak workflows, and retest under realistic time pressure before scheduling again.