AZ-305 FAQ — Common Questions About the Azure Solutions Architect Exam

Answers to the most common questions about AZ-305: what’s tested, prerequisites, how it differs from AZ-104, how long to study, labs, and exam-day tactics.

What is AZ-305 and who should take it?

AZ-305 validates solution architecture decisions in Azure: identity/governance/monitoring, data services, business continuity, and infrastructure design. It’s for architects and senior engineers who translate requirements into Azure designs that are secure, reliable, and cost-aware.

How is AZ-305 different from AZ-104?

AZ-104 is operational (configure and run Azure). AZ-305 is design-heavy (choose the right services and justify trade-offs). AZ-305 assumes you understand operational realities (monitoring, backup, RBAC scopes), but tests your ability to select architectures.

Do I need AZ-104 first?

You can usually sit AZ-305 without AZ-104, but to earn Azure Solutions Architect Expert, you must hold Azure Administrator Associate (AZ-104) and pass AZ-305. Always confirm current requirements on Microsoft Learn.

How many questions and what is the passing score?

The passing score is typically 700/1000 (scaled). Question count and format vary (MCQ/MR, case studies, drag-and-drop). Expect scenario wording that forces trade-offs.

What domains are tested?

  • Identity, governance, monitoring (log routing, IAM design, policies/management groups)
  • Data storage (relational services, NoSQL, unstructured storage, integration/analytics)
  • Business continuity (backup/restore, DR, high availability)
  • Infrastructure (compute selection, application architecture, migrations, networks)

Are labs required?

Hands-on work helps, but AZ-305 is not “lab-y.” You should be able to design from first principles, and it’s much easier if you’ve built a small reference stack: hub-spoke VNet, Private Endpoints, a workload with App Insights + Log Analytics, a relational DB, a storage account with lifecycle rules, and a basic DR story.

How long does it take to prepare?

With strong Azure exposure: 3–5 weeks part-time. If you’re new to Azure, it’s better to do AZ-900 → AZ-104 → AZ-305 rather than jumping straight to architecture patterns.

What are the most common weak spots?

  • Picking the wrong front door: Front Door vs App Gateway vs LB vs Traffic Manager
  • Confusing RBAC vs Policy vs Locks (access vs compliance vs deletion protection)
  • Under-designing DR (backups only) or over-designing it (too complex/expensive)
  • Data service selection (SQL DB vs MI vs SQL VM; Cosmos partitions/consistency)
  • Missing DNS and routing details for private access patterns

Any last-mile tips?

  • For every scenario, write: Availability target, data sensitivity, latency, region scope, budget. Then choose the simplest design that satisfies those constraints.
  • Treat the cheatsheet as a set of decision trees, not a glossary.
  • In practice review, convert misses into one-line rules (e.g., “Need ordered queue + transactions → Service Bus”).

Keep going