AZ-305 Solutions Architect Expert Study Guide

By Macdara Ó Murchú · Founder, AzurePrep·Last reviewed ·13 min read·2,704 words

The Microsoft Azure AZ-305 certification marks a significant milestone in your cloud career. This exam tests your ability to design complete Azure infrastructure solutions at the enterprise level, positioning you as a trusted solutions architect who can make critical decisions about cloud adoption, security, governance, and cost optimization. Unlike the foundational AZ-104 exam, AZ-305 requires you to think strategically about trade-offs, scalability, and long-term architectural decisions.

This guide covers everything you need to pass AZ-305, from prerequisites to exam strategy to domain-specific content that will prepare you for the challenging case study format.

What AZ-305 Actually Tests

The AZ-305 exam is fundamentally different from other Azure certifications. It does not test your ability to click buttons in the Azure Portal or execute specific commands. Instead, it evaluates whether you can design enterprise-grade solutions that balance performance, security, cost, and compliance requirements.

You will face scenarios that mirror real-world situations: a healthcare company moving to the cloud needs HIPAA compliance and disaster recovery. A financial services firm requires multi-region high availability with sub-second failover. A startup wants to minimize costs while maintaining scalability. Your job is to recommend the right Azure services and architectural patterns to solve these problems.

The exam tests architectural thinking. You must understand when to use Azure SQL Database versus Cosmos DB, when hub-and-spoke topology matters, how to design for disaster recovery with acceptable RTO and RPO targets, and how to implement governance across multiple teams and subscriptions.

AZ-104Prerequisite certMust hold before attempting
$165Exam cost (USD)Expert level
180 minExam durationScenario-heavy, time pressure

Prerequisites: You Must Pass AZ-104 First

Microsoft requires the AZ-104 Azure Administrator certification as a prerequisite for AZ-305. This is non-negotiable. You cannot register for AZ-305 without first passing AZ-104.

This prerequisite exists because AZ-305 assumes you understand Azure fundamentals: virtual networks, storage accounts, identity and access management, and basic resource deployment. The exam will not explain how to create a virtual machine or configure a network security group. It assumes you already know these operations and focuses instead on how to design solutions that use these components strategically.

If you have not yet passed AZ-104, obtain that certification first. The preparation time typically ranges from 2-4 weeks for experienced IT professionals. Once you hold AZ-104, you are ready to invest 6-12 weeks in AZ-305 preparation.

Who Should Take This Exam

AZ-305 targets cloud architects and senior infrastructure professionals with substantial Azure experience. This includes:

You should have hands-on experience with Azure for at least 12-18 months. Reading documentation and watching videos is insufficient. You need practical exposure to network design, storage decisions, security implementations, and operational challenges.

The ideal candidate has managed multiple Azure projects, made decisions about service choices, learned what works and what fails, and understands the consequences of architectural decisions six months or a year later.

Architect Expert Path
AZ-900FundamentalsFUND
AZ-104Administrator AssocASSOC
AZ-305Architect ExpertEXPERT

Exam Format and Structure

AZ-305 differs significantly from multiple-choice exams you may have taken previously.

Case Study Format

The exam consists of case studies followed by multiple-choice questions. You receive a detailed scenario document (typically 6-8 pages) describing a company, its requirements, current infrastructure, compliance needs, budget constraints, and growth plans. After reading the scenario, you answer 8-12 questions specific to that case study.

The case study contains critical details scattered throughout. You might find a key compliance requirement in the middle of a paragraph, or a cost constraint mentioned only once. Successful test-takers read the entire scenario before answering questions, annotating important details.

Time Allocation

You have approximately 120 minutes to complete the exam. With multiple case studies, you must allocate time carefully. Spending 15 minutes reading a case study and 10-15 minutes answering its questions is reasonable. Avoid getting trapped on a single difficult question.

Question Types

All questions are multiple choice with four options. You select one answer per question. Some questions ask you to identify the best solution. Others ask you to identify what requirement a proposed solution meets or fails to meet.

Five Core Exam Domains

Microsoft organizes AZ-305 content across five domains. Understanding the distribution helps you allocate study time appropriately.

Domain Percentage Key Topics
Design identity, governance, and monitoring solutions 25-30% Azure AD, RBAC, policy, cost management, Log Analytics
Design data storage solutions 25-30% SQL Database, Cosmos DB, storage accounts, data lakes, caching
Design business continuity solutions 10-15% Backup, disaster recovery, RTO/RPO, failover strategies
Design infrastructure solutions 25-30% Virtual networks, load balancing, app deployment, hybrid connectivity
Design migrations 5-10% Assessment, migration strategies, legacy system integration

