AZ-305: Azure architecture and production decisions
Design Azure solutions from access, data, continuity, compute, and migration requirements through production decisions and cases.
Objectives and progression
Eight lessons, 50 regular questions, and eight original cases provide a first pass across the four AZ-305 domains using the April 2026 outline’s weight ranges. Fictional cases focus on architecture responsibilities and transition to RUN. The internal assessment reuses 32 decisions and does not reproduce the official exam. Earning external Azure Solutions Architect Expert also requires Azure Administrator Associate; completing this path does not meet that requirement. This first pass does not provide exhaustive coverage, a cloud lab, or a full mock exam.
Audience: Architects, experienced administrators, and infrastructure and production technical managers.
Prerequisites: Azure administration, networking, data, and application operations. The official Expert credential also requires Azure Administrator Associate.
295 estimated study minutes
- Design identity, governance, and evidence collection.
- Choose data and compute around constraints and trade-offs.
- Evaluate service recovery against RTO and RPO.
- Plan integration, networking, migration, and operational autonomy.
Modules
- Identity and access boundaries
- Governance, cost, and observation
- Relational data decisions
- Storage and data integration
- Continuity and demonstrated recovery
- Compute and operational responsibility
- Integration and change contracts
- Networking and complete-service migration
Continue learning
- AZ-104 — Azure Administrator
- AWS Certified Solutions Architect Associate
- Technical Project Manager
- Production Support L3
References and version
AZ-305 objectives 2026-04-17
- Azure Solutions Architect Expert · 2026-09-29
- AZ-305 study guide · 2026-09-29
- Service Bus settlement · 2026-09-29
- Event Grid delivery · 2026-09-29
- Event Hubs concepts · 2026-09-29
- Application Insights OpenTelemetry overview · 2026-09-29
- VM Scale Sets autoscale · 2026-09-29
- Microsoft exam scoring · 2026-09-29
- Microsoft exam experience · 2026-09-29
- Managed identities · 2026-09-29
- Azure RBAC overview · 2026-09-29
- Azure Policy · 2026-09-29
- Azure budgets · 2026-09-29
- Diagnostic settings · 2026-09-29
- Blob access tiers · 2026-09-29
- Storage redundancy · 2026-09-29
- VNet peering · 2026-09-29
- Bicep what-if · 2026-09-29
- Privileged Identity Management · 2026-09-29
- Access reviews · 2026-09-29
- Conditional Access · 2026-09-29
- Emergency access accounts · 2026-09-29
- Key Vault RBAC · 2026-09-29
- Resource organization · 2026-09-29
- Resource tags · 2026-09-29
- Log Analytics workspace design · 2026-09-29
- Azure SQL service comparison · 2026-09-29
- SQL elastic pools · 2026-09-29
- SQL serverless · 2026-09-29
- SQL read scale-out · 2026-09-29
- SQL automated backups · 2026-09-29
- SQL Private Link · 2026-09-29
- Cosmos DB partitioning · 2026-09-29
- Data Factory integration runtime · 2026-09-29
- Immutable blob storage · 2026-09-29
- Disaster recovery architecture · 2026-09-29
- Azure compute selection · 2026-09-29
- Azure Batch · 2026-09-29
- Cache-aside pattern · 2026-09-29
- Transactional outbox · 2026-09-29
- Load balancing options · 2026-09-29
- ExpressRoute encryption · 2026-09-29
- Migration dependency analysis · 2026-09-29
What you will explore
0 / 8Identity and access boundaries
Design daily access and administrative recovery.
Governance, cost, and observation
Turn organizational requirements into verifiable controls.
Relational data decisions
Balance compatibility, capacity, consistency, and recovery.
Storage and data integration
Relate distribution, access, retention, and integration paths.
Continuity and demonstrated recovery
Design and measure operational recovery, including dependencies.
Compute and operational responsibility
Choose a platform from requirements and team capability.
Integration and change contracts
Define delivery, consistency, caching, and controlled deployment.
Networking and complete-service migration
Relate protocol, routing, and cutover dependencies.