AZ-305: Designing Microsoft Azure Infrastructure Solutions — Still the Core in 2027

Of everything Microsoft changed in the 2026/2027 certification reset, AZ-305 is the exam that barely moved. It was not retired. It was not renumbered. Its job — testing whether you can design Azure infrastructure solutions for real business requirements — is unchanged, because the job itself is unchanged.

If the AI certifications got a rewrite, AZ-305 got a footnote. That is not an accident. It is the point.

---

Why AZ-305 Survived the Reset Untouched

The 2026 shakeup retired AZ-204 and AZ-500, renamed the AI track, and invented a new agent builder lane. Infrastructure design — the work of taking requirements like "we need a highly available web app with a SQL backend, governed by policy, costing under a budget, secure enough for a regulated workload" — did not go anywhere. Nobody's prompt can design a secure, cost-aware, compliant architecture end to end and own the consequences of it. That job still goes to a person.

AZ-305 is the certification that says you can do that job at the design level.

---

The 2027 Azure Certification Map

Here is the simplest honest picture of where AZ-305 sits now — and where the AI exams landed:

2027 AZURE CERTIFICATION MAP
═══════════════════════════════════════════

FUNDAMENTALS (orient yourself)
  ├── AZ-900  — Azure Fundamentals (unchanged)
  └── AI-901  — Azure AI Fundamentals (renamed from AI-900, broader)

INFRASTRUCTURE CORE (did not move)
  ├── AZ-104  — Azure Administrator (admin muscle)
  └── AZ-305  — Azure Solutions Architect (design layer)  ← this exam

AI TRACK (rewritten for 2027)
  ├── AI-901  — Azure AI Fundamentals
  └── AI-103  — Azure AI Apps and Agents Developer (replaced AI-102)

SECURITY (renamed)
  └── SC-500  — Cloud and AI Security Engineer (replaced AZ-500)

NEW SPECIALTY
  └── AB-620  — Agent builder track (least crowded lane)

AZ-305 sits in the middle of the infrastructure core, exactly where it always did.

---

What AZ-305 Actually Tests

AZ-305 is a design exam. You are given a business or technical requirement and asked to pick the right Azure services, architecture pattern, and governance approach. The exam covers:

Compute Design

• When to use Virtual Machines, App Service, Azure Kubernetes Service, Azure Functions, Container Apps, and Azure Spring Apps — not just what each is, but which fits a given workload, scale pattern, and operational model.
• Migration considerations: lift-and-shift vs. refactor vs. replatform, and the tradeoffs among them.
• Scaling: autoscale, scale sets, and the design decisions that make scaling actually work rather than just exist.

Storage Design

• Blob storage tiers and lifecycle management for real data access patterns.
• Managed Disks, Files, and Disk Storage in the right context.
• Data redundancy options (LRS, ZRS, GRS, RA-GRS) and what each means for availability, cost, and recovery objectives.
• Storage security: shared access signatures, private endpoints, and encryption-at-rest considerations.

Networking Design

• Virtual Networks, subnets, and network segmentation as an architectural decision, not a checkbox.
• Load balancing: Azure Load Balancer vs. Application Gateway vs. Front Door vs. Traffic Manager — and when each is the right answer.
• Private endpoints, service endpoints, DNS, and the connectivity patterns that keep traffic off the public internet where it should be.
• Hybrid connectivity: ExpressRoute, VPN Gateway, and the scenarios that drive one vs. the other.

Identity and Security Design

• Microsoft Entra ID (formerly Azure AD) integration: hybrid identity, B2B, B2C, and the scenarios each serves.
• Managed identities vs. service principals vs. keys — and why managed identity is usually the answer.
• Role-Based Access Control design: least privilege, scope, and the way permissions compound across a subscription.
• Azure Policy, Blueprints (where they still apply), and the governance tooling that keeps a design from drifting.

Business Continuity and Disaster Recovery

• Backup and restore: what to back up, how often, and the RPO/RTO implications of your choices.
• Site Recovery and geo-redundancy for the workloads that need them.
• The difference between high availability and disaster recovery, and why designing for one is not the same as designing for the other.

Cost and Monitoring Design

• Cost estimation and optimization: reserved instances, savings plans, right-sizing, and the design-time decisions that dominate a workload's bill.
• Monitoring and alerting design: what to monitor, how to structure alerts, and the operational visibility a design needs to survive contact with real users.

---

Why AZ-305 Is Still the Anchor

If you look at the 2027 certification map, AZ-305 sits at the center of the infrastructure track the way it always did:

• AZ-900 gives you the vocabulary.
• AZ-104 gives you the administration muscle (and is still the natural next step after fundamentals).
• AZ-305 gives you the design layer on top of that muscle.

The AI certifications now run on top of infrastructure someone has to design, secure, and cost-control. The agent builders Microsoft is pushing still need networks, identities, and governance. The platform engineering lane that pays the money still runs on the skills AZ-305 tests.

None of that changed because AI got reorganized.

---

What Has Been True Since Before 2026

The durable truths of AZ-305 did not move:

• Design is a decision discipline, not a memorization exercise. The exam rewards people who can take a scenario, weigh options, and justify a choice — not people who have memorized one canonical architecture.
• Tradeoffs are the point. The right answer to "design a storage solution" is almost never "the one with the most features." It is the one that fits the access pattern, the budget, the compliance requirements, and the team's ability to operate it.
• Security and cost are design concerns, not afterthoughts. A design that ignores either one is a design that fails in production, and the exam tests for that in a way that a checklist cannot capture.

If you are studying for AZ-305 now, these truths are still true. The material is still current. The exam is still worth taking.

---

How to Study for AZ-305 in 2027

1. Know the core services cold, in context. Not "what is App Service" but "given this workload, why App Service and not Kubernetes, and what would change my mind."
2. Practice scenario questions. AZ-305 is a scenario exam. Practice questions that force you to choose between two plausible designs are more valuable than any number of definition-recall questions.
3. Learn the governance tooling well enough to apply it. Azure Policy, RBAC, managed identity — these are not side topics. They are design concerns and the exam treats them that way.
4. Do not skip the cost and monitoring design sections. They are easy to under-prepare for and expensive to fail on, because they are easy to dismiss as "soft" until you are staring at a question that turns on them.
5. Use AZ-104 as a foundation if you have not taken it. AZ-305 assumes you understand the services at an operational level. If you only know them conceptually, the design questions will feel harder than they are.

---

The Bottom Line

AZ-305 is the middle of the infrastructure core. If your goal is to be the person who can design Azure solutions that actually work — secure, available, cost-aware, governable — AZ-305 is still the exam that certifies that.

The world changed around it. It did not need to change itself.