AZ-305: Designing Microsoft Azure Infrastructure Solutions

Passing AZ-305 (plus holding AZ-104) earns the Azure Solutions Architect Expert certification. The exam is design-oriented: given business/technical requirements, choose the best Azure service and configuration — across identity/governance, storage, business continuity, and infrastructure. Heavy on case studies.

~40–60 questions ~100–120 min pass 700/1000 $165 USD AZ-104 prereq (for cert)
⚡ Open the 1-page Cram Jam sheet

Part 1 — High-Level Overview

What & Why

AZ-305 validates your ability to design solutions on Azure that meet requirements — it's the architect-level companion to the administrator-level AZ-104. You won't be clicking through the portal; you'll be reading a scenario and picking the right service, tier, and topology. The mental model is Microsoft's Well-Architected Framework (WAF) and Cloud Adoption Framework (CAF).

Cert requirement The Azure Solutions Architect Expert certification requires both AZ-104 (Administrator) and passing AZ-305. You can sit AZ-305 first, but the Expert cert isn't awarded until AZ-104 is earned — and AZ-104's knowledge is assumed. Detail in §1.

Exam at a Glance

AttributeValue
Exam codeAZ-305 (Designing Microsoft Azure Infrastructure Solutions)
Questions~40–60 (not officially published), incl. a case-study block of ~6–8
Question typesMultiple choice, case studies, drag-and-drop/build-list, hot area, dropdown, yes/no repeated-answer series
Time~100–120 min answering (~140 min appointment)
Passing score700 / 1000 (scaled — not a raw 70%)
Cost$165 USD
Validity1 year — renew free via an online assessment on Microsoft Learn

→ Deep dive: §1 Exam Details & Case Studies

The 4 Domains

Infrastructure (30–35%) is the biggest, closely followed by Identity/Governance/Monitoring (25–30%). Data storage and business continuity round it out.

25–30%
Identity, Governance & Monitoring
20–25%
Data Storage Solutions
15–20%
Business Continuity
30–35%
Infrastructure Solutions
DomainWhat it testsDeep dive
1 · Identity/Gov/Monitor 25–30%Entra ID auth, RBAC, management-group/subscription hierarchy, Azure Policy, Key Vault, logging/Monitor.→ §3
2 · Data Storage 20–25%Blob/Files/Disk, Azure SQL vs MI vs SQL-on-VM, Cosmos DB APIs & consistency, data integration.→ §4
3 · Business Continuity 15–20%Backup vs Site Recovery, HA for compute/data, RTO/RPO.→ §5
4 · Infrastructure 30–35%Compute/app hosting, networking & load balancing, messaging/event architectures, migration (CAF).→ §6

Service Snapshot

Identity & Governance

Entra ID (P1/P2), RBAC, Management Groups, Azure Policy, Blueprints, Key Vault, PIM, Conditional Access. →

Storage

Blob (Hot/Cool/Cold/Archive), Files, Managed Disks, ADLS Gen2, LRS/ZRS/GRS/GZRS. →

Databases

Azure SQL DB, SQL Managed Instance, SQL on VM, Cosmos DB, Azure Database for MySQL/PostgreSQL. →

Compute

VMs, App Service, AKS, Container Apps, Functions, Batch, ACI, VM Scale Sets. →

Networking

VNet, Load Balancer, App Gateway, Front Door, Traffic Manager, VPN Gateway, ExpressRoute. →

Continuity & Integration

Azure Backup, Site Recovery, Availability Zones/Sets; Service Bus, Event Grid, Event Hubs. →

Recommended Materials (community consensus)

The consensus stack: earn/refresh AZ-104 first → one structured course (Scott Duffy Udemy or Microsoft Learn paths) → John Savill's free AZ-305 Study Cram to connect the dots (re-watch 24–48h before) → practice exams (MeasureUp official and/or Tutorials Dojo) to 80%+ → deep-dive weak spots in Microsoft Learn docs. Avoid dumps.

→ Full breakdown with sources (§8)