Note that the exam is heavily weighted toward identity/governance, data storage, and infrastructure. Business continuity deserves focused study, but represents a smaller percentage. azureprep.com offers targeted practice tests for each domain, allowing you to master weak areas before exam day.

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

This domain requires deep understanding of Azure AD (now Microsoft Entra ID), role-based access control, policy enforcement, cost management, and operational monitoring.

Azure AD and Identity Architecture

Enterprise organizations struggle with identity at scale. You must design solutions that support thousands of users, multiple applications, third-party integrations, and evolving security requirements.

Key concepts include:

A typical question: "A financial services company has 15,000 employees across four countries. They use on-premises Active Directory and are expanding to Azure. They require conditional access that blocks access from non-managed devices. How should they design their identity solution?"

The correct answer considers directory synchronization (Azure AD Connect), conditional access policies in Azure AD, device compliance requirements, and possibly Azure AD Premium licensing for advanced features.

Governance and Compliance

Governance ensures organizations use Azure consistently, securely, and cost-effectively across teams.

Azure Policy enforcement prevents teams from creating non-compliant resources. Management Groups provide hierarchical governance across multiple subscriptions. Blueprints define standardized environments for teams to deploy.

The hardest questions in this area ask you to balance governance with agility. Over-strict policies slow development. Too-lenient policies create security and compliance risks.

Cost Management and Monitoring

Organizations cannot manage what they do not measure. Azure Monitor, Log Analytics, and Azure Cost Management provide visibility into resource usage and spending.

Architecture decisions directly impact costs. Choosing between VM families, storage tiers, or service SKUs can multiply monthly bills. You must understand cost drivers and recommend solutions that meet requirements while controlling expenses.

Monitoring questions often present a scenario: "A development team is experiencing unexpected Azure bills. They have 200 VMs running across multiple resource groups. How would you implement monitoring to identify cost anomalies?"

The answer involves Azure Cost Management for cost analysis, Azure Monitor for resource metrics, and potentially Azure Advisor for optimization recommendations.

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

This is perhaps the most conceptually challenging domain. Storage decisions have massive consequences. Choosing the wrong database for a critical application creates problems that persist for years.

Relational vs. NoSQL vs. Analytical Stores

You must master the fundamental trade-offs:

A classic question: "An e-commerce company processes millions of orders daily. They need to query order history, customer profiles, and payment information transactionally. Where should they store data?"

Answer: Azure SQL Database with appropriate scaling (elastic pools or hyperscale) because relational consistency, transactional integrity, and strong querying capabilities matter more than horizontal scale.

Different scenario: "A real-time gaming company stores player stats, match results, and social connections. Data access patterns vary widely, and they need sub-millisecond latency with millions of concurrent players globally."

Answer: Cosmos DB with multi-region replication because flexible schema, eventual consistency, and massive global scale matter more than strict transactions.

Caching and Performance

Caching dramatically improves application performance. Azure Cache for Redis sits between applications and databases, reducing database load by 10-100x for read-heavy workloads.

You must understand when caching helps and when it creates problems. Caching works for relatively static data (product catalogs, user preferences) but creates consistency issues for frequently changing data (account balances, inventory counts).

Data Migration and Integration

When designing data storage, you must consider how data gets there. Azure Data Factory orchestrates data movement from legacy systems. Azure Synapse Pipelines integrate with data lakes. You should understand these tools conceptually, not operationally.

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

Business continuity ensures services survive failures. The two critical metrics are RTO (Recovery Time Objective) and RPO (Recovery Point Objective).

RTO answers: "How long can we tolerate downtime?" An e-commerce site might have RTO of 5 minutes. An internal HR system might have RTO of 8 hours.

RPO answers: "How much data can we afford to lose?" A payment system might have RPO of seconds. A data warehouse might accept RPO of hours.

High Availability Architecture

High availability keeps services running during component failures. Availability Zones (independent datacenters within a region) protect against datacenter outages. Load balancers distribute traffic across multiple instances. Managed services like Azure App Service handle failover automatically.

A solution with RTO of minutes and RPO of minutes typically requires:

Disaster Recovery Architecture

Disaster recovery prepares for regional outages. Azure Paired Regions provide geo-redundancy. You replicate critical data to a secondary region and maintain recovery runbooks for rapid failover.

RTO and RPO determine strategy:

The exam tests whether you can match architectural approaches to RTO/RPO requirements without over-building (and over-spending).

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

