AZ-305 Complete Guide: Microsoft Azure Solutions Architect Expert Exam Scope, Resources & Strategy

Microsoft Certified: Azure Solutions Architect Expert (AZ-305) is the Expert-tier certification for designing end-to-end Solutions Architecture on Azure. It is the destination for any engineer aiming at the top Azure roles (architect, tech lead, principal engineer, consultant), and it is appearing as a hard requirement in senior Azure job postings with growing frequency. AZ-305 alone is often a prerequisite for senior Azure roles in the 10-15M JPY salary band, making it one of the highest-ROI certifications you can pursue.

This article walks through the AZ-305 exam specs, the AZ-104 coordination needed to earn the Expert certification, the 4-domain structure, strategies for the case study format, the relationship with the Well-Architected Framework, a 3-4 month roadmap to pass, and onward routes to adjacent Experts (AZ-400, SC-100). The first step to passing is understanding that AZ-305 is a design-decision-centric exam — it asks "which service do you choose and why" rather than implementation minutiae.

AZ-305 Exam Basics

AZ-305 follows the standard Expert-tier specs.100 minutes, 40-60 questions, passing score 700/1000, 165 USD / 21,103 JPY, valid for 12 months (renewable via a renewal assessment). You take it through Pearson VUE either online with OnVUE or at a test center, in multiple languages including Japanese. The question mix combines multiple-choice with 2-3 case studies (a long-form fictional company brief plus 5-10 design-decision questions), drag-and-drop questions, and sequence-ordering questions. The majority of items ask design decisions, not step-by-step implementation.

AZ-104 Is Required to Earn the Expert Credential

To earn the Expert credential via AZ-305, holding AZ-104 (Azure Administrator Associate) is a prerequisite. You can sit AZ-305 alone, but the Expert badge will not be issued. Only once you also pass AZ-104 will the Azure Solutions Architect Expert badge appear on Credly. Microsoft's official Credentials page explicitly recommends that AZ-305 candidates be at AZ-104 skill level, and the AZ-104 knowledge of the Azure portal, VM/VNet/Storage/Backup configuration forms the assumed baseline for AZ-305.

In practice the standard order is AZ-104 → AZ-305, because the implementation-level knowledge from AZ-104 becomes the reasoning behind "why this design would not be chosen" calls on AZ-305 case studies. Almost nobody takes them in the reverse order (AZ-305 first), and pass rates trend lower for those who do.

Domain 1: Design Identity, Governance & Monitoring (25-30%)

This domain designs the enterprise-wide control plane. Core topics include Microsoft Entra ID tenant design, hybrid identity strategy (Connect Sync vs Cloud Sync vs Federated), External Identity (B2B/B2C) integration; the Management Group → Subscription → Resource Group → Resource hierarchy, naming conventions, and tagging strategy; Azure RBAC role inheritance strategy and custom role design; Azure Policy for compliance enforcement, Initiatives, and Resource Selectors; Azure Blueprint (deprecation-bound, but legacy knowledge); Cost Management strategy (Budget, Cost Allocation, Reservation, Savings Plan); and unified Azure Monitor + Log Analytics + Sentinel monitoring design. The classic trap in this domain is how to split subscriptions (by environment vs department vs billing unit vs region), with frequent questions asking you to choose the optimal answer from the combination of company size, org structure, and governance requirements.

Domain 2: Design Data Storage Solutions (25-30%)

This domain designs the data storage strategy on Azure. Core topics include non-relational DB selection (Cosmos DB API choice [SQL/MongoDB/Cassandra/Gremlin/Table], Consistency Level [Strong/Bounded Staleness/Session/Consistent Prefix/Eventual], partition key design, throughput modes [Provisioned/Serverless/Autoscale]); relational DB selection (Azure SQL DB / MI / SQL on VM, service tiers, HADR strategy); object storage (Blob Hot/Cool/Cold/Archive, replication [LRS/ZRS/GRS/GZRS/RA-GRS]); files/disk (Azure Files SMB/NFS, Managed Disk SKU selection); data integration (Data Factory vs Synapse Pipeline vs Fabric Pipeline); and data migration (Database Migration Service, Azure Migrate). Storage selection questions repeatedly probe the 4-axis trade-off of cost, latency, redundancy, and consistency, testing your ability to read the priority axis out of the requirements.

Domain 3: Design Business Continuity Solutions (10-15%)

The weighting is small, but this domain has an outsized impact on pass/fail. Core topics include backup strategy (Azure Backup Vault, Recovery Services Vault, Snapshots, Long-term Retention); Site Recovery (Azure-to-Azure, On-prem-to-Azure, Recovery Plans, Replication Policies); choosing the numbers for RTO (Recovery Time Objective) and RPO (Recovery Point Objective); multi-region HA design (Active-Active vs Active-Passive, leveraging Region Pairs, Traffic Manager/Front Door failover); Availability Zone design (Zonal vs Zone-redundant); and multi-service HADR combinations (App Service + SQL DB Geo-replication + Front Door). Misreading the RTO/RPO numbers in this domain can cascade and break an entire case study, so practice extracting them precisely from requirements.