Study Plan (Quick Version)

  1. Foundation: AZ-104 knowledge is assumed — shore it up first.
  2. Learn the decisions: one course + Savill's cram; focus on "which service for these requirements."
  3. Active recall: build decision trees (Blob/Files/Disk; LB/AppGw/FrontDoor/TM; Backup/ASR) from memory.
  4. Practice: drill case-study technique + practice exams to consistent 80%+; re-watch Savill's cram right before.

→ Detailed retention-based plan (§9) · ⚡ Cram Jam

Part 2 — Thorough Study Guide

1 · Exam Details & Case Studies

  • Passing score is 700/1000, a scaled score — not "70% of questions right." Sections are weighted.
  • Question count is not officially published; recent candidates report ~49–54, in ~100–120 minutes of answering time.
  • Question formats: standard multiple choice, case studies, drag-and-drop / build-list ordering, hot area, dropdown, and yes/no repeated-answer series ("does this solution meet the goal?" — the same scenario asked 3 ways, each independent).
  • Renewal: the cert expires after 1 year but renews free via an unproctored online assessment on Microsoft Learn (available 6 months before expiry).

Case-study technique (heavily repeated by passers)

  • A case study is a scenario with tabs: Overview, Business Requirements, Technical Requirements, Existing Environment, then ~6–8 questions.
  • Read the question first, then scan the tabs hunting for constraint keywords — RTO, RPO, cost, region/data-sovereignty, compliance, latency, availability %. Those constraints usually determine the single "best" answer among several that would technically work.
  • Watch out: in some formats you cannot return to a case study once you finish its block and move on — don't rush past it.
  • Use the official exam sandbox (aka.ms/examdemo) beforehand so the drag-and-drop/hot-area UI isn't new on the day.
Mindset trap AZ-305 is not AZ-104. It tests design decisions ("which service, which tier, which topology"), not portal/CLI procedures. Several answers will "work"; the requirements pick the best one.

2 · Well-Architected & Cloud Adoption Frameworks

Every AZ-305 answer is graded against Microsoft's frameworks. Know them as the "why" behind the right choice.

FrameworkPurpose
Well-Architected Framework (WAF)Five pillars for good workloads: Reliability, Security, Cost Optimization, Operational Excellence, Performance Efficiency.
Cloud Adoption Framework (CAF)End-to-end cloud journey: Strategy → Plan → Ready (landing zones) → Adopt (Migrate/Innovate) → Govern → Manage → Secure. Migration questions map here.

Migration "R" strategies: Rehost (lift-and-shift), Refactor, Rearchitect, Rebuild (and Replace). Assess with Azure Migrate.

3 · Identity, Governance & Monitoring 25–30%

3.1 · Identity — Microsoft Entra ID

  • Microsoft Entra ID (formerly Azure AD) is Azure's cloud identity provider. Tiers: Free / P1 / P2.
  • P1 adds Conditional Access, dynamic groups, self-service password reset writeback, and hybrid identity features. P2 adds Identity Protection, Privileged Identity Management (PIM), Access Reviews, and entitlement management.
  • Hybrid identity sync (Entra Connect): Password Hash Sync (simplest), Pass-through Authentication, or Federation (AD FS).
  • Authorization: use RBAC to grant least-privilege access to Azure resources; use Conditional Access for context-aware sign-in (MFA, device/location, risk).
  • Built-in RBAC roles: Owner (everything incl. granting access), Contributor (everything except granting access), Reader, User Access Administrator (only grants access). Assign at the narrowest useful scope (mgmt group / subscription / RG / resource); create custom roles only when built-ins don't fit.
  • Managed identities — let Azure resources authenticate to other services (Key Vault, storage, SQL) without any stored credentials. System-assigned = tied 1:1 to the resource's lifecycle; user-assigned = standalone, shareable across many resources. The default answer to "app needs to access X securely without secrets."
  • PIM (P2) — just-in-time, time-boxed, approval-gated elevation for privileged roles, with audit trail. The answer to "admins should have standing access to nothing."
  • B2B (guest collaboration into your tenant) vs B2C (customer-facing identity for your apps). Entra Domain Services = managed AD DS domain (Kerberos/NTLM/LDAP) for legacy apps that need domain-join without on-prem DCs.