Infrastructure solutions encompass networking, compute, and deployment patterns.

Virtual Network Architecture

Most organizations use hub-and-spoke topology:

This architecture scales to hundreds of spokes, maintains security boundaries, and simplifies management.

Landing zones formalize this pattern. Azure provides landing zone reference architectures that teams use to create standardized environments for new workloads.

Load Balancing and Traffic Management

Azure Load Balancer (Layer 4) distributes traffic across VMs. Application Gateway (Layer 7) understands HTTP and can route based on hostname or path. Azure Front Door provides global load balancing with DDoS protection.

Selecting the right load balancer depends on requirements: internal versus external, Layer 4 versus Layer 7, regional versus global.

Compute and Deployment

Virtual Machines provide maximum control but require operational overhead. Container instances offer lightweight containerization. App Service provides platform-as-a-service simplicity. Azure Functions enable serverless workloads.

A well-designed infrastructure solution uses the least complex service that meets requirements. If App Service works, use it instead of VMs. If managed databases work, avoid self-hosted databases on VMs.

Mastering Design Patterns

Three patterns appear repeatedly on AZ-305:

Hub-and-Spoke Networking

Centralizes security controls and shared services. The hub contains firewalls, VPN gateways, and DNS servers. Spokes are isolated workload networks. This prevents traffic from flowing directly between spokes (they communicate through the hub).

Benefits: centralized security, scalability to hundreds of workloads, shared services.

Drawbacks: adds latency (all traffic traverses hub), hub becomes critical point of failure.

Landing Zone Design

A landing zone is a pre-configured Azure environment ready for workload deployment. Organizations create landing zones for different teams (development, production, data analytics) to enable self-service while maintaining governance.

Key elements: network topology, identity integration, policy enforcement, monitoring, cost allocation.

Well-designed landing zones let teams deploy workloads in hours instead of weeks.

High Availability and Disaster Recovery

Availability Zones replicate across datacenters within a region (99.99% SLA). Paired Regions enable geo-redundancy across regions (99.999% SLA for most services).

Design for failure: assume individual components will fail and architect around failures.

The Hardest Questions: Balancing Requirements

The most challenging questions present competing requirements and ask you to choose the solution that meets everything while optimizing cost.

Example: "A company needs a database solution that supports complex transactions, scales to 10 million daily requests, costs less than $2,000 monthly, and provides disaster recovery. Which solution?"

This tests whether you understand:

You might recommend Azure SQL Database with read replicas for some workloads, or Cosmos DB with careful partitioning for others. The point: architecture is about understanding trade-offs.

Study Approach: Think Like an Architect

Studying for AZ-305 requires different thinking than studying for Azure Administrator or Fundamentals exams.

Do not memorize facts. Instead, practice thinking through scenarios:

Read Azure architecture documentation, not just training courses. Azure Architecture Center provides real-world patterns used by large organizations. These patterns appear frequently on the exam.

azureprep.com AZ-305 practice tests expose you to the case study format and help you identify knowledge gaps. Practice tests are more valuable than lectures because they force you to apply knowledge under time pressure, exactly like the real exam.

For someone with AZ-104 certification and 12+ months of hands-on Azure experience:

Adjust this timeline based on your experience and how you perform on practice tests.

Exam Tips and Strategies

Read case studies completely before answering questions. Many candidates skim scenarios and miss critical requirements.

Annotate key details: budget, compliance requirements, RTO/RPO targets, geographic distribution. Mark these in your notes as you read.

When multiple answers seem correct, choose the one that best balances all requirements. AZ-305 often tests whether you understand why one approach is superior to alternatives, even when alternatives partially work.

Pay attention to cost. The hardest questions ask which solution meets all requirements while being most cost-effective. This requires understanding cost drivers for each Azure service.

Remember you can return to previous questions. If a question takes too long, flag it and continue. You can return after answering all other questions if time permits.

Do not overthink questions. Azure architects are pragmatists. They choose solutions that work reliably and cost-effectively. Look for the practical answer, not the theoretically perfect one.

Final Thoughts

AZ-305 certification validates that you can design enterprise Azure solutions. This is a valuable skill as organizations accelerate cloud adoption. The exam is challenging because the role itself is challenging.

Prepare thoroughly by understanding not just Azure services, but why architects choose specific services for specific problems. Use azureprep.com practice tests to expose yourself to the case study format and build confidence. Think like an architect during preparation and during the exam.

Pass AZ-305, and you have earned a credential that opens doors throughout the cloud industry. The effort is worth it.