AZ-305 Study Planner
A week-by-week study plan for the AZ-305 exam: 2-week, 4-week, and 8-week schedules.
How to use this planner
AZ-305 is an expert exam: it tests design judgement, not recall. Every plan below assumes you already hold AZ-104 (or have equivalent hands-on Azure administration experience). If you do not, complete AZ-104 first — AZ-305 assumes that knowledge. All three plans mix study guides, hands-on labs, and practice questions; the labs matter as much as the reading, because the exam rewards people who have actually built and broken Azure solutions.
The 2-week sprint (for experienced Azure architects)
For candidates with two or more years of Azure architecture experience who need a focused refresher. Days 1–3: Identity, governance, and monitoring (guides 1–4) — focus on Conditional Access design, hybrid identity choices, and RBAC data-plane distinctions. Days 4–6: Data storage (guides 5–7) — SQL tiers and failover groups, Cosmos DB partition keys and consistency, blob tiers and redundancy. Days 7–8: Business continuity (guides 8–9) — RPO/RTO-driven design, backup vs Site Recovery, availability zones and composite SLAs. Days 9–12: Infrastructure (guides 10–14) — the largest domain; prioritise the compute decision tree, the load-balancing matrix, and network connectivity. Days 13–14: Take the 50-question mock test under timed conditions, review every wrong answer against its guide, and re-read the cheat sheet. Lab focus: build a hub-and-spoke network with a firewall, a SQL failover group, and a Front Door front end.
The 4-week plan (the recommended pace)
For working professionals studying 8–10 hours a week. Week 1 — Identity, governance, monitoring: guides 1–4, one per study session, with practice questions after each. Lab: configure Conditional Access with a break-glass account, set up PIM eligible assignments, and deploy a Log Analytics workspace with diagnostic settings. Week 2 — Data storage: guides 5–7. Lab: deploy Azure SQL Database with a failover group, a Cosmos DB container with a chosen partition key, and a storage account with lifecycle policies. Week 3 — Business continuity and infrastructure (part 1): guides 8–11. Lab: configure Azure Backup with soft delete, deploy a VM scale set across zones, and build a Service Bus topic with subscriptions. Week 4 — Infrastructure (part 2) and revision: guides 12–14, then the mock test, then targeted re-study of your weakest domains using the domain breakdown. Read the cheat sheet twice in the final three days.
The 8-week plan (for a thorough first attempt)
For candidates who want maximum confidence or who have less hands-on Azure experience. Weeks 1–2: Identity, governance, and monitoring (guides 1–4), with a full lab environment: Entra ID with hybrid identity concepts, a management-group hierarchy with policies, and a monitoring workspace. Weeks 3–4: Data storage (guides 5–7), with labs for each SQL tier, Cosmos DB consistency levels, and a data integration pipeline in Data Factory. Weeks 5–6: Business continuity and infrastructure (guides 8–12), with a disaster-recovery lab (Site Recovery test failover) and a compute comparison lab (App Service vs Container Apps vs Functions for the same workload). Week 7: Networking and migrations (guides 13–14), with a hub-and-spoke lab and a migration assessment using Azure Migrate on a test VM. Week 8: Mock test, weak-domain re-study, cheat sheet, and a second mock attempt. Take the exam in week 8 or 9 while the material is fresh.
Study tips that actually help
Read the scenario constraint first. In case-study questions, the deciding fact is usually one sentence: the RPO, the budget, the compliance rule, the team size. Find it before reading the options. Eliminate by requirement. Most AZ-305 options are plausible services; the wrong ones fail one stated requirement. Check each option against each requirement. Lab the decision points. You will remember the Front Door vs Traffic Manager distinction far better after configuring both than after reading about them twice. Time yourself. 100 minutes for 40–60 questions means roughly two minutes per question, and case studies take longer — practice finishing the mock test with time to spare. Do not cram the night before. Read the cheat sheet, review your missed questions, and rest.
Exam week checklist
Seven days out: take your final mock test, review every wrong answer, and note the domains where you are weakest. Five days out: re-read the cheat sheet and your weakest guides; do not start new topics. Three days out: confirm your exam booking, test-centre location (or online system check), and identification documents. One day out: light review only — the cheat sheet and your missed-questions list — then rest. Exam day: arrive early, read each case study carefully, watch the clock (aim to finish with 10 minutes to spare for flagged questions), and answer every question. If you fail, the score report shows your weak domains: study those for two weeks and retake — the 24-hour minimum wait applies only after the first attempt, and most second-attempt candidates pass.
A daily study routine that works
Consistency beats intensity. A sustainable routine is 60–90 minutes a day, five days a week: 30 minutes reading one guide section, 20 minutes answering its practice questions and reading every explanation, and 20–30 minutes in the lab building what you just read about. Reserve one longer weekend session (2–3 hours) for the week's lab project — a hub-and-spoke network, a failover group, a containerised deployment. Keep a running list of concepts you got wrong and review it weekly; the list shrinks fast, and what remains is your personal exam syllabus. Study with the official Microsoft Learn documentation open alongside this site: when a guide mentions a service, read its Learn overview for five minutes. That habit builds the breadth the exam rewards and the familiarity with Microsoft's own terminology that helps you parse its questions.
Study with others
Studying alone works, but studying with others works better for an exam like AZ-305. A study partner or small group gives you someone to argue design trade-offs with — and arguing is exactly how design judgement forms. Explain your answer to each practice question out loud before reading the explanation; if you cannot defend it, you do not understand it yet. Online communities (the Microsoft Learn forums, Reddit's Azure certification community, and local user groups) are good places to find study partners and to ask questions when a concept refuses to click. Teaching is the fastest way to learn: if you can explain Front Door versus Traffic Manager to a colleague, you know it well enough for the exam.