3.2 · Governance

  • Hierarchy (top→bottom): Management Groups → Subscriptions → Resource Groups → Resources. Apply policy/RBAC at the right scope; children inherit.
  • Azure Policy — enforce/audit rules (allowed regions/SKUs, required tags, enforce encryption). Initiatives group policies. Effects: Deny, Audit, Append, DeployIfNotExists.
  • RBAC vs Policy: RBAC = who can do what; Policy = what resources/config are allowed. Different questions, don't conflate.
  • Resource locks (CanNotDelete / ReadOnly) and tags (cost/organization). Azure Blueprints package policies/RBAC/templates for repeatable environments.
  • Azure Key Vault — store secrets, keys, certificates (Standard vs Premium/HSM-backed). Use managed identities so apps fetch secrets without credentials. Enable soft-delete + purge protection so keys/secrets can't be permanently destroyed (required before using customer-managed keys for many services).
  • Tags are not inherited by default (use Azure Policy to enforce/append them); locks and policy assignments do inherit down the hierarchy.
  • Microsoft Defender for Cloud — cloud security posture management (secure score, recommendations) + workload protection plans. "Assess/improve overall security posture" → Defender for Cloud, not Sentinel.

3.3 · Monitoring

  • Azure Monitor is the umbrella — Metrics (fast, numeric, near-real-time alerting) and Logs (rich, queryable with KQL in a Log Analytics workspace).
  • Application Insights for app telemetry/APM — request rates, dependencies, failures, availability (URL ping) tests, distributed tracing.
  • Diagnostic settings route resource logs/metrics to Log Analytics (analysis), a Storage Account (cheap archive), or Event Hubs (stream to an external SIEM) — that trio is a recurring answer set.
  • Workspace design: a centralized workspace simplifies cross-resource queries & RBAC; use resource-context access to scope who sees what. Set retention per table to balance cost.
  • Alerts + Action Groups for notification/automation. Microsoft Sentinel = cloud SIEM/SOAR built on Log Analytics (threat detection/hunting/response — a different job than Defender for Cloud's posture management).
  • Network Watcher — packet capture, NSG flow logs, connection troubleshooting for network diagnostics.

4 · Data Storage Solutions 20–25%

4.1 · Storage accounts

TypeUse for
BlobObject/unstructured (images, logs, backups); data lake via ADLS Gen2 (hierarchical namespace).
Azure FilesManaged SMB/NFS file share; lift-and-shift shared drives / cloud file server (+ Azure File Sync for hybrid).
Managed DisksBlock storage attached to a single VM (OS/data disks).
Queue / TableSimple message store / NoSQL key-value.
  • Blob access tiers: Hot → Cool → Cold → Archive (Archive = cheapest storage, but rehydration latency + retrieval cost). Lifecycle management auto-tiers.
  • Redundancy (cheapest→most resilient): LRS (1 datacenter) → ZRS (across zones) → GRS (paired region, async) → GZRS (zones + region). RA-GRS/RA-GZRS add read access to the secondary.
  • Authorizing storage access (a favorite): Entra ID + RBAC = best for apps/users (identities, auditable) · SAS tokens = scoped, time-limited delegated access for external parties (prefer user-delegation SAS, backed by Entra) · account keys = full-account god-mode, avoid handing out. "Grant a partner temporary access to one container" → SAS.
  • Immutable storage — time-based retention or legal hold WORM policies on blob containers for compliance ("data must not be modified or deleted for N years").
  • Private Endpoints give the storage account a private IP in your VNet (public access can be disabled) — the default answer for "storage must not be reachable from the internet."
  • Azure Files extras: identity-based SMB auth via AD DS / Entra Domain Services; Azure File Sync caches shares on on-prem Windows servers (cloud tiering). Azure NetApp Files = high-performance NFS/SMB for demanding workloads (SAP, HPC) when Files/managed disks can't hit the IOPS/latency target.

4.2 · Relational databases

OptionBest for
Azure SQL DatabaseNew cloud apps; fully PaaS (single DB or elastic pool); no OS/instance access; most managed.
SQL Managed InstanceLift-and-shift — near-100% SQL Server compatibility (SQL Agent, cross-DB queries, CLR); VNet support.
SQL Server on a VM (IaaS)Full OS + instance control; unsupported/legacy features; you patch & manage.
Azure DB for MySQL / PostgreSQLManaged open-source engines.
  • Purchasing: DTU vs vCore. vCore tiers: General Purpose, Business Critical (local SSD + built-in HA replica, lowest latency, free readable secondary), Hyperscale (up to 100 TB, fast scale/restore). Serverless auto-pauses for intermittent load — pay only when active.
  • Elastic pools — many databases with variable, non-overlapping usage share one pool of resources; the answer to "dozens of small DBs with spiky individual load."
  • HA/scale: zone-redundant deployment; active geo-replication (readable secondaries, per-DB) vs auto-failover groups (group failover + a stable listener endpoint — apps don't change connection strings); read scale-out.
  • SQL security stack (asked as "which feature?"): TDE = encryption at rest (on by default) · Always Encrypted = client-side encryption, even DBAs can't read values · Dynamic Data Masking = hides values in query results (display-level, not encryption) · row-level security · auditing → Log Analytics.

4.3 · Cosmos DB & NoSQL

  • Azure Cosmos DB — globally distributed, multi-model, single-digit-ms latency, elastic. APIs: NoSQL (Core), MongoDB, Cassandra, Gremlin (graph), Table. Pick the API to match an existing app/driver.
  • 5 consistency levels (strongest→weakest): Strong → Bounded Staleness → Session (default) → Consistent Prefix → Eventual. Stronger = more latency/cost; weaker = faster.
  • Multi-region writes + global distribution for low-latency global apps.
  • Capacity: billed in Request Units (RUs) — provisioned (steady), autoscale (variable, scales 10× band), or serverless (sporadic). A good partition key (high cardinality, even access) is the #1 design lever — hot partitions throttle.
  • Change feed streams item changes in order — drives event-driven downstream processing (Functions triggers, materialized views).

4.4 · Data Integration & Analytics

ServiceUse for
Azure Data FactoryETL/ELT orchestration — pipelines that move & transform data on schedules/triggers (the Azure "data pipeline" answer).
Azure Synapse AnalyticsData warehousing + big-data analytics — dedicated or serverless SQL pools + Spark, integrated workspace.
Azure DatabricksManaged Apache Spark — advanced analytics, ML, when the team already uses Spark/notebooks.
Azure Stream AnalyticsReal-time SQL-like queries over streams (pairs with Event Hubs/IoT Hub).
ADLS Gen2The data-lake storage layer (hierarchical namespace on Blob) all of these read/write.
Power BIDashboards & visualization on top.

Pattern to recognize: ingest (Event Hubs / Data Factory) → store (ADLS Gen2) → process (Synapse / Databricks / Stream Analytics) → serve (SQL / Power BI).

5 · Business Continuity 15–20%

NeedService
Backup / point-in-time restore (data protection, RPO)Azure Backup (Recovery Services vault) — VMs, files, SQL, etc.
Disaster recovery / regional failover (RTO, near-zero data loss)Azure Site Recovery (ASR) — replicate + orchestrated failover.
  • RTO = how fast you must recover; RPO = how much data loss is acceptable. Case-study answers hinge on these words.
  • HA building blocks: Availability Sets (fault + update domains, single datacenter, 99.95%) vs Availability Zones (physically separate datacenters in a region, 99.99%) vs Region pairs (cross-region DR). VM Scale Sets for autoscaling identical VMs.
  • Data HA: zone-redundant storage (ZRS/GZRS), SQL geo-replication/failover groups, Cosmos multi-region.
  • Azure Backup detail: Recovery Services vault with GRS by default (enable cross-region restore to restore in the paired region); soft delete keeps deleted backups 14 days; immutable vaults / MUA protect backups from ransomware & rogue admins; supports VMs, Files, SQL/SAP in VMs, on-prem via MARS/Azure Backup Server.
  • SQL PaaS backups: automatic point-in-time restore (default up to 35 days) + long-term retention (LTR) for up to 10 years — don't design VM-style backup for Azure SQL.
  • Multi-region app failover: put Front Door (HTTP) or Traffic Manager (DNS) in front of two regional deployments — active/active or active/passive with priority routing + health probes.
  • Composite SLA: chained dependencies multiply availability (99.95% × 99.99% < either alone); parallel independent paths raise it. Case studies that state a required "%" are steering you toward zones (99.99%) or multi-region.
Backup vs Site Recovery Backup = keep restorable copies (protects against corruption/deletion; RPO). Site Recovery = replicate a running workload and fail it over to another region fast (RTO). They solve different problems and are often used together.

6 · Infrastructure Solutions 30–35% — biggest

6.1 · Compute & app hosting

ServiceUse for
Virtual MachinesFull control / IaaS / legacy lift-and-shift.
App ServiceManaged web apps/APIs — easiest PaaS hosting.
AKSFull Kubernetes for complex microservices needing orchestration control.
Container AppsServerless containers/microservices with KEDA event scaling — no K8s to manage.
Azure FunctionsEvent-driven, short-lived, per-execution serverless.
Container Instances (ACI)Simplest single-container / burst.
BatchLarge-scale parallel/HPC batch jobs.
  • App Service plans: Free/Basic (dev) → Standard (autoscale, slots) → Premium (more scale, VNet integration) → Isolated / App Service Environment (dedicated, fully VNet-injected — the "compliance demands network isolation" answer). Deployment slots enable zero-downtime blue/green swaps.
  • Functions hosting plans: Consumption (pure pay-per-execution, ~5–10 min cap, cold starts) · Premium (pre-warmed instances = no cold start, VNet access, longer runs) · Dedicated (run on an App Service plan you already own). "Serverless but no cold starts + VNet" → Premium.
  • Decision drivers: control ↔ management burden. VM (most control) → AKS → Container Apps / App Service → Functions (least). Case studies pick by: containerized? needs K8s APIs? event-driven? team ops maturity? compliance isolation?

6.2 · Networking & load balancing

Memorize the Layer × Scope 2×2 — the most-tested networking decision:

RegionalGlobal
Layer 4 (TCP/UDP)Azure Load BalancerTraffic Manager (DNS-based routing)
Layer 7 (HTTP/S)Application Gateway (URL routing, WAF, SSL offload)Azure Front Door (global HTTP LB + CDN + WAF)
  • Hybrid connectivity: VPN Gateway (encrypted over internet; cheaper; site-to-site / point-to-site) vs ExpressRoute (private dedicated circuit, higher bandwidth/SLA, predictable latency, bypasses public internet). Combine ExpressRoute + VPN for failover. ExpressRoute traffic is not encrypted by default.
  • NSG = subnet/NIC-level allow/deny rules; Application Security Groups (ASGs) tag VMs by role so NSG rules read "web-asg → db-asg" instead of IP lists; Azure Firewall = central, stateful, FQDN-aware firewall for the hub (a different layer than NSGs — use both).
  • Private Endpoint vs Service Endpoint (heavily tested): Private Endpoint gives the PaaS service a private IP in your VNet — reachable from on-prem via VPN/ER, public access can be fully disabled. Service Endpoint keeps the service's public endpoint but routes your VNet's traffic over the backbone and scopes the firewall to your subnet — no private IP, not reachable from on-prem. "Completely remove public exposure" → Private Endpoint.
  • Hub-spoke topology: peering is non-transitive, so spokes talk through a hub (Azure Firewall/NVA + gateways in the hub, workloads in spokes) with UDRs steering traffic. Azure Bastion = browser-based RDP/SSH without public IPs on VMs. NAT Gateway for scalable, predictable outbound egress. Private DNS zones resolve private endpoints; link them to VNets.

6.3 · Messaging & application architecture

ServiceUse for
Service BusEnterprise messaging — queues/topics, ordering (FIFO), transactions, dead-letter.
Event GridReactive routing of discrete events (e.g. blob created) to handlers.
Event HubsHigh-throughput streaming/telemetry ingestion (big data, IoT).
Storage QueuesSimple, large-volume queueing.
Events vs messages An event is a lightweight notification that something happened (consumer decides what to do) → Event Grid (discrete) / Event Hubs (streams). A message is data the producer expects to be processed, often with ordering/transactions → Service Bus. That one distinction answers most integration questions.
  • Caching: Azure Cache for Redis (sessions, DB offload). API Management — publish/secure/throttle/version APIs behind one gateway. Logic Apps — low-code workflow integration with hundreds of connectors ("automate this business process across SaaS/systems"). App Configuration + Key Vault for centralized settings/feature flags.
  • Queue-based load leveling: put Service Bus/queues between spiky producers and slower consumers so bursts don't topple the backend — the resiliency pattern case studies fish for.
  • Automated deployment: ARM templates / Bicep (declarative IaC; Bicep is the friendlier DSL) via Azure DevOps Pipelines or GitHub Actions; Template Specs to share approved templates.

6.4 · Migration

  • Azure Migrate — the central hub: discovery appliance → assessment (readiness, right-sizing, cost estimate) → migration tooling for servers/databases/web apps/VDI.
  • Database Migration Service (DMS) — offline (downtime during cutover) vs online (continuous sync, minimal downtime) migrations; pair with SQL assessments (Data Migration Assistant heritage) for compatibility checks.
  • Moving bulk data: network (AzCopy, Storage Mover, Data Factory) when bandwidth allows; Data Box family (~8 TB Disk / ~80 TB Data Box / ~800 TB+ Heavy, shipped appliances) when it doesn't.
  • Frame with the CAF and the "R" strategies (rehost/refactor/rearchitect/rebuild/replace).

7 · Decision Tables

Storage

NeedChoose
Object/unstructured, data lakeBlob / ADLS Gen2
Shared file drive (SMB)Azure Files
Disk for one VMManaged Disk
Cheapest archiveBlob Archive tier
Survive a region lossGRS / GZRS

Relational vs NoSQL

NeedChoose
New cloud relational appAzure SQL Database
Lift-and-shift SQL Server (full compat)SQL Managed Instance
OS/instance control, legacy featuresSQL on a VM
Global, low-latency, flexible schemaCosmos DB
MongoDB/Cassandra app to AzureCosmos DB (matching API)

Networking

NeedChoose
L7 URL routing + WAF, one regionApplication Gateway
Global HTTP LB + CDN + WAFFront Door
L4 TCP/UDP, one regionLoad Balancer
DNS-based global routingTraffic Manager
Private, dedicated on-prem linkExpressRoute
Encrypted tunnel over internetVPN Gateway

Compute

NeedChoose
Managed web app, least effortApp Service
Full K8s controlAKS
Serverless microservices, no K8sContainer Apps
Event-driven short functionsAzure Functions
Full OS control / legacyVirtual Machines

8 · Study Materials (community consensus)

Averaged across r/AzureCertification & r/Azure "passed AZ-305" threads and community study plans. The dominant pattern: one course + John Savill's free cram + a quality practice-exam bank + Microsoft Learn deep-dives.

1 · Video courses

ResourceWhy
#1John Savill's YouTube (free)Mentioned in essentially every pass thread. Watch the AZ-305 Study Cram (~3h) early and again 1–2 days before; go deeper with his AZ-305 playlist and Azure Master Class. Free whiteboards/notes on GitHub (johnthebrit/CertificationMaterials).
Scott Duffy (Udemy)Most-recommended paid, structured course — a linear curriculum. Caveat: "good but low-energy."
Alan Rodrigues / Thomas Mitchell (Udemy)Alan includes hands-on labs; both are solid alternatives.
Microsoft Learn paths (free/official)Authoritative but text-heavy — best as reference/deep-dive, not sole primary course.

2 · Practice exams

Drive a practice bank to 80%+ before booking. Top picks: MeasureUp (the official Microsoft practice test) and Tutorials Dojo (Jon Bonso) — which now has an AZ-305 bank (155+ Q, timed/review/final modes, free 20-Q sampler) with strong explanations. Whizlabs is mixed (some outdated). Use the Microsoft Learn free Practice Assessment as a baseline. Caveat practice tests skew easier than the real exam and heavy on Entra ID — use them to find weak spots, not as a pass predictor.

3 · Hands-on & free

  • Free Azure account ($200 credit / 30 days) + Microsoft Learn sandbox modules. AZ-305 is design-heavy so hands-on matters less than for AZ-104 — but AZ-104's hands-on foundation is assumed.
  • Azure Architecture Center (learn.microsoft.com/azure/architecture/browse) — reference patterns; great for "which pattern" reasoning.
  • WAF + CAF docs — the mental model the exam grades against.
  • Exam sandbox (aka.ms/examdemo) — practice the UI.

4 · Notes / cheat sheets

  • No single book dominates. The de-facto cheat sheet is John Savill's AZ-305 whiteboard PDFs (GitHub). Keep your own decision-tree notes (Blob/Files/Disk, LB/AppGw/FrontDoor/TM, Backup/ASR) — that's exactly this guide's Cram Jam.

Sources

9 · Study Plan (Retention-Based, ≈3–6 weeks after AZ-104)

AZ-305 rewards understanding trade-offs, not memorizing facts — so lean hard on active recall and elaboration. Reproducing decision trees from memory and explaining why a service fits a constraint is exactly what the case studies test.

PrincipleHow to apply it to AZ-305
Active recallAfter each domain, redraw its decision tree (e.g. SQL DB vs MI vs VM) from a blank page; self-quiz on tiers & SKUs.
Spaced repetitionFlashcard the "which service" pairs and consistency levels/redundancy tiers; review daily at growing intervals.
Elaboration (Feynman)Explain out loud why ExpressRoute beats VPN here, or Backup vs ASR there. Tie every choice to a WAF pillar.
InterleavingMix domains in practice; case studies deliberately blend identity + storage + network + continuity.
Concrete practiceDo case-study-style questions early; the format is the hard part as much as the content.
PhaseFocusActions
Week 0FoundationConfirm AZ-104-level knowledge (VNets, storage, identity, VMs). Fill gaps before starting AZ-305 design content.
Week 1–2Course + framingWork a structured course (Scott Duffy / MS Learn). Watch Savill's Study Cram once to connect the dots. Build decision trees as you go.
Week 3Depth on biggest domainsDeep-dive Infrastructure (30–35%) & Identity/Gov (25–30%). Teach each decision out loud; read Architecture Center patterns.
Week 4Practice + case studiesMeasureUp / Tutorials Dojo in review mode; practice the case-study "read question first, hunt constraints" technique. Re-study weak areas.
Week 5Consistency + taperFresh sets to consistent 80%+. Re-watch Savill's cram 24–48h before. Do the exam sandbox. Sleep well.

Reported times: ~1 week (experienced, MS Learn + Savill) to ~1 month at a few hrs/day after AZ-104; ~100 total hours if newer.

Readiness bar You're ready when you can, from memory, pick the right service for a given constraint set and justify it against a WAF pillar — and you're consistently 80%+ on fresh practice sets.

10 · Tips & Common Traps

  • It's a design exam. Multiple answers "work" — the constraints (RTO/RPO, cost, region/compliance, latency, HA%) pick the best one. Hunt those keywords.
  • Case studies: read the question first, then the tabs. You may not be able to return to a case-study block — don't rush it.
  • Backup vs Site Recovery — restore copies (RPO) vs region failover (RTO).
  • SQL DB vs Managed Instance vs SQL-on-VM — PaaS-new vs lift-and-shift-compat vs full-control.
  • LB vs App Gateway vs Front Door vs Traffic Manager — L4/L7 × regional/global.
  • VPN vs ExpressRoute — internet-encrypted vs private-dedicated.
  • Entra ID P1 vs P2 — P2 adds PIM, Identity Protection, Access Reviews.
  • Availability Set (99.95%, one DC) vs Zone (99.99%, separate DCs).
  • Cosmos consistency: Strong→Bounded→Session(default)→Consistent Prefix→Eventual.
  • Storage redundancy: LRS < ZRS < GRS < GZRS.
  • Know tiers/SKUs — questions hinge on feature differences between tiers.
Ignore Exam dumps (ExamTopics "discussions", DumpsGate, etc.) — often outdated/wrong, violate the NDA, and can void your cert. Legit practice tests (MeasureUp, Tutorials Dojo, Whizlabs) teach reasoning and are fine; dumps just leak stolen answers.

↑ back to top