11.1 Final Two-Week Study Plan

The final two-week strategy

The last two weeks before AZ-104 are not for rebuilding your study plan from zero. They are for converting loose knowledge into reliable administrator behavior. Use the April 17, 2026 skills outline as the map: manage Azure identities and governance is 20-25 percent, implement and manage storage is 15-20 percent, deploy and manage compute is 20-25 percent, implement and manage virtual networking is 15-20 percent, and monitor and maintain resources is 10-15 percent.

Do not give every domain the same amount of time unless your diagnostic results justify it. Identity and governance and compute deserve large review blocks because they are high-weight domains and because they appear inside many mixed scenarios. Storage and networking are also central. Monitoring has the smallest stated range, but it often turns a resource configuration question into an operations question.

Start with a diagnostic set that mixes all domains. Mark each answer as correct, wrong, or guessed. A guessed correct answer is still a gap. For every miss, write the root cause as one of five labels: did not know service behavior, confused two services, missed a requirement word, lacked command or portal recall, or ran out of time. This turns a practice score into a repair plan.

Domain repair blocks

For identity and governance, practice users, groups, external users, self-service password reset, built-in role selection, role assignment scope, Azure Policy, resource locks, tags, management groups, subscriptions, budgets, cost alerts, and Advisor recommendations. Do not study RBAC as a list of role names only. Practice reading a scenario and deciding whether the correct scope is management group, subscription, resource group, or resource.

For storage, rotate through storage account redundancy, account kind, Blob containers, Azure Files shares, snapshots, soft delete, versioning, lifecycle rules, access tiers, access keys, SAS, stored access policies, firewalls, virtual networks, private endpoints, AzCopy, and Storage Explorer. A storage miss often comes from mixing authentication, authorization, network access, and data protection.

For compute, practice ARM and Bicep interpretation, deployment commands, VM sizing, disks, encryption at host, availability sets, availability zones, VM Scale Sets, Azure Container Registry, Azure Container Instances, Azure Container Apps, App Service plans, custom domains, TLS, deployment slots, scaling, backups, and app networking. If you cannot explain the deployment result from a template fragment, spend time there before memorizing more portal labels.

For networking, rebuild the flow from source to destination. Check subnet, NIC, NSG, application security group, route table, public IP, load balancer, DNS, peering, service endpoint, private endpoint, Bastion, and Network Watcher evidence. Many wrong answers come from skipping effective security rules or from treating VNet peering as transitive routing by default.

For monitoring and maintenance, practice Azure Monitor metrics, logs, diagnostic settings, Log Analytics queries, alert rules, action groups, alert processing rules, VM insights, storage insights, network insights, Connection Monitor, Recovery Services vaults, Azure Backup vaults, backup policies, restore, Azure Site Recovery, secondary-region failover, reports, and backup alerts. Know whether the question asks for detection, notification, suppression, analysis, backup, or recovery.

Daily structure

A useful final-week session has four parts. First, spend 20 minutes reviewing missed facts from yesterday. Second, spend 60-90 minutes doing hands-on tasks or reading portal paths and commands. Third, do a timed mixed quiz. Fourth, write a repair note for each miss. Do not let passive video time replace repair notes.

A repair note should be short and operational. Example: Storage account firewall blocks public network access unless selected networks, trusted services, or private endpoint path is allowed. SAS permission does not bypass network rules. Another example: Unscheduled breaks do not stop the exam clock and prevent return to previously seen questions. These notes are the material you review during the final 48 hours.

Pacing without false assumptions

Microsoft says most Microsoft Certification exams typically contain 40-60 questions, but the number can vary. Do not build a plan that assumes an exact item count. The AZ-104 assessment time listed in the source brief is 100 minutes, and role-based exam seat duration can include non-question time. The delivered exam may include interactive components, and labs may be present or removed at any time.

Use pacing ranges instead of fixed math. In a first pass, answer direct items quickly and mark uncertain items only when the interface allows review. Slow down for case studies, build-list questions, hot areas, drag/drop, or any screen that changes review behavior. Read the overview page at launch because it tells you how the delivered exam is organized.

Final 48 hours

The final 48 hours are for confidence through precision, not cramming. Review official logistics, your weak-domain notes, commands you repeatedly forget, and any Microsoft Learn pages you might need for targeted lookup. Microsoft Learn access on role-based exams is helpful, but no extra time is added, and it is restricted. It is not a replacement for knowing the administrator workflow.

Stop full-length practice early enough to sleep. On the final day, do a light pass over domain weights, common failure modes, and exam-day rules. Avoid new unofficial claims about pass rates, exact question counts, or guaranteed labs. The best final plan is boring in the right way: current facts, weighted study, hands-on repair, and calm pacing.