Domain 4: Design Infrastructure Solutions (25-30%)

The largest-weighted domain, covering compute, networking, and migration design decisions. For compute: choosing among VM, VMSS, App Service, AKS, Container Apps, ACI, Functions, Logic Apps; cost optimization with Spot VM, Reserved Instances, Hybrid Benefit; dedicated host and Ultra Disk selection for sustained high performance. For networking: VNet design, Hub-Spoke vs Mesh vs Virtual WAN, VPN Gateway vs ExpressRoute vs Virtual WAN Branch Connect, Azure Firewall vs NVA vs Application Gateway WAF, Front Door vs CDN vs Traffic Manager, and Private Link vs Service Endpoint. For migration: using Azure Migrate, choosing among Lift and Shift vs Re-platform vs Re-architect, DB migration with Database Migration Service, and App Service Migration Assistant.

How to Tackle the Case Study Format

The defining feature of AZ-305 is the presence of case study question blocks. A single case study describes a fictional company's Background, Existing Environment, Requirements, Technical Constraints, and Planned Changes across 5-10 pages, with 5-10 design-decision questions based on that material. Within a case study, you typically cannot go back (navigation to earlier questions from other ones is restricted), so a bad answering strategy can be fatal.

The standard approach: spend the first 5-10 minutes reading the entire case and locking in the keywords from each section (SLA numbers, budget constraints, organizational structure, incumbent vendors) before you start answering; use the right-side navigation pane to jump back to the relevant requirement section per question; and when stuck between similar options, eliminate the choice that proposes a feature not asked for in the requirements. On the real exam, 2-3 case studies mix with regular multiple-choice questions, and case studies alone can consume more than half the total exam time — simulate your time allocation in advance.

Relationship with the Well-Architected Framework

AZ-305 uses the Well-Architected Framework (WAF) as the implicit backbone of its exam design, and answer choices are crafted around the trade-offs between WAF's 5 pillars.The 5 pillars: 1) Reliability (SLA, redundancy, disaster recovery); 2) Security (identity, network, data protection); 3) Cost Optimization (sizing, Reserved Instances, Spot); 4) Operational Excellence (IaC, monitoring, DevOps); 5) Performance Efficiency (scaling, caching, data partitioning).

A question like "what is the correct choice when cost reduction is the top priority?" directly probes the Cost Optimization pillar; "how do you achieve 99.99% SLA?" directly probes Reliability. Completing the Microsoft Azure Well-Architected Framework module on Microsoft Learn at least once, and reaching a level where you can articulate the design principles and anti-patterns of each pillar, is essential for making the right calls on case studies.

A 3-4 Month Roadmap to Pass

A 3-month plan assuming you hold AZ-104 and have 1-3 years of Azure experience.Month 1: complete the AZ-305 learning path on Microsoft Learn (Identity / Governance / Storage modules), finish the Well-Architected Framework module, and read 10 reference architectures from the Azure Architecture Center.Month 2: cover BCP / DR / Infrastructure domains, read an additional 10-20 reference architectures, and start case study practice (official Practice Assessment plus third-party question banks).Month 3: iterate on the official Practice Assessment until you consistently score 80%+, revisit weak areas via the Architecture Center, and rehearse case study strategy (time allocation, reading style). If you do not yet hold AZ-104, prepend 3-4 months of AZ-104 study, making a realistic 6-7 month combined plan.

What to Aim for After AZ-305

There is no higher Architect tier, but adjacent Experts dramatically broaden your value.Integrate DevOps: AZ-400 (DevOps Engineer Expert) for CI/CD, IaC, GitOps, and SRE practices. An AZ-305 + AZ-400 Expert dual-track is a strong weapon for senior roles that need to "speak both design and deployment automation."Integrate security: SC-100 (Cybersecurity Architect Expert) for zero trust strategy and security architecture. An AZ-305 + SC-100 architect dual-track is valued on enterprise GRC engagements as "an architect who bakes security in from day one."Specialize deeper: AZ-700 (Network), SC-500 (GA expected 2026-09), DP-700, AI-103 each go deep in a single area. For multi-cloud architects, pairing with AWS Solutions Architect Professional or Google Cloud Professional Cloud Architect is highly regarded in the job market.

Frequently Asked Questions

Exam information in this article is based on the official AZ-305 page on Microsoft Learn and theAzure Architecture Center. This article is not an official Microsoft Corporation product and has no affiliation or endorsement. Microsoft, Azure, and Microsoft Entra are trademarks of the Microsoft group of companies. Information reflects officially published materials as of 2026-05-24. Always check the official pages for the latest updates.