AZ-305 is the Azure Solutions Architect Expert exam. People walk in expecting an Azure trivia quiz and walk out confused, because that's not what it is. It tests whether you can read a set of requirements and pick a design that fits them. The services are just the vocabulary. The exam is about the choosing.
If you study it like AZ-104 (the associate admin exam), you'll struggle. AZ-104 asks "how do you do X." AZ-305 asks "given these constraints, which approach is right, and why not the other three." That's a different muscle.
What AZ-305 actually covers
The exam is organized around designing four things:
- Identity, governance, and monitoring solutions
- Data storage solutions
- Business continuity solutions
- Infrastructure solutions
Notice every line starts with "design." You're not configuring anything. You're choosing between options that all technically work, where one fits the stated requirements better than the rest.
Microsoft also expects you already hold AZ-104 knowledge or the equivalent experience. AZ-305 doesn't re-teach the basics. It assumes you know what a VNet, a storage account, and a managed identity are, then asks you to assemble them into something that meets a goal.
The design mindset
Here's the shift. For almost every question, two or three of the answer choices are valid Azure architectures. They'd all run. The right answer is the one that best satisfies the constraint buried in the scenario.
So when you read a question, hunt for the constraint first:
- "minimize cost" - now the cheapest workable option wins, even if it's less capable
- "minimize administrative effort" - favor managed and serverless services over things you run yourself
- "minimize latency for users in three regions" - now geo-distribution matters, single-region answers are out
- "meet a 15-minute RPO" - now your backup and replication choice is forced
- "must not store keys in code" - managed identities, Key Vault, not connection strings
The constraint is the whole question. Two answers might be identical except one uses a managed identity and one uses a stored secret. If the scenario said "follow least privilege" or "avoid storing credentials," the secret answer is wrong even though it works fine in real life.
Train yourself to underline the constraint before you look at the options. That one habit moves more points than memorizing service limits.
Patterns worth knowing cold
You don't need to memorize every SKU. You do need fluent recall of which service solves which problem. A short list of the comparisons that show up constantly:
- Storage redundancy: LRS vs ZRS vs GRS vs GZRS. Map each to "what failure does it survive" - disk, datacenter, region.
- Databases: when to reach for Azure SQL Database vs SQL Managed Instance vs Cosmos DB. Cosmos shows up whenever you see "global distribution" or "single-digit millisecond latency" or "multiple consistency models."
- Compute: App Service vs Container Apps vs AKS vs Functions. The driver is usually how much control vs how little ops you want.
- Identity: managed identities vs service principals, and where Conditional Access and PIM fit.
- Continuity: Azure Backup vs Azure Site Recovery. Backup is for restoring data, Site Recovery is for failing over a whole workload. RPO and RTO numbers in the scenario tell you which.
- Governance: Azure Policy vs RBAC vs Blueprints vs Management Groups, and the order they nest in.
For each of these, don't just learn what they are. Learn the sentence in a scenario that points to one over the others.
How I'd study
Read the official Microsoft Learn path for AZ-305 once, end to end, to get the vocabulary. Then stop reading and start practicing scenarios. Your reading-to-practice ratio should tilt hard toward practice, because the exam is a reasoning test, not a recall test.
When you do practice questions, don't just check if you got it right. For every question, force yourself to say out loud why each wrong answer is wrong. "B is a valid architecture but it doesn't minimize cost." "C stores a secret, and the scenario banned that." If you can articulate why the distractors fail, you've actually learned the question. If you only know the right letter, you've memorized noise.
This is also where talking through a scenario with someone, or running mock interview-style drills where you have to defend a design out loud, pays off more than flashcards. The exam is asking you to justify a choice. Practice justifying choices.
The honest summary
AZ-305 isn't hard because Azure is hard. It's hard because it refuses to give you a single correct service and instead makes you weigh tradeoffs under a constraint. Study the tradeoffs, read for the constraint in every scenario, and practice explaining your reasoning. Do that and the exam stops feeling like a memory test and starts feeling like the job it's named